Lots of BSOD's

[Corwyn]

Last week my computer died on me. I thought the Power supply was the culprit unfortunately it had also fried the motherboard so I replaced that, the cpu and memory. New settings can be seen in the system specs. With the new system I started to get a lot of BSOD's some of them were the 'irql no les or equal' and the 'bad spooler header'. Initially I suspected bad drivers or corrupted files. So I reinstalled windows and didn't install any drivers. I'm still getting BSOD's The last 3 were with BCcode 100007e, 1e and 50. I'll Upload the last few minidumps. Also I ran a Memtest 86 it didn't register any faults with the memory.
I could really use some help with figuring out what's wrong with my poor pc.

 

[Tews]

All of your .dmp files point to your ATI graphic driver as the cause for your crashes (atikmdag.sys) Go to ATI's website and download the latest driver for your card...

 

[Corwyn]

Thank you for the quick response.

I'm installing the ati drivers as I type. Let's hope it works.

 

[Corwyn]

Well everything went ok for a few hours and another bsod . For dump see attachment.

 

[Corwyn]

ok. this time with attachment

 

[Corwyn]

And again this morning.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Is it still the graphic driver that is giving me problems?

Thanks for all the help.

 

[reventon]

Hi,

Here is the summary of your BSODs so far:

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 23 22:52:12.616 2010 (GMT+12)
System Uptime: 0 days 10:23:24.990
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 23 12:27:35.362 2010 (GMT+12)
System Uptime: 0 days 2:12:59.110
BugCheck 1000007E, {ffffffffc0000005, fffff88004820cf7, fffff88003d546a8, fffff88003d53f10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 23 06:41:49.484 2010 (GMT+12)
System Uptime: 0 days 0:01:42.232
BugCheck 50, {ffffd88004c370bb, 1, fffff88004c370a7, 7}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+37f0a7 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 23 06:38:47.586 2010 (GMT+12)
System Uptime: 0 days 7:48:38.334
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+3b )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 22 22:49:08.043 2010 (GMT+12)
System Uptime: 0 days 0:43:47.791
BugCheck 1000007E, {ffffffffc0000005, fffff88004f570a4, fffff88003cbd868, fffff88003cbd0d0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 22 08:41:14.513 2010 (GMT+12)
System Uptime: 0 days 4:36:17.261
BugCheck 24, {1904fb, fffff880031b5ee8, fffff880031b5750, fffff80002dad90d}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 22 04:03:31.665 2010 (GMT+12)
System Uptime: 0 days 20:58:50.413
BugCheck 1000007E, {ffffffffc0000005, fffff88004831ca1, fffff88003d3c868, fffff88003d3c0d0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 06:30:35.586 2010 (GMT+12)
System Uptime: 0 days 0:28:21.944
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 06:00:55.056 2010 (GMT+12)
System Uptime: 0 days 0:31:57.430
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88004fbb099, fffff880027787e8, fffff88002778050}
Probably caused by : Rt64win7.sys ( Rt64win7+14099 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16399.amd64fre.win7_gdr.090722-1835
Debug session time: Fri May 21 05:09:19.828 2010 (GMT+12)
System Uptime: 0 days 0:45:45.576
BugCheck A, {fffffa1fffffffe0, 2, 1, fffff80002b0fe89}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/FONT]

Such a wide variety suggests a hardware fault.

The fact that the Graphics card is just about the only device that you have not swapped out, and that a lot of the dump files mention graphics drivers leads me to suspect that the graphics card is broken.

Especially as:

I thought the Power supply was the culprit unfortunately it had also fried the motherboard

That is probably not the only thing it fried.

Regards,
Reventon