random BSOD

[nilV]

Hello, over the last week or so my computer has been randomly BSODing and I was wondering if anyone could help point my in the right path to fixing the problem.

The problem got very serious about an hour ago, it bsod almost right after I rebooted and then did it again immediately. After that it kept saying it need to check the consistency of C: and would keep crashing while trying to do that(I assume the constant crashing had corrupted my install or something).

Blue screen view is reporting the problem centering around "ntkrnlpa.exe" and "halmaccpi.dll" with the common errors being "PAGE_FAULT_IN_NONPAGED_AREA" "IRQL_NOT_LESS_OR_EQUAL" and "DRIVER_IRQL_NOT_LESS_OR_EQUAL" I attached 3 of the most recent dmp files created. Any advice on this would be of huge help as I don't want to have to start replacing parts for nothing. Thanks in advance.

 

[usasma]

First, please run these diagnostics as you have time:

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)

There is no clear blame assigned by the memory dumps, so let's also give Driver Verifier a shot right off the bat. Please follow 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

Here's a summary of the BSOD's:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan 23 19:05:07.094 2010 (GMT-5)
System Uptime: 0 days 1:13:05.577
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
BugCheck D1, {deadfa6c, 2, 0, 94055d9d}
Probably caused by : Unknown_Module_84fdb530 ( Unknown_Module_84fdb530>+f07a86d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan 23 19:45:23.321 2010 (GMT-5)
System Uptime: 0 days 0:38:49.679
BugCheck A, {839ff664, 2, 1, 8289dce5}
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+c9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan 23 19:48:48.214 2010 (GMT-5)
System Uptime: 0 days 0:01:12.572
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System