Windows 7 (almost fresh install) keeps on crashing

[Samoth]

Hello guys,

I´m so glad, that I found this board. Looks like, there are some pros doing the crash-debugging, so you´re my final hope.

Since aboud end of 2009 the computer of a friend keeps on crashing with a BSOD. What we´ve done so far:

- Memtest: RAM was tested OK
- Chipsetdriver-Update: Keeps on crashing
- VGA-Update: Keeps on crashing
- Windows 7 reinstalled: Keeps on crashing

The BSOD appears randomly. There is no action, that I´m aware of, which might let the PC act funny.

Attached to my begging you´ll find a couple of crashdumps in a RAR-file.

What I´ve seen (by running WinDbg), it looks like there is always the same error, but I wouldn´t count too much on my capabilities on reading crashdumps. Maybe you can find something out? . Any questions are well appreciated - I´ll give my best to assist you.

Thanks so far,
Samoth

 

[usasma]

24 memory dumps from 22 Nov 2009 to 04 May 2010 (5½ months)
4 different STOP errors (0x1A, 0x3B, 0x7F, 0xE1) with STOP 0x7F being the most common.
Please see the "Usual causes" section of the link to the STOP 0x7F error.
It's gonna be a while until the dump files stop running, so I'll post this and will return later with the results.

 

[usasma]

OK, the 2 STOP 0xE1 errors blame networking drivers - the rest blame the Windows kernel
As such, I'd:
- download new copies of the latest networking drivers for your system (both wired and wireless if so equipped).
- remove the old drivers using Control Panel...Programs...Uninstall a program
- install the new drivers and monitor for further BSOD's.

Then visit Windows Update and get all the updates that are available (it appears that the system isn't updated, but I can't be sure).

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

ADIHdAud.sys Tue Jan 16 11:36:18 [COLOR=Red]2007[/COLOR] - SoundMAX Digital HD Audio Driver - http://www.carrona.org/dvrref.html#ADIHdAud.sys
ASACPI.sys   Sun Mar 27 22:30:36 [COLOR=Red]2005[/COLOR] - [COLOR=Red]This is a [U][B]KNOWN BSOD[/B][/U] causing driver, update it [U][B]IMMEDIATELY[/B][/U]!!![/COLOR][COLOR=Black] - Asus ATK0110 ACPI Utility driver[/COLOR] - http://www.carrona.org/dvrref.html#ASACPI.sys
fwlanusb.sys Thu Dec 14 12:04:55 [COLOR=Red]2006[/COLOR] - AVM FRITZ!WLAN USB Stick - http://www.carrona.org/dvrref.html#fwlanusb.sys

Summary of the BSOD's:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May  4 12:19:45.661 2010 (GMT-4)
System Uptime: 0 days 0:20:34.409
BugCheck 7F, {8, 80050031, 6f8, fffff80002e4be58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Apr 27 12:20:13.418 2010 (GMT-4)
System Uptime: 0 days 0:08:25.166
BugCheck 7F, {8, 80050031, 6f8, fffff80002ea0e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Apr 26 14:49:50.716 2010 (GMT-4)
System Uptime: 0 days 0:05:40.464
BugCheck 7F, {8, 80050031, 6f8, fffff80002e8fe58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Apr 26 14:43:33.863 2010 (GMT-4)
System Uptime: 0 days 0:04:36.611
BugCheck 7F, {8, 80050031, 6f8, fffff80002e8fe58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Apr 26 14:37:50.309 2010 (GMT-4)
System Uptime: 0 days 0:56:48.057
BugCheck 7F, {8, 80050031, 6f8, fffff80002e52e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Apr 26 13:40:16.894 2010 (GMT-4)
System Uptime: 0 days 0:54:50.642
BugCheck 7F, {8, 80050031, 6f8, fffff80002e9de58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Apr 24 18:08:10.776 2010 (GMT-4)
System Uptime: 0 days 0:22:46.524
BugCheck 7F, {8, 80050031, 6f8, fffff80002e3ce58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Apr 24 17:44:18.317 2010 (GMT-4)
System Uptime: 0 days 0:07:53.065
BugCheck 7F, {8, 80050031, 6f8, fffff80002e96e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  SkypeNames.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Apr 24 12:14:00.160 2010 (GMT-4)
System Uptime: 0 days 6:50:16.908
BugCheck 7F, {8, 80050031, 6f8, fffff80002e89e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 15 13:25:55.468 2010 (GMT-4)
System Uptime: 0 days 0:11:17.216
BugCheck E1, {fffff88001798010, 2, fffffa800585eb90, fffffa800585eba0}
Probably caused by : ndis.sys ( ndis!ndisWorkItemHandler+0 )
BUGCHECK_STR:  0xE1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Apr  6 13:10:32.156 2010 (GMT-4)
System Uptime: 0 days 0:00:20.904
BugCheck 3B, {c0000005, fffff800031a2fb9, fffff880031f1740, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+51 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  autochk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Apr  6 06:44:35.844 2010 (GMT-4)
System Uptime: 0 days 0:00:20.592
BugCheck 3B, {c0000005, fffff80003155fe0, fffff88003ffb740, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+78 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  autochk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Mar 28 07:18:02.097 2010 (GMT-4)
System Uptime: 0 days 0:05:16.720
BugCheck 7F, {8, 80050031, 6f8, fffff80002e8e798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Mar 28 07:12:03.009 2010 (GMT-4)
System Uptime: 0 days 0:19:37.757
BugCheck 7F, {8, 80050031, 6f8, fffff80002ea2798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 27 09:32:54.257 2010 (GMT-4)
System Uptime: 0 days 1:17:49.005
BugCheck E1, {fffff88001744010, 2, fffffa8005bc9670, fffffa8005bc9680}
Probably caused by : ndis.sys ( ndis!ndisWorkItemHandler+0 )
BUGCHECK_STR:  0xE1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar 24 10:17:38.132 2010 (GMT-4)
System Uptime: 0 days 0:04:45.880
BugCheck 7F, {8, 80050031, 6f8, fffff80002e47798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar 24 10:12:10.078 2010 (GMT-4)
System Uptime: 0 days 0:17:32.826
BugCheck 7F, {8, 80050031, 6f8, fffff80002e4f798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Mar 11 08:48:49.324 2010 (GMT-4)
System Uptime: 0 days 0:02:08.072
BugCheck 7F, {8, 80050031, 6f8, fffff80002e54798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Mar  7 17:00:32.557 2010 (GMT-4)
System Uptime: 0 days 0:16:45.305
BugCheck 7F, {8, 80050031, 6f8, fffff80002e45798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  vsmon.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Mar  7 13:09:08.147 2010 (GMT-4)
System Uptime: 0 days 0:57:32.896
BugCheck 7F, {8, 80050031, 6f8, fffff80002e8e798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar  3 18:48:18.230 2010 (GMT-4)
System Uptime: 0 days 7:25:01.978
BugCheck 7F, {8, 80050031, 6f8, fffff80002e46798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  javaw.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 16 17:32:23.815 2010 (GMT-4)
System Uptime: 0 days 0:24:42.563
BugCheck 3B, {c0000005, fffff80002f62fb9, fffff880029c2740, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+51 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 27 12:00:16.674 2009 (GMT-4)
System Uptime: 0 days 0:00:19.422
BugCheck 3B, {c0000005, fffff80002f60fb9, fffff88005ec0740, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+51 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  autochk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 22 16:50:30.414 2009 (GMT-4)
System Uptime: 0 days 2:45:07.037
BugCheck 1A, {41790, fffffa8002400000, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  schedul2.exe

PS - I lived in Bamberg for 5 years - I love Bayern!!!

 

[Samoth]

Hallo usasma,

wie geht es dir jetzt? I don´t live too far from Bamberg. When you´re next time here in Germany make sure to give me a message - I owe you one!

Thanks for your help so far. We updated the W/LAN driver and I also found the "ASACPI.sys" on the PC and updated it.

We´re testing now...


Cheers
Samoth

PS. Another question: Where can I learn to diagnose such errors like you do it? There are a lot of problems I could solve like that.

 

[usasma]

Well, it's a long process - but you can start right away and work on it as you go.

First, you'll need to run the Debugging Tools for Windows on the memory dump files.
Instructions on that are here: WinDbg Analysis Report
Then, at the bottom of the page is a link to a description of what I do once I've finished running the analysis.

Also, study the following:
- the Help file for the Debugging Tools
- Windows Internals v5
- Advanced Windows Debugging
- and any other debugging references you can get your hands on.

Read everything several times. Each time that you read it you'll find that you understand a bit more.

Then, follow the BSOD threads here and try to analyze them yourself.
If you run into difficulties, post back with specific questions and we'll do our best to answer.

As you can see, there just aren't that many people doing this - so we can use all the help that we can get.

 

[Samoth]

Allright, after updating the drivers for several hardware components there was another crash. Want me to upload the current dump-file?

Thanks again for your help with "How to be a debugger"

 

[Jonathan_King]

Please follow these instructions for enabling driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Then upload the new dmps that were generated. I suggest deleting all the dmps from the folder now, so we know that whatever dmps are in the folder are new, generated after Verifier was turned on.

 

[Samoth]

Hello guys,

I´m working on it. Besides I´m studying so across the week there ist just little time to spend diagnosing computer crashes

I´ll stay in contact.

Take care so far...

Samoth

 

[Samoth]

Hello everybody,

I´ve got an update here: The guy whos PC keeps on crashing gave the thing to a friend for "further analysis" - whitout letting me know. I guess it took him too long until the diagnosis was done. I´m going to leave this case open here, OK? As soon as the computer returns (and is not fixed) I´ll pop up more information for you.

Sorry for the inconvenience :-/.

Read you soon . Cheers!

Samoth

 

[usasma]

Not a problem, we'll be here when and if you need us!

 

[Samoth]

Appreciate that a lot!

 

[Samoth]

Hello again,

just wanted to update you with news: The other guy was running some more tests (one of it was "Prime95") and after a couple of minutes one of the CPU Cores failed. So what they did now, was putting another dualcore-CPU into the system and letting it run again. So far no failures from Prime. Maybe the CPU caused the problem? :-S

Have a good night (it´s 23:30 over here )

Samoth

 

[Jonathan_King]

Great, thanks for the update. It is fully possible CPU caused it.

 

[Samoth]

Hello guys, after a long period, I just wanted to inform you, what happenend with the computer. Maybe this will help some other "customers" . Finally the problem was simply caused by a corrupted Windows-Installation. Can you believe it? The guy just reinstalled Windows since then the computer ist working w/o any errors. Thanks again and always keep in mind, that the installation might cause some errors cheers samoth

 

[Jonathan_King]

Thanks for the report! I'm glad it's all sorted out.