Blue Screen of Death IRQL

[Serthure]

Hello there. I've been using Windows 7 for a good while now, and since I've upgraded my PC components, many BSOD's have started to happen. While I have reason to think it's my RAM, I've already cleaned everything and no more sluggishness problems occurred.

I've been having these IRQL_NOT_LESS_OR_EQUAL Blue Screens lately and I read around the web that this is usually a faulty driver.

I do think my drivers are all up to date/working normally, but it's getting a bit of a bore to have these every 2 or 3 days.

Can you please help me out? I'll post a file to help you help me

This Windows is x64, and it's a Retail Version. The OS's age is around 4-5 Months, and the Hardware is variable, but most of it is less than one year old, except the Hard Drive and Disk Drives, both of which are around 5-6 years old.

View attachment 166685

 

[Jonathan_King]

Hello,

Start by uninstalling Daemon Tools, as it uses SPTD. When done, remove SPTD itself with the tool found here: DuplexSecure - Downloads

I saw your thread here: Help with Memory Parts (2 x TW3X4G1333C9A) - The Corsair Support Forums

Has anything changes since then? The thread ended without a conclusion. Try restoring the original RAM configuration, see if the BSODs quit.

...Summary of the dumps:

[font=lucida console]
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Debug session time: Tue Jul 12 04:37:18.897 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:54.740
Probably caused by : ntkrpamp.exe ( nt!NtOpenKey+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID:  0x1_SysCallNum_bd_nt!NtOpenKey+0
BiosReleaseDate = 02/24/2009
SystemProductName = Inspiron 530
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 00:52:58.826 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:53.731
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+110 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+110
BiosReleaseDate = 02/11/2011
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 17 03:57:11.491 2011 (UTC - 4:00)
System Uptime: 2 days 11:46:44.457
*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
*** WARNING: Unable to verify timestamp for asmtxhci.sys
*** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
Probably caused by : asmthub3.sys ( asmthub3+37b1 )
BUGCHECK_STR:  0xC5_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xC5_2_asmthub3+37b1
BiosReleaseDate = 02/11/2011
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul 14 15:43:47.705 2011 (UTC - 4:00)
System Uptime: 0 days 17:40:06.611
*** WARNING: Unable to verify timestamp for asmtxhci.sys
*** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
Probably caused by : asmtxhci.sys ( asmtxhci+1a763 )
BUGCHECK_STR:  0x4E_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_7_asmtxhci+1a763
BiosReleaseDate = 02/11/2011
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 11 18:03:28.846 2011 (UTC - 4:00)
System Uptime: 3 days 3:38:06.751
Probably caused by : Npfs.SYS ( Npfs+7f54 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  palemoon.exe
FAILURE_BUCKET_ID:  X64_0x3B_Npfs+7f54
BiosReleaseDate = 02/11/2011
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul  8 13:58:41.717 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:25.623
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireFastMutex+1a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Au_.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExAcquireFastMutex+1a
BiosReleaseDate = 02/11/2011
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul  8 13:51:24.567 2011 (UTC - 4:00)
System Uptime: 0 days 13:13:29.457
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireFastMutex+1a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Au_.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExAcquireFastMutex+1a
BiosReleaseDate = 02/11/2011
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul  7 23:44:22.230 2011 (UTC - 4:00)
System Uptime: 0 days 13:30:42.135
*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
Probably caused by : asmthub3.sys ( asmthub3+104f1 )
BUGCHECK_STR:  0xC1_32
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_asmthub3+104f1
BiosReleaseDate = 02/11/2011
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Wed Jul  6 14:19:07.071 2011 (UTC - 4:00)
System Uptime: 1 days 3:34:03.976
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+202845 )
BUGCHECK_STR:  0xC1_32
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  palemoon.exe
FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nvlddmkm+202845
BiosReleaseDate = 02/11/2011
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Serthure]

Hello, and many thanks for your reply.

About the thread at Corsair, yes some stuff has changed.

I basically changed the speeds of the RAM on the BIOS from 9-9-9-24 to 10-10-10-24, and I also upped the voltage a little bit, from 1.5 to 1.6 as they told me to. That really took care of a few Blue Screens I used to have that I thought were memory-related, such as "SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION", and really improved loading speeds in games and general OS speed.

About Daemon Tools, I've already uninstalled that as I was able to find that some of the blue screens I used to have were related to them (I used verifier.exe to check them and to narrow down the problem).

I've changed from Daemon Tools to Alcohol 120% version, and I think it uses SPTD aswell. Still, I'll do as you told me. I'll uninstal Alcohol aswell and remove SPTD and see if anything changes.

By the way, the Blue Screens have been happening lately rather randomly. Sometimes after logging in, other times after 2 days with my pc turned on, other times from 3 to 3 days.

Waiting for a reply, and thanks for your time

 

[Serthure]

UPDATE: I just got another BSOD, this time with the error "The Video Scheduler has encountered an unexpected fatal error". This looks like a Graphics Card problem, but I monitor my gfx card religiously and it always behaved nicely.

Have I just been unlucky enough to buy multiple broken parts?

 

[Jonathan_King]

You might still try restoring the original RAM configuration and see if it helps any. Also, if you have a spare graphics card or could borrow one, that would be great.

Run each of the three Prime95 tests: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

 

[Serthure]

I do have a spare graphics Card, and I've already ran Prime95 many times.

What am I expecting for results? Sometimes the 4th core always fails right from the start, and sometimes the program can run fine for hours.

You think my graphics card is at fault here?

 

[Jonathan_King]

I'd suspect RAM is the cause first, though CPU is also possible.

That "video scheduler" error sounds like a bad video card, but it's hard to say. The only thing we can do is replace parts and watch the results.

 

[Serthure]

I think I'll just replace everything then... I don't have any spare DDR3 DIMMS, so if I want to replace memory I'd have to replace motherboard and CPU aswell... Guess it's back to the store then..