BSOD Seemingly At Random, error KMODE_EXCEPTION_NOT_HANDLED

[VistaKing]

Can you manually zip the dmp file ? The dmp file should be in C:\Windows\minidumps

 

[k4nc3r]

Ok, was able to get the .dmp file this time. Thank you for your patience here

 

[k4nc3r]

Can you manually zip the dmp file ? The dmp file should be in C:\Windows\minidumps

I put the last dump in my previous post. Any ideas?

 

[VistaKing]

I am seeing this driver CAHS164.sys

belongs to C-Media Electronics USB Audio Driver

Image name: CAHS164.sys
Timestamp: Thu Jun 16 00:10:06 2011

I believe the driver is for your Headset . Are you using any Headsets?

 

[Pauly]

I havent looked at your dump files but the fact you are experiencing BSODs on a clean install is concerning this is usually indicative of a hardware problem although it is possible you are installing the offending driver shortly after.
Things to try? you have options here and its really up to you, a clean boot would be an easy first step http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html this will boot your system without all your regular startup items, if this doesnt help then you could try good old safe mode - along the same lines but with basic drivers and even less bloat on boot, these are pretty basic steps and shouldnt take long if neither of these help or you just dont want too then you could start proving your hardware
First off if your OCing in anyway stop, return everything to stock settings for the purposes of testing
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
http://www.sevenforums.com/tutorials/433-disk-check.html (windows based check)
Hard Drive Diagnostic Procedure (bootable disk check) using something like SeaTools | Seagate
Next would be some stress tests
http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

A different route to go would be driver verifier as mentioned by arc before but you responded that you couldnt ??
This is sometimes very handy for flushing out faulting drivers (although not always) but will make your system very slow and sluggish as it places increased load on drivers in an attempt to cause another crash
http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[k4nc3r]

I am seeing this driver CAHS164.sys

belongs to C-Media Electronics USB Audio Driver

Image name: CAHS164.sys
Timestamp: Thu Jun 16 00:10:06 2011

I believe the driver is for your Headset . Are you using any Headsets?

Yes I have a Corsair 1500 headset. I would be so darn happy if that were the offender instead of my hardware. Wouldn't it BSOD the moment it gets plugged in though? Let me know what I need to do. thanks!

 

[k4nc3r]

A different route to go would be driver verifier as mentioned by arc before but you responded that you couldnt ??
This is sometimes very handy for flushing out faulting drivers (although not always) but will make your system very slow and sluggish as it places increased load on drivers in an attempt to cause another crash
http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Thanks for the post Pauly, really appreciate the input. I did initially run driver verifier, but as it readily BSOD's on its own without it running, I didn't see the point in having that going. Maybe I'm not understanding the purpose of driver verifier, but I thought it just makes the BSOD occur so you can analyze the dmp files.

I have already done the tests you brought up and haven't had anything pop up from them unfortunately. I'm not overclocking because I just haven't had a stable build to really mess with yet, so I should be good there too. The one thing I haven't tried is doing a clean boot, though I've been mainly in safe mode when I'm communicating in these forums as I don't get BSOD's there and can actually get things done diagnostic-wise.

 

[VistaKing]

Try this driver for your headset

http://www.corsair.com/media/cms/drivers/v1500driver_1-1.exe

 

[k4nc3r]

Should I uninstall any drivers before installing that new one?

 

[VistaKing]

Uninstall the old one before you install the new one .

 

[k4nc3r]

I installed the new driver for the headset and it still BSOD'd. Here's the dmp file.

 

[VistaKing]

Did you update your Graphic Card driver ?

 

[Pauly]

If safe mode works for prolonged periods then thats a good sign, i would recommend you remove the Gigabyte software especially easytune its installed a really old driver on your system (2006) thats not going to help matters, if BSODs are still occuring after that then driver verifier may give us some more clues, i think you may have slightly misunderstood its purpose, its job is to cause stress on drivers in the hope of causing a crash and then if/when it does it can often generate a more accurate dump file that can specify the faulting driver instead of just generalising and blaming the kernel upon which they crashed. It will make the system slow and sluggish but thats the idea and may give us some more info

 

[k4nc3r]

Did you update your Graphic Card driver ?

I just did now, when I formatted the harddrive and reinstalled windows I didn't get the new drivers for my GPU. Though I had all updated drivers on the GPU, I believe, when it was BSODing to begin with. I'll turn on driver verifier when I get home and see if I cant get it to crash again, shouldn't be a problem there. Here's the dump file from last night before I installed newest GPU drivers.

 

[Arc]

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus. All, but not MSC.
5. Apply > OK
6. Accept then restart.

A stop 0x3B is very common, and it is some of the cases very difficult to debug, at is is related to a display driver mostly (as in your case). So we can try to attempt for a most perfect driver installation only. According to Carrona.org,

Cause
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

Install the latest WHQL of the display driver only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Reboot. Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  
• During uninstall and install, accept all the offered reboots.

Also, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% excess is safe.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

 

[k4nc3r]

Ok, sorry for the delay, family came in town.

I cleared out the start up, got rid of all old nvidia drivers, driver swept them, (though I skipped over the chipset ones, wasn't sure what to do there...), re-installed nvidia drivers you showed to select, did the stress test for awhile no issues there, checked the power supply calculator, good there, and everything looks fine on Speccy. The screenshot was just after an hour or so of normal usage that causes the BSOD.

So far I haven't run into any BSOD's yet but I've gone for a week before a BSOD in the past so I'm keeping my fingers crossed that this was the issue. I'll let you know when/if the next one comes. Hopefully this was the magic bullet. On a side note, does that mean I won't be able to do 3D gaming? Can't say I had that in mind, but just curious on the couple of drivers that I didn't install. Thanks a ton for your help again, can't thank you enough here.

 

[k4nc3r]

Well this is strange, I had shut my computer off to go out for awhile and when I came home to turn it on there was a 'Windows recovered from a unexpected shutdown' prompt. I didn't see a bluescreen at all, but it says there was one. Here's the dump file.

 

[Arc]

Intel RST AHCI driver is a failing module here.

fffff880`0374dd88  fffff880`0106325bUnable to load image \SystemRoot\system32\DRIVERS\[URL="http://www.carrona.org/drivers/driver.php?id=iaStor.sys"]iaStor.sys[/URL], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=iaStor.sys"]iaStor.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=iaStor.sys"]iaStor.sys[/URL]
 iaStor+0x2e25b

Download and install this particular versionof Intel Rapid Storage Driver:

• Version: 11.2.0.1006
• Date: 06/11/2012

Also, seeing frequent storage related errors.

fffff880`0374ea08  fffff880`0151d6df fltmgr!FltpDispatch+0xcf
fffff880`0374e978  fffff880`0151ebcf fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f

I think you should not use Marvell 91xx SATA 6G Controller. (SCSI Controller)

ITEM | VALUE
Model | WDC WD1002FAEX-00Z3A0
SCSI Bus | 0
SCSI Logical Unit | 0
SCSI Port | 0
SCSI Target ID | 0

So this driver should not be present there. Uninstall Marvell. Then follow Drivers - Clean Left over Files after Uninstalling

Let us know the situation when done.

 

[k4nc3r]

Ok, I got the intel driver and got rid of the Marvel driver. I know we were having issues with that before, I completely forgot when I reinstalled windows that it would pop back up. I'll run driver verifier tonight to see if I can get it to BSOD. thanks again

 

[k4nc3r]

Damn. BSOD while playing CIV 5. Here is the zip. Have run into a build this buggy without have something wrong with the hardware itself? Thanks man