BSOD Errors

[Natural20]

So my computer has decided that whenever I want to run a high memory programme it's going to crash.

Problem started around Sunday, to my knowledge there has been no change in my drivers or anything like that. There has been no change to my hardware which to my knowledge has been working without error up until this point.

Most common problem that shows on the BSOD is Driver IRQL not_less_or_equal. Often the thing doesn't even get to BSOD and just freezes up before even managing to restart. When it does go to BSOD it often can't dump memory and create a log, hence explaining log sparcity.

Attached are minidump files from recent errors in a single zip.

Any help would be appreciated.

 

[usasma]

The dump files are spread out - and this usually indicates a hardware problem.
As such, please do these tests:

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)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Also, please update this older driver as it's known to cause BSOD's: ASACPI.sys Thu Aug 12 22:52:52 2004
It belongs to the Asus ATK0110 ACPI Utility (and can also be found in their PCProbe and AISuite utilities).

Please post back if the BSOD's continue (after running the diagnostics) and we'll run some tests.

Here's a summary of the BSOD's:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sun Jan 17 20:18:37.846 2010 (GMT-5)
System Uptime: 0 days 12:33:51.347
BugCheck 1000008E, {c0000005, 828df888, 8e613b60, 0}
Probably caused by : memory_corruption ( nt!MiGetNextNode+20 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 12:40:48.457 2010 (GMT-5)
System Uptime: 0 days 0:23:14.455
BugCheck A, {ffffffe8, 2, 1, 828bcbbd}
Probably caused by : usbaudio.sys ( usbaudio!USBCaptureProcessPin+dc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 12:46:53.596 2010 (GMT-5)
System Uptime: 0 days 0:00:19.593
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 14:25:54.632 2010 (GMT-5)
System Uptime: 0 days 1:35:28.505
BugCheck D1, {34, 2, 0, 8ac4661a}
Probably caused by : ndis.sys ( ndis!ndisQueuedMiniportDpcWorkItem+38 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Thu Jan 21 16:48:33.135 2010 (GMT-5)
System Uptime: 0 days 8:54:03.133
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
BugCheck 1000008E, {c000001d, 8f516d96, 82b31c28, 0}
Probably caused by : ntkrpamp.exe ( nt!PoIdle+538 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[Natural20]

I have now done the diagnostic tests and still suffer from BSODs. Both diagnostic tests have come up negative. I'm thinking it's a problem with the Motherboard, although that doesn't explain why the error is more frequent when I use more memory.

 

[usasma]

Can we see the latest BSOD's?
Once you upload them, please run Driver Verifier according to these directions:

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 "Low Resource Simulation" and click "Next"
- 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.

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

 

[Natural20]

Attached is the new minidump just in case my computer crashes again. Will be performing the other tests today.

 

[Natural20]

Have just run the driver test. The machine couldn't get past the windows startup before BSODing. I hope these are the logs as I had to system restore using startup recovery to make it work.

 

[usasma]

Please ensure that Driver Verifier is turned off.

This is the infamous ASACPI.SYS BSOD.
Please update this driver: ASACPI.sys Thu Aug 12 22:52:52 2004

From post #2 in this topic:

Also, please update this older driver as it's known to cause BSOD's: ASACPI.sys   Thu Aug 12 22:52:52 2004
It belongs to the Asus ATK0110 ACPI Utility (and can also be found in their PCProbe and AISuite utilities).

Summary of the BSOD:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Mon Jan 25 09:05:52.368 2010 (GMT-5)
System Uptime: 0 days 0:00:15.412
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System

 

[Natural20]

7 was telling me that the driver I had installed for that piece of hardware was the most up to date so instead I uninstalled the hardware to see if that sorted the problem.

Will update if I get more BSODs.

 

[Natural20]

Removed driver. Got an error. Computer didn't bluescreen, just restarted without it and then crashed on startup. This happened multiple times.

Started up in safe mode and have system restored to "Direct X installed" haven't have a bluescreen happen yet. This reversed multiple windows updates that had happened in between the two.

 

[Natural20]

Driver appears to have come back and caused a bluescreen following system restore. I have tried multiple times to update the driver but to no avail. It says the driver i downloaded is not compatible with the hardware when I manually try to have it download and says it is fully up to date when I attempt to automatically install the driver update.

Edit: I now cannot find the device in device manager. It seems to have been replaced with an unknown device.

 

[Natural20]

Emerged unknown device was the same one. I went ahead and uninstalled it. Things seem alright. Will keep posting.

 

[usasma]

Windows Update and the Update driver function in Device Manager do not provide you with the most current drivers. This is explained in more detail here: Mark's Blog : The Case of the Crashed Phone Call

The ASACPI.SYS 2004 and 2005 versions are known to cause BSOD's in Windows 7. There is a 2009 version that is stable - and it's in the ATK0110 ACPI Utility, the PCProbe utility, and the AISuite utility at the Asus support website.

 

[Natural20]

Driver is updated to the 2009 version as far as I can tell. I've had a bluescreen where my computer has had a memory problem, dumped and then for some reason not created a minidump file (not sure why) and a second restart which just involved the computer crashing to a blackscreen, trying to restart and getting stuck at the motherboard's initial startup page (before it detects drives)

Edit: These problems have continued and I've had to system restore it back to Tuesday when it seemed to be working alright. Trying to reupdate the drivers. I don't understand why the computer still kept restarting even though the drivers were up to date, 2009 and all that. My suspicion is that there's a windows update that's causing the problem.

Edit2: I have now finally managed to completely uninstall the ASACPI.sys thing, currently testing to see if I bluescreen. Have turned off windows update as I suspect that it is reinstalling the thing.

 

[Natural20]

Alright, uninstalling ASCPI.sys just caused more problems. So I reinstalled, patched it up to the windows 7 version from 2009 and still get bluescreens. Despite full memory dumps minidump files of these problems have not been created. They ranged from MEMORY MANAGEMENT errors to IRQL_NOT_LESS_OR_EQUAL.

Help would be appreciated.

 

[usasma]

One thing at a time please.
Is the ASACPI.SYS file still installed or is it uninstalled? If installed, is it the 2009 version?

Please zip up and post the memory dump files that you've had since you last uploaded them.
Also, please let us know where (in relation to the dump files) that you installed/uninstalled/changed the ASACPI.SYS files.

 

[Natural20]

Currently having trouble doing this as the computer is bluescreening inside 5 minutes from startup and then requires a 10 minute break to work again. Will try getting dump files to you.

 

[usasma]

Any easier if you try Safe Mode with Networking (tap F8 repeatedly just before the Windows Splash Screen shows up)?

The 10 minute rest is required before you can reboot? I'd suspect an overheating issue with that (and it won't get any better in Safe Mode with Networking). This also leads us back to the beginning where we suspected a hardware issue.

If that's the case, open up the case and make sure that it's clean (don't use a vacuum or an air compressor - they'll cause damage). Also make sure that the fans are working (plug it in and turn it on with the side off - just don't stick your fingers inside the case when it's turned on).

Leave it on until it blue screens/shuts itself down. Unplug it from the wall, hold onto the metal of the case with one hand. With the other hand, CAREFULLY feel around inside the case. Figure out where the hot spots are without getting burnt!

Once that's done, you can test further by leaving the side off the case and pointing a house fan into the computer. This should (if it's an overheating issue) increase the amount of time before it crashes. Let us know how all of this works out.