BSOD

kenlinmelb · 03 Dec 2010

Hi I have a windows 7 x64 running and getting random BSODs. I have done standard memory test. Swapped out video card and reinstalled Windows several times. It an IRQL_NOT_LESS_OR_EQUAL error. Any help would be greatly appreciated. Really at my wits end.

System Specs
AMD Athlon II 620 2.6GHz
2x2 GB Cosair XMS3
1TB WD Caviar Green
Was running Gigabyte ATI Radeon 4870
Now running Gigabyte nVidia 9600GT
Gigabyte GA-MA-770T UD3P
LG DVD Burner
Antec Earthwatts 500W PSU

Jonathan_King · 03 Dec 2010

Hello, and welcome!

The dumps are all the same, except for the latest one, which blames hardware.

I suspect SPTD may be the cause here. Remove Daemon Tools, and then remove SPTD with this tool: http://www.duplexsecure.com/download...t-v174-x64.exe

Code:

sptd.sys      Sun Oct 11 16:55:14 2009 (4AD24632)
aept8e8n.SYS  Tue Jul 14 17:12:55 2009 (4A5CF4D7)
af8axedg.SYS  Tue Jul 14 17:12:55 2009 (4A5CF4D7)
ak45dp5p.SYS  Tue Jul 14 17:12:55 2009 (4A5CF4D7)
am2mqzgt.SYS  Tue Jul 14 17:12:55 2009 (4A5CF4D7)
azi3myur.SYS  Tue Jul 14 17:12:55 2009 (4A5CF4D7)
ambx41w6.SYS  Tue Jul 14 17:12:55 2009 (4A5CF4D7)
apm5dhs6.SYS  Tue Jul 14 17:12:55 2009 (4A5CF4D7)
aoufm9bk.SYS  Tue Jul 14 17:12:55 2009 (4A5CF4D7)

Also, run a disk check with Data Lifeguard Tools.

...Summary of the dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec  3 04:05:04.214 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:42.665
Probably caused by : hardware ( nt!KiCancelTimer+4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec  3 01:47:58.818 2010 (UTC - 5:00)
System Uptime: 0 days 0:12:44.629
Probably caused by : win32k.sys ( win32k!TimersProc+197 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!TimersProc+197
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec  3 01:34:36.400 2010 (UTC - 5:00)
System Uptime: 0 days 0:15:38.210
Probably caused by : win32k.sys ( win32k!TimersProc+197 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!TimersProc+197
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec  2 04:53:33.975 2010 (UTC - 5:00)
System Uptime: 0 days 3:05:46.785
Probably caused by : win32k.sys ( win32k!TimersProc+197 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!TimersProc+197
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec  1 03:05:24.285 2010 (UTC - 5:00)
System Uptime: 0 days 0:45:13.721
Probably caused by : win32k.sys ( win32k!TimersProc+197 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!TimersProc+197
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 25 07:53:34.643 2010 (UTC - 5:00)
System Uptime: 0 days 0:26:54.469
Probably caused by : win32k.sys ( win32k!TimersProc+197 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!TimersProc+197
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 25 07:17:29.410 2010 (UTC - 5:00)
System Uptime: 0 days 0:07:07.236
Probably caused by : win32k.sys ( win32k!TimersProc+197 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!TimersProc+197
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 25 07:09:37.493 2010 (UTC - 5:00)
System Uptime: 0 days 3:30:41.319
Probably caused by : win32k.sys ( win32k!TimersProc+197 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!TimersProc+197
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

kenlinmelb · 03 Dec 2010

Thanks for the quick reply Jonathan. Just formatted my system for the umpteenth time. Gonna take it slow this time. maybe one driver a day and check for stability. I can't replicate the crash because its so random. so gonna hold off installing daemon tools for a while. Thanks for the tip!

Jonathan_King · 03 Dec 2010

You're welcome.

I think it's also worth it to test the hard drive, as your dumps remind me of previous ones where hard drive was the cause.

I suggest that you use the manufacturer's tool, Data Lifeguard Tools, to test the hard drive.

WD Support / Downloads / SATA & SAS / WD Caviar Black

kenlinmelb · 03 Dec 2010

Cheers mate. passed with quick test. Should i do the extended test as well?

Jonathan_King · 03 Dec 2010

It never does hurt, although you may want to do the test overnight, as it can take a long time. I recall the extended test running for 8+ hours on a drive we suspected of failure.

kenlinmelb · 03 Dec 2010

Thanks so much. Seems to be running quite well atm. But everytime i think i have fixed it then BAM. hehe. Will update in a few days. What software do you use to analyse mini dumps. I used the one on the microsoft developers site and it didn't tell me much. maybe you got more out of it then I did.

Jonathan_King · 03 Dec 2010

I use Windbg for my dump analysis: Windows Debugging Tools and Symbols for Driver Developers: Getting Started

The commands I use:

Code:

!analyze -v; lmntsm

That will show all the info you see in my dump summaries.

kenlinmelb · 03 Dec 2010

Thanks!

kenlinmelb · 03 Dec 2010

No luck still BSOD just after i installed windows update, found something quite interesting. All the updates says pending after I restarted the computer a few times. and getting same error in all of them. seems like windows update cannot complete updates for some reason. Any clues?