BSOD on Startup and IQRL_NOT_OR_LESS_EQUAL

ace123 · 03 Apr 2011

Hello there, I have a problem on my hands here but I'm pretty scared to do anything since I'm not that savvy when it comes to these things.

First of all some background on my computer (if they matter):
Running Windows 7 Ultimate 32 bit (build 7600)
Pentium Dual Core 2.60 GHz but overclocked to 2.79 at the moment
Crappy 160 GB SATA hard drive (I think)
It is a custom built computer, built in summer of 09. I ran vista on it at first but I think that I installed 7 on it within a few months. I've never once had a problem with it before.

Background on the problem:
I brought this computer to college for gaming purposes mostly. I quit for a while, leaving this computer unused for about a month. A week ago I used it to write up a report and it was fine. Then day before yesterday I tried playing World of Warcraft on it. It ran fine for an hour then WoW experienced a critical error then it restarted the game. Another 30 minutes of playtime went by and the critical error happened again, this time 10 seconds later I blue screened.

The screen said DRIVER_IQRL_NOT_OR_LESS_EQUAL blah blah blah and dumped the memory or whatever that was. Then it restarted but blue screened the second it booted back up with the same error. Then it restarted again but this time it didn't get past the windows logo and just looped a constant restart-crash cycle at the logo. When startup repair is done, it says "it worked" and that the cause was "Registry is Corrupt" however no amount of startup repair fixes it.

The next morning I turned it on and it worked for an hour, but once again started blue screening. Now I'm running it on safe mode with networking and it doesn't seem as if any system files are bad since it started.Anways, sorry if that was long but thought that someone could get something useful from my info.

zigzag3143 · 03 Apr 2011

ace123 said:

Hello there, I have a problem on my hands here but I'm pretty scared to do anything since I'm not that savvy when it comes to these things.

First of all some background on my computer (if they matter):
Running Windows 7 Ultimate 32 bit (build 7600)
Pentium Dual Core 2.60 GHz but overclocked to 2.79 at the moment
Crappy 160 GB SATA hard drive (I think)
It is a custom built computer, built in summer of 09. I ran vista on it at first but I think that I installed 7 on it within a few months. I've never once had a problem with it before.

Background on the problem:
I brought this computer to college for gaming purposes mostly. I quit for a while, leaving this computer unused for about a month. A week ago I used it to write up a report and it was fine. Then day before yesterday I tried playing World of Warcraft on it. It ran fine for an hour then WoW experienced a critical error then it restarted the game. Another 30 minutes of playtime went by and the critical error happened again, this time 10 seconds later I blue screened.

The screen said DRIVER_IQRL_NOT_OR_LESS_EQUAL blah blah blah and dumped the memory or whatever that was. Then it restarted but blue screened the second it booted back up with the same error. Then it restarted again but this time it didn't get past the windows logo and just looped a constant restart-crash cycle at the logo. When startup repair is done, it says "it worked" and that the cause was "Registry is Corrupt" however no amount of startup repair fixes it.

The next morning I turned it on and it worked for an hour, but once again started blue screening. Now I'm running it on safe mode with networking and it doesn't seem as if any system files are bad since it started.Anways, sorry if that was long but thought that someone could get something useful from my info.

You have the trifeckta

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

2-SPTD.SYS the second biggest cause used by daemon tools and alcohol120

Remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller when you're done:DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

3-Symantec remove and replace with microsoft security essentials
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/

ace123 · 03 Apr 2011

Thank you for your response. So far I did the 1st step with the ASUS driver. It went through smoothly.

For the second step I uninstalled anything that had to do with Daemon tools or any CD mounting things of that nature. However, you said to use the uninstaller. I used it and it the little dialog box with the options "Install" "Uninstall" and "Cancel" came up, but the uninstall option wasn't lit up, only the install was. It says "No SPTD Version was detected, Select action to be performed", I'm assuming step two is good?

Step three however, I'm stuck on. I can't go to the "Add/Remove Programs" and remove it in safe mode at least. I haven't tried using the removal tool for the software, but it only prompts me do remove anything that's norton. I know norton is a company related to symantec but I don't have anything "norton" installed on my machine so I doubt that it will do anything. It gives me an error message saying:

"Symantec AntiVirus 9 or later must be removed before continuing"

EDIT: I got out of safe mode and finally got my computer booted. I removed Symantec manually, which worked in regular mode and didn't in safe mode. Since I updated that ASUS file, removed daemon tools, and Symantec all looks well again. is there anything else I could do to keep it from BSODing?

mgorman87 · 03 Apr 2011

Continue using your computer as you normally would. If it crashes again upload a new report.

ace123 · 03 Apr 2011

Since I did all of the above, it worked for around an hour. Then while just casually browsing the internet it blue screened again with the IQRL_NOT_OR_LESS_EQUAL. I restarted and it worked for another 5 minutes and got the same thing. I've attached the files for the report for this last crash. Currently running in safe mode

mgorman87 · 03 Apr 2011

One of your system dumps was a DRIVER_OVERRAN_STACK_BUFFER.

A driver overran a stack-based buffer (or local variable) in a way that would have overwritten the function's return address and jumped back to an arbitrary address when the function returned.
This is the classic "buffer overrun" hacking attack. The system has been brought down to prevent a malicious user from gaining complete control of it.

I would like you to run a rootkit scanner, malware scan, and online virus scan to rule out any potential virus'.
How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)?
HouseCall - Free Online Virus Scan - Trend Micro USA
Malwarebytes' Anti-Malware: Malwarebytes

Code:

Security Processor Loader Driver
ROOT\LEGACY_SPLDR\0000
This device is not present, is not working properly, or does not have all its drivers installed

To see if you can reinstall this driver go to Start > Device Manager look for Yellow marks you might find Security processor Loader driver Right click and click on Update driver.

Also run a System File Check - SFC /SCANNOW Command - System File Checker

Please report back the results of those tests.

Once that's completed please update your computer to SP1 - How to update to SP1

Code:

L1E62x86.sys Sun Aug 23 01:06:36 2009 (4A90CE5C)

Update your Atheros network driver - here

Code:

nvlddmkm.sys Fri Jul 09 17:15:14 2010 (4C379162)

Update your video card drivers - here

Code:

RivaTuner32.sys Tue Jul 17 15:13:33 2007 (469D14DD)

Uninstall Riva Tuner - Known issues w/ Win 7

Code:

sptd.sys     Sun Feb 27 14:28:51 2011 (4D6AA5F3)

Daemon Tools is still being shown as installed on your system. Please uninstall Daemon Tools through Add/Remove programs and then run the SPTD removal tool found here.

If you still experience BSOD after doing everything I listed above then please enable driver verifier.
Driver Verifier - Enable and Disable

Summary of dumps

Code:

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Apr  1 22:44:49.037 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:29.723
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+2e3 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: Smc.exe
FAILURE_BUCKET_ID: 0x8E_nt!ExDeferredFreePool+2e3
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P5KPL-CM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Apr  1 22:39:00.110 2011 (UTC - 4:00)
System Uptime: 0 days 0:36:35.448
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+31 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7f_d
PROCESS_NAME: Wow.exe
FAILURE_BUCKET_ID: 0x7f_d_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+31
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P5KPL-CM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Apr  1 22:44:49.037 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:29.723
Probably caused by : STACK_BUFFER_OVERRUN
DEFAULT_BUCKET_ID: STACK_BUFFER_OVERRUN
BUGCHECK_STR: 0xf7
PROCESS_NAME: System
FAILURE_BUCKET_ID: STACK_BUFFER_OVERRUN_MISMATCH_GSCOOKIE_nt!KiDispatchException+17c
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P5KPL-CM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Apr  2 12:17:04.751 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:47.437
Probably caused by : memory_corruption ( nt!MmZeroPageThread+2e1 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xA_nt!MmZeroPageThread+2e1
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P5KPL-CM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Apr  2 11:31:39.811 2011 (UTC - 4:00)
System Uptime: 0 days 0:51:00.481
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : hidusb.sys ( hidusb!HumReadReport+ef )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_hidusb!HumReadReport+ef
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P5KPL-CM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Apr  1 22:59:08.862 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:08.548
Probably caused by :
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: wermgr.exe
FAILURE_BUCKET_ID: 0x50_nt!CmpKcbCacheLookup+18f
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P5KPL-CM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Apr  3 21:23:57.848 2011 (UTC - 4:00)
System Uptime: 0 days 0:59:46.533
Probably caused by : win32k.sys ( win32k!FreeObject+2e )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: firefox.exe
FAILURE_BUCKET_ID: 0xA_win32k!FreeObject+2e
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P5KPL-CM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun Apr  3 21:31:34.246 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:50.932
Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+138 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: 0xA_nt!MiRemoveAnyPage+138
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P5KPL-CM

Code:

891a4000 891ec000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8e019000 8e073000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
89200000 89212000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
892b9000 892c2000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
957f9000 957fa6c0   ASACPI   ASACPI.sys   Wed May 13 07:11:32 2009 (4A0AAAE4)
8e00e000 8e00f440   AsIO     AsIO.sys     Wed Dec 21 03:55:21 2005 (43A91879)
8928d000 89296000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
89296000 892b9000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
89919000 89920000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
8e000000 8e00e000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
836b3000 836bb000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
9a4a5000 9a4be000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
96560000 9657e000   cdd      cdd.dll      unavailable (00000000)
898f3000 89912000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
836fd000 837a8000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8989c000 898c1000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
836bb000 836fd000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
89582000 895df000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
89400000 8940d000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
9a550000 9a553480   cpuz133_x32 cpuz133_x32.sys Tue May 11 05:59:25 2010 (4BE92A7D)
903dc000 903e9000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8e177000 8e1db000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
8e1db000 8e1f3000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
8e16b000 8e177000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8988b000 8989c000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
903b9000 903d2000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
903f4000 903fd000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
903e9000 903f4000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
90200000 90211000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
903d2000 903dc000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
95684000 9573b000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
9573b000 95774000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
892f6000 89307000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
892c2000 892f6000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
895ed000 895f6000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
89859000 8988b000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D)
89762000 89793000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
89858000 89858680   giveio   giveio.sys   Wed Apr 03 22:33:25 1996 (316334F5)
83426000 8345d000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8f897000 8f89bc00   hamachi  hamachi.sys  Thu Feb 19 05:36:27 2009 (499D362B)
95774000 95793000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
8f955000 8f968000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
90211000 90217480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
8f94a000 8f955000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
9a420000 9a4a5000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
89850000 89858000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
89600000 89618000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
89262000 89269000   intelide intelide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17)
899ce000 899e0000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
9c73f000 9c765000   ipnat    ipnat.sys    Mon Jul 13 19:54:28 2009 (4A5BC934)
8e1f3000 8e200000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
80bac000 80bb4000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8f8a8000 8f8dc000   ks       ks.sys       Mon Jul 13 19:45:13 2009 (4A5BC709)
8956f000 89582000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
83600000 83625000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
95793000 957a3000   L1E62x86 L1E62x86.sys Sun Aug 23 01:06:36 2009 (4A90CE5C)
8f9d9000 8f9e9000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
8f973000 8f98e000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
8362a000 836a2000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
8f93f000 8f94a000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
899ef000 899fc000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
8f968000 8f973000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
89277000 8928d000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
9a4be000 9a4d0000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
9a4d0000 9a4f3000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
9a4f3000 9a52e000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
9a52e000 9a549000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
89972000 8997d000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
89000000 89008000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
89544000 8956f000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8e161000 8e16b000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
89840000 89850000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
89307000 893be000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8f824000 8f82f000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
8f82f000 8f851000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
8f92e000 8f93f000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
8e0cb000 8e0d9000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
8e073000 8e0a5000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
893be000 893fc000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8997d000 8998b000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8e157000 8e161000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
83016000 83426000   nt       ntkrpamp.exe Sat Feb 27 02:33:35 2010 (4B88CACF)
89415000 89544000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
89912000 89919000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
95682000 95683040   nvBridge nvBridge.kmd Fri Jul 09 17:10:11 2010 (4C379033)
94c04000 95681dc0   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:14 2010 (4C379162)
8e0ac000 8e0cb000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
897e5000 897fd000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E)
837d2000 837e3000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
9a549000 9a550000   parvdm   parvdm.sys   Mon Jul 13 19:45:29 2009 (4A5BC719)
837a8000 837d2000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
89269000 89277000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
895df000 895ed000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
9a554000 9a5eb000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
9038a000 903b9000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
836a2000 836b3000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8f80c000 8f824000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
8f851000 8f869000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
8f869000 8f880000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
8f880000 8f897000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
8e116000 8e157000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
8f89c000 8f8a6000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
8995a000 89962000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
89962000 8996a000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8996a000 89972000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
89813000 89840000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
9c765000 9c767380   RivaTuner32 RivaTuner32.sys Tue Jul 17 15:13:33 2007 (469D14DD)
8f9a8000 8f9d9000   RMCAST   RMCAST.sys   Mon Jul 13 19:53:39 2009 (4A5BC903)
8f9e9000 8f9fc000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
9a5eb000 9a5f5000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
89800000 8980a000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
8e0d9000 8e0f3000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
897e3000 897e4480   speedfan speedfan.sys Sun Sep 24 09:28:47 2006 (4516880F)
897db000 897e3000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
9c607000 9c671000   spsys    spsys.sys    Mon May 11 12:37:10 2009 (4A085436)
8908e000 891a4000   sptd     sptd.sys     Sun Feb 27 14:28:51 2011 (4D6AA5F3)
9c6ee000 9c73f000   srv      srv.sys      Tue Dec 08 03:05:37 2009 (4B1E08D1)
9c69f000 9c6ee000   srv2     srv2.sys     Mon Jul 13 19:14:52 2009 (4A5BBFEC)
9c671000 9c692000   srvnet   srvnet.sys   Tue Dec 08 03:05:06 2009 (4B1E08B2)
8f8a6000 8f8a7380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
89619000 89762000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E)
9c692000 9c69f000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
899a2000 899ad000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
8998b000 899a2000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8e106000 8e116000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
96530000 96539000   TSDDD    TSDDD.dll    Mon Jul 13 20:01:40 2009 (4A5BCAE4)
899ad000 899ce000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
8f8dc000 8f8ea000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
90218000 90219700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
899e0000 899ef000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
8f8ea000 8f92e000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
957ae000 957f9000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
957a3000 957ae000   usbuhci  usbuhci.sys  Mon Jul 13 19:51:10 2009 (4A5BC86E)
891f5000 89200000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
89920000 8992c000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
9021b000 9038a000   viahduaa viahduaa.sys Thu Jul 09 23:04:40 2009 (4A56AFC8)
8992c000 8994d000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
89793000 8979b380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
837e3000 837f3000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
89217000 89262000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8979c000 897db000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8e0f3000 8e106000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8994d000 8995a000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
8900f000 89080000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
89080000 8908e000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8e0a5000 8e0ac000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
962d0000 9651a000   win32k   win32k.sys   Sat May 01 10:49:02 2010 (4BDC3F5E)
891ec000 891f5000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
8f98e000 8f9a8000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)

Unloaded modules:
898c1000 898ce000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
898ce000 898d9000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
898d9000 898e2000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
898e2000 898f3000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000

ace123 · 03 Apr 2011

I ran the malware programs twice to make sure. TDSS showed nothing. HouseCall found a trojan which was deleted. Malwarebytes found "Hijack.Shell.Gen and it was deleted. Also Malwarebytes found Adware.Agent and deleted it

I went to the device manager and found nothing out of the ordinary. None of the exclamation marks that denote problems. So the "security processor loader driver" was not there.

Updated both Atheros and NVIDIA drivers with no problem.

Riva tuner was removed without problems.

As for Daemon Tools, I can't find it on my program files or add/remove programs. Whenever I run the SPTD remover it asks for "Install" or "Uninstall" however, I can't click uninstall and it says: "No SPTD Version was detected, Select action to be performed" EDIT: This was in safe mode, in regular mode the uninstallation for SPTD went through fine. However daemon doesn't show up still on my program files or add/remove

I ran the sfc /scannow and it couldn't repair some files. I ran the
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.tx command and got a file telling me the errors. I attached this on here.

For some reason I can't get the automatic updates on windows to give me SP1. I can't download it from the Microsoft Website due to the bandwith restrictions that the school places on my internet.

Also, my brother (the person who built the computer) has told me that he didn't not use a genuine key. And now the computer is showing a "this copy of windows is not genuine" in the lower right of the desktop. Will this cause me problems?

Will a legit reformat (as a last resort) make these blue screens stop?

mgorman87 · 04 Apr 2011

If you are still experiencing BSOD after doing everything listed above then you will need to follow the instructions on how to enable driver verifier. Once you've enabled it continuing using your computer and when you get a crash upload a new report.

ace123 · 04 Apr 2011

I ran windows with the verifier and managed to run the entire day from 9AM Monday to 12AM Tuesday with no blue screen. Finally I just got one and here is the results of the report.

In the verifier I only checked files that weren't manufactured by windows as the tutorial said. This made my computer have a few sound bugs and made me slightly slower, but no other problems.