BSOD: constant blue screens, many pointing to different places.

[kevawo]

Hello.

I finally gave up all hope trying to solve my problem by myself.

I just built a new computer early last month and everything was fine til a week later when I started getting very random blue screens mostly blaming ntoskrnl, or other windows services. These blue screens didn't seem to have any real pattern and sometimes occurred when playing games either online of offline or just browsing net or being idle.

I have ran SFC /SCANNOW command twice and nothing has shown up both times.

Also, I used a utility called WhoCrashed to help me analyze minidump files and somehow the SF Diagnostic Tool missed out on one of my dumps which I can't seem to find either. But here's what WhoCrashed says:

[FONT=Segoe UI, Arial]On Thu 8/2/2012 1:48:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-21060-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]volmgr.sys[/FONT] (volmgr+0x2C75)
Bugcheck code: 0xD1 (0xFFFFFA7F9ED222E0, 0x2, 0x1, 0xFFFFF88000F08C75)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\volmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft? Windows? Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Volume Manager Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
[/FONT]

I'm really thankful if anyone can help or point me on what to do next.

 

[FredeGail]

Hello kevawo and welcome to Sevenforums.

BSOD Analyse

Events

You basically have tons of failed Windows Updates. Did you manage to get those installed?

• Event[8845]:
    Log Name: System
    Source: Disk
    Date: 2012-07-12T00:47:26.951
    Event ID: 51
    Task: N/A
    Level: Warning
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: Kevin-PC
    Description: 
  An error was detected on device \Device\Harddisk2\DR2 during a paging operation.

  • This error may be causing a camera, USB, or another device connected into the computer. Disconnect any device you're not using during use of the computer. There's also a hotfix called M885464. You can find that in the Windows Update if you haven't got it already. You may also want to try Diagnosing your Hard Drive.

Memtest86+

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.

   Warning

:info: Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

3rd party drivers

360AntiHacker64.sys Thu Jun 14 10:17:06 2012 (4FD99E02)
360AvFlt.sys Wed Jan 11 10:39:30 2012 (4F0D58D2)
360Box64.sys Wed Jun 13 11:05:39 2012 (4FD857E3)
360FsFlt.sys Mon Jul 9 10:45:26 2012 (4FFA9A26)
360netmon.sys Wed May 30 04:01:20 2012 (4FC57F70)

As far as I'm concerned this is your anti-virus, is that correct?

You have a lot of USB 3rd party drivers. I'd be a little careful with those as they intent to produce BSODs if they don't work properly.

Possible fix for defected USB-drivers| Go to Device Manager > Expand the USB list > Uninstall every driver (not device) and Reboot Windows.
Let Windows detect them and reinstall them.

• What kind of USB Devices to you have attached to your computer?

Click Start | Search for 'devmgmt.msc' | Expand all the dropdowns
| Look for :warn:

Report if any.

Conclusion - 3rd party drivers

You have many 3rd party drivers. Sometimes they mess up and you might want to try a Clean Install, and get the stuff you need, and not anything additional.

360AntiHacker64.sys Thu Jun 14 10:17:06 2012 (4FD99E02)
360AvFlt.sys Wed Jan 11 10:39:30 2012 (4F0D58D2)
360Box64.sys Wed Jun 13 11:05:39 2012 (4FD857E3)
360FsFlt.sys Mon Jul 9 10:45:26 2012 (4FFA9A26)
360netmon.sys Wed May 30 04:01:20 2012 (4FC57F70)
a8eriuht.SYS Tue Dec 27 23:30:45 2011 (4EFA4715)
amd_sata.sys Wed Apr 11 16:40:24 2012 (4F8597D8)
amd_xata.sys Wed Apr 11 16:40:27 2012 (4F8597DB)
amdxata.sys Fri Mar 19 17:18:18 2010 (4BA3A3CA)
BAPIDRV64.SYS Fri Dec 2 10:34:18 2011 (4ED89B9A)
cpuz135_x64.sys Wed Sep 21 10:23:41 2011 (4E799F0D)
EtronHub3.sys Wed Jun 13 12:59:07 2012 (4FD8727B)
EtronXHCI.sys Wed Jun 13 12:59:04 2012 (4FD87278)
GEARAspiWDM.sys Mon May 18 14:17:04 2009 (4A1151C0)
hcmon.sys Tue Aug 30 08:05:35 2011 (4E5C7DAF)
Lachesis.sys Fri Oct 16 15:09:12 2009 (4AD87078)
Lycosa.sys Wed Sep 30 06:45:50 2009 (4AC2E27E)
mv91xx.sys Thu Jun 7 05:10:27 2012 (4FD01BA3)
mvs91xx.sys Mon Nov 7 09:58:49 2011 (4EB79DC9)
mvxxmm.sys Thu Jun 7 05:10:13 2012 (4FD01B95)
Mydrivers64A.SYS Thu May 10 15:05:19 2012 (4FABBD0F)
nvhda64v.sys Wed Apr 18 19:07:54 2012 (4F8EF4EA)
nvlddmkm.sys Tue May 15 09:35:36 2012 (4FB20748)
Rt64win7.sys Tue Jun 12 16:00:29 2012 (4FD74B7D)
RTKVHD64.sys Tue Jun 19 10:50:56 2012 (4FE03D70)
RtNdPt60.sys Mon Jul 20 04:27:32 2009 (4A63D614)
sptd.sys Sat Mar 3 17:45:52 2012 (4F524AC0)
usbfilter.sys Sat Mar 31 05:48:56 2012 (4F767EA8)
vmci.sys Wed Jul 27 04:42:09 2011 (4E2F7B01)
VMkbd.sys Sat Jun 9 10:10:17 2012 (4FD304E9)
VMNET.SYS Fri Jul 8 09:43:55 2011 (4E16B53B)
vmnetadapter.sys Fri Jul 8 09:43:56 2011 (4E16B53C)
vmnetbridge.sys Fri Jul 8 09:44:44 2011 (4E16B56C)
vmnetuserif.sys Tue Aug 23 00:35:59 2011 (4E52D9CF)
vmx86.sys Sat Jun 9 11:05:57 2012 (4FD311F5)
vstor2-mntapi10-shared.sys Sat Jul 9 00:31:49 2011 (4E178555)

360AntiHacker64.sys <-- not available on the table
360AvFlt.sys <-- not available on the table
360Box64.sys <-- not available on the table
360FsFlt.sys
360netmon.sys
a8eriuht.SYS <-- not available on the table
amd_sata.sys
amd_xata.sys
amdxata.sys
BAPIDRV64.SYS
cpuz135_x64.sys
EtronHub3.sys
EtronXHCI.sys
GEARAspiWDM.sys
hcmon.sys
Lachesis.sys
Lycosa.sys
mv91xx.sys
mvs91xx.sys
mvxxmm.sys
Mydrivers64A.SYS
nvhda64v.sys
nvlddmkm.sys
Rt64win7.sys
RTKVHD64.sys
RtNdPt60.sys
sptd.sys
usbfilter.sys
vmci.sys
VMkbd.sys
VMNET.SYS
vmnetadapter.sys
vmnetbridge.sys
vmnetuserif.sys
vmx86.sys
vstor2-mntapi10-shared.sys



Best Regards,
Frederik.

 

[kevawo]

Hey there Frederik thanks for your prompt response. I will go ahead and get to work on these.

As for the third party drivers, I believe they're all drivers needed. The ones that start with 360 is my AntiVirus program. The ones that start AMD are for the CPU. I also use VMWare so there are those drivers. And some others are used by Nvidia graphics card. I also have a Razer lycosa/lachesis mouse and keyboard, so those are drivers for that. I wouldn't know which ones to uninstall. The only extra USB device I am using is a Xbox controller for Windows, I will go ahead and unplug that when not using it.

And I can't seem to figure out what a8eriuht.SYS is. Google search does nothing for that driver.

Pertaining to the ones you pointed out in red <-- not available on the table. Can you clarify for me as to why they're not available?

I have also ran devmgmt.msc and no

has come up.

Also, I went into the control panel and checked for Windows Update and there doesn't seem to be any important updates that I haven't installed. I searched for a hotfix named M885464 in the list if updates I have already installed and I can't seem to find it, I did a little google search and it seems as if that hotfix was for Win XP (correct me if I'm wrong). All of my hotfixes and updates starts with KB followed by different numbers (ex. KB2552343). I am using Win 7 Ultimate x64.

I will go ahead with the memtest86+ and post results after.

Again thank you for your help and hope I can get these issues resolved.

-Kevin

 

[FredeGail]

The only extra USB device I am using is a Xbox controller for Windows, I will go ahead and unplug that when not using it.

The Xbox driver for Windows 7 is actually a known BSOD causer in many cases. I'd maybe uninstall it for a trial, and see if anything has changed.

And I can't seem to figure out what a8eriuht.SYS is. Google search does nothing for that driver.

Me neither, it's probably an extension to something. We can ignore that for now.

Pertaining to the ones you pointed out in red <-- not available on the table. Can you clarify for me as to why they're not available?

They're not known to users, and the table is not updated with them. I highlighted them, just to tell you, that you won't be able to see details about those drivers.

Also, I went into the control panel and checked for Windows Update and there doesn't seem to be any important updates that I haven't installed. I searched for a hotfix named M885464 in the list if updates I have already installed and I can't seem to find it, I did a little google search and it seems as if that hotfix was for Win XP (correct me if I'm wrong). All of my hotfixes and updates starts with KB followed by different numbers (ex. KB2552343).

For now it's alright. It was probably because of your Xbox controller that you had connected from time to time in your computer. Event logs can be important and pointless at times, no matter what level of danger they report.

I will go ahead with the memtest86+ and post results after.

Awesome. Memtest86+ is the important troubleshoot you should focus on at the moment. If no errors will come up, I have further troubleshooting we can do.

You're certainly welcome, glad you're updating me.

Best Regards,
Frederik.

 

[kevawo]

Hey there Frederik,

Thanks for your response! I ran memtest86+ for 20 straight hours and it passed with 0 errors. Where should I proceed from here?

Thanks in advance, Kevin.

 

[FredeGail]

Alright Kevawo!

It's time to enable Driver Verifier.

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 "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- 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 locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

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:

Delete these registry keys to stop Driver Verifier from loading (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

Best Regards,
Frederik.

 

[kevawo]

Hey there Frederik, thanks for the prompt response!

First of all, I am willing to give this a try, but first I would like to let you know that my CD-rom does not read CDs at startup for some odd reason (except when I first installed Win 7 at the time I built the PC).

I ran memtest86+ using a USB flash drive (the flash drive is only 2GB). So if anything were to occur and I was not able to boot to Safe Mode, I won't be able to enter System Repair from the boot screen (unless you know of another way).

Should I go ahead with Driver Verifier anyways?

Also when you say backup, do you mean a full back up of everything I have using the Windows 7 Backup Utility?

Thanks in advance!

-Kevin

 

[FredeGail]

So if anything were to occur and I was not able to boot to Safe Mode, I won't be able to enter System Repair from the boot screen (unless you know of another way).

That's quite odd. I do not know any other methods on the top of my head, other than the Recovery Disc. Or you can create your own one, but if you ain't able to boot it's a problem of course.

http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html

Should I go ahead with Driver Verifier anyways?

I would yes. The driver might belong to a device that's bugging your system.

Also when you say backup, do you mean a full back up of everything I have using the Windows 7 Backup Utility?

Just backup the files you'd need, and maybe consider an Image Backup, that'd probably be better.

http://www.sevenforums.com/tutorials/663-backup-complete-computer-create-image-backup.html

Best Regards,
Frederik.