BSOD Help: Second attempt

nbittel · 31 Jul 2011

I posted here about a month ago with a BSOD problem. I was told to test my memory which I did and no errors were found. The BSOD seemed to go away so I did not pursue it further. Unfortunately, it has returned and the error code inside the BSOD seems to be a bit different than my old one.

There doesn't seem to be any direct cause for this, so far as I can tell, as it is happening randomly. It's happened while gaming, surfing the net, and even overnight.

So, here I am once again asking for help, I have no idea what to do next.

I would greatly appreciate any help anyone could provide. I've attached all of the necessary items based on the sticky.

My system specs are as follows:

Windows 7 Home Premium 64 OEM
CPU: Intel Core i7 950 3.06GHz
Motherboard: ASUS Sabertooth X58
Memory: 6GB DDR3 1600MHz
Graphics Card: NVIDIA GeForce GTX 580 1.5GB
Sound Card: Integrated

The system is less than a year old, maybe 8 months. I have not resinstalled Windows.

Again, I appreciate any help that can be offered, this has become quite frustrating.

usasma · 31 Jul 2011

One of the memory dumps points to aswSP.SYS - a component of your Avast protection.
Also, I wonder if the Advanced System Care is interfering with it (I'm not familiar with this program).
Please, at a minimum, uninstall both programs - then replace the Avast with a freshly downloaded copy.

If the BSOD's keep up, please reset the system to default values (no overclock) and see if that stops the problems. The dump files show that the system is rated at 3.070 gHz and is overclocked to 3.703 gHz

You also have a driver named lirsgt.sys that dates from 2006 - way too old for Win7! Please uninstall the program that it belongs to (it's a part of a copy protection scheme from an older program).

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


mv91xx.sys            Fri Dec 25 01:45:39 2009 (4B345F93)
mvxxmm.sys            Fri Dec 25 01:45:15 2009 (4B345F7B)
amdxata.sys           Fri Mar 19 12:18:18 2010 (4BA3A3CA)
SmartDefragDriver.sys Wed Feb 23 03:37:56 2011 (4D64C764)
nusb3xhc.sys          Thu Apr 22 21:34:36 2010 (4BD0F92C)
AsIO.sys              Mon Aug 03 03:03:16 2009 (4A768BB4)
ASACPI.sys            Wed Jul 15 23:31:29 2009 (4A5E9F11)
GEARAspiWDM.sys       Mon May 18 08:17:04 2009 (4A1151C0)
nvhda64v.sys          Tue May 10 05:41:18 2011 (4DC9083E)
LGBusEnum.sys         Mon Nov 23 20:36:48 2009 (4B0B38B0)
nusb3hub.sys          Thu Apr 22 21:34:35 2010 (4BD0F92B)
LHidFilt.Sys          Tue Aug 24 13:21:36 2010 (4C73FFA0)
LMouFilt.Sys          Tue Aug 24 13:21:43 2010 (4C73FFA7)
dump_pciidex.sys      Mon Jul 13 19:19:47 2009 (4A5BC113)
lirsgt.sys            Sun Jan 29 06:13:28 2006 (43DCA358)
xusb21.sys            Thu Aug 13 18:10:17 2009 (4A848F49)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-25849-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 19:31:16.085 2011 (UTC - 4:00)
System Uptime: 0 days 5:58:15.053
BugCheck D1, {ffffffffffffffff, 2, 0, ffffffffffffffff}
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+d8f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!ExDeferredFreePool+d8f
Bugcheck code 000000D1
Arguments ffffffff`ffffffff 00000000`00000002 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0603   
BiosReleaseDate = 10/29/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz"
MaxSpeed:     3070
CurrentSpeed: 3703
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-18907-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 13:21:56.862 2011 (UTC - 4:00)
System Uptime: 0 days 11:08:26.830
BugCheck D1, {ffffffffffffffff, 2, 0, ffffffffffffffff}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1251 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  PolarClock3.sc
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!ExDeferredFreePool+1251
Bugcheck code 000000D1
Arguments ffffffff`ffffffff 00000000`00000002 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0603   
BiosReleaseDate = 10/29/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz"
MaxSpeed:     3070
CurrentSpeed: 3703
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

karlsnooks · 31 Jul 2011

Uninstall Avast.

Install MSE (link in my sig)

nbittel · 06 Aug 2011

Update: I am still having problems although the frequency has decreased significantly. I was starting to think we had it beat but today I was greeted with another BSOD only slightly different than the last.

I removed Avast and replaced it with AVG. I also removed Advanced System Care. I updated the lirsgt.sys file listed above.

I know it was suggested that I reset my system to default values but I would like to leave that as a last resort. I did not OC this system myself and am not all that comfortable fooling with it unless absolutely necessary.

I have attached another set of reports.

Once again, I really appreciate all of the help, worst case is I am already in better shape than I was this time last week.

usasma · 06 Aug 2011

I understand your reluctance to remove the overclock (and that you may not be able to get it back).
So, let's try this...
Remove the side of the case and point a house fan into the case.
Run the computer normally to see if this decreases the problems.
If it does, that means it's likely caused by heat - which is a by-product of the overclock.

But first, please try this:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool" and "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Finally, I'd suggest familiarizing yourself with the BIOS section of your owners manual (it' downloadable from the Asus website here: http://dlcdnet.asus.com/pub/ASUS/mb/...rtooth_X58.pdf )

Once you know about the BIOS settings, then check in your BIOS to see what settings are different - and those are the settings for your overclock (there's a lot of them, so jot notes in the owner's manual). We can then adjust them one-at-a-time to see if we can fix things that way (and we won't remove the overclock then).

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080611-28267-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Aug  6 10:52:38.914 2011 (UTC - 4:00)
System Uptime: 2 days 3:55:15.867
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+1f3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!RtlDispatchException+1f3
Bugcheck code 00000050
Arguments fffff880`03393300 00000000`00000000 fffff800`032b4113 00000000`00000000
BiosVersion = 0603   
BiosReleaseDate = 10/29/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz"
MaxSpeed:     3070
CurrentSpeed: 3703
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

usasma · 06 Aug 2011

If it's heat that's causing problems, we may note some problems with your Hard Drive or RAM.
Please run these free, bootable diagnostics as you have time:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)
There are also free, bootable antivirus disks at this link: Free Online AntiMalware Resources