| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 32357 | 2003-04-16 05:37:00 | Hardware Diagnostic Tool | TerryW (2183) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 136201 | 2003-04-16 05:37:00 | I'm looking for a decent hardware diagnostic program that runs from a dos environment to do some troubleshooting on a PC. When I last played with these tools I used to use the likes of CheckIt, AMI Diag and QA Plus, but I am looking for some programs to download that I can run from DOS to try it out. I've got a relatively new PC that is built from components that has become VERY flakey over the past week. I am going to go down the part swapping phase, but I want some diag software to give me some clues for where to start. Reloading windows generally fixes it, the PC can reboot multiple times with no problem, but come back to it a bit later on and its dies - the most recent was a TRAP 0000000006 ===========EXCEPTION======== when loading XP Pro yesterday, no it doesnt go past this. I know I could repair or reinstall but I want to find out what is causing this before I reinstall again. |
TerryW (2183) | ||
| 136202 | 2003-04-16 05:47:00 | Oh for the days when all the chips were in sockets and the IBM diagnostics told you which 64k or 256k (bit) RAM chip to replace. :D Have a look in the Simtel msdos archive. I seem to remember there were a few such programmes there. My first suspicion if there's a problem loading an MS OS is memory. That's when memory use is greatest, and the meory has to be right. After that comes connectors. |
Graham L (2) | ||
| 136203 | 2003-04-16 06:37:00 | There is a version of aida that runs in dos, it should be here (www.aida32.hu). For a good memory checker, check out memtest86 (www.aida32.hu). |
bmason (508) | ||
| 136204 | 2003-04-16 08:41:00 | Another good memory tester is DocMem . | mikebartnz (21) | ||
| 136205 | 2003-04-16 19:31:00 | Hi TerryW, This may or may not be relevant but according to Microsoft this might help you . Its for Windows 2000 but they are from the same stable so it might work . "Trap 00000006 Exception" Error Message When You Start Windows 2000 The information in this article applies to: Microsoft Windows 2000 Advanced Server Microsoft Windows 2000 Professional This article was previously published under Q329903 SYMPTOMS When you try to start your computer, you may receive an error message that is similar to the following error message: TRAP 00000006 exception TR=0028 cr0=0000000011, cr2=00000000, cr3=000000000 GDT limit=03ff base=00017000 idt limit=07ff base=00017400 CS:eip=0008:08000000 ss:esp=0010:00061fec errcode=0000 flags=000100012 nocy nozr intdis down trapdis eax=0000110c ebx0003001d5 ecx=00001660 cdx=534d0030 ds-0010 es=0010 edi=00350000 exi=00051db6 ebp=00061ff0 cr0=00000011 fs=0030 gs=0000 After you receive this error message, Windows does not start . CAUSE This issue may be caused by a damaged NTLDR file . RESOLUTION To resolve this issue, replace the NTLDR file by using the Windows Recovery Console: Restart your computer by using either the Windows 2000 CD-ROM or Windows Setup floppy disks . At the Welcome to Setup screen, press R to repair the Windows 2000 installation . Press C to repair the Windows 2000 installation by using the Recovery Console . Type the number of the Windows installation that you want to repair, and then press ENTER . Type the administrator password, and then press ENTER . NOTE: The Recovery Console uses the administrator password that you provided when you installed Windows 2000 . Changes that you made to the administrator password after you installed Windows do not apply to the Recovery Console . Type chkdsk /r, and then press ENTER . Type cd . . , and then press ENTER . Type ren ntldr ntldr . old, and then press ENTER . Type copy CD-ROMDrive:\i386\ntldr HardDisk:\ntldr, and then press ENTER, where CD-ROMDrive is the CD-ROM drive letter, and HardDisk is the drive letter of your hard disk . Type exit, and then press ENTER to restart your computer . Regards Repo74 |
Repo74 (2384) | ||
| 136206 | 2003-04-16 21:53:00 | I guess the big question is WHAT caused it (The file) to be damaged in the first place. | somebody (208) | ||
| 136207 | 2003-04-17 04:36:00 | Thanks for the Technet link; I think I found it the other night while doing a frenzied search . Just as an update I swapped out the ram for an old stick I had lying around and took the hard drive out - didn't unhook it but just moved it outside the case and the damn thing booted first time . . . shouldn't have done two things at once . I am doubtful about the hard drive being involved as its in a good firm mounting place, its still sitting in the cage and no problem with air flow or power (i think) so I guess its just a case of wait and see . . . Thanks for the input guys |
TerryW (2183) | ||
| 1 | |||||