Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Seemingly At Random, error KMODE_EXCEPTION_NOT_HANDLED


05 Apr 2013   #1

Windows 7 Home 64 Bit
 
 
BSOD Seemingly At Random, error KMODE_EXCEPTION_NOT_HANDLED

Well, I have to admit I've been away from PC's for about the last decade and I decided to get back into PC Gaming. It's been pretty daunting, and I'm still getting back into the swing of things (I've been using a Mac for about the last ten years.) The build I've done has seen its share of troubles, the newest being a constant, seemingly random BSOD. Sometimes I can be up and running for about a half hour playing a game or just listening to music, other times it BSOD's right after boot up. I can't seem to make it past an hour or so and there never seems to be a logic behind the crash as I'm not doing anything very intensive. All drivers should be up to date, I had to bring it in for repair because of a dead power supply and the tech there updated all drivers, but the problem could still be in that area based on the crash report. If anyone could lend a hand that'd be great and if I've left anything out just let me know and I'll provide as much info as possible. Thanks!

Here's the report from WhoCrased:

On Fri 4/5/2013 12:09:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040413-19999-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032A44FE, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Here's my Build

PC/Desktop
Custom Build
Windows 7 Home 64 Bit
Inet i5 3570K
Gigabyte Z77X-UD4H
Corsair Vengeance 8GB 1600 DDR3
EVGA GeForce GTX580
WD 1TB SATA 6 GB/s 7200 RPM
Corsair CX750
CoolerMaster HAF X
Razer BlackWidow
Logitech Gaming Mouse
Cable Internet
Antivirus
Norton
Browser
Chrome

My System SpecsSystem Spec
.

06 Apr 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Your BSOD is caused by Norton Internet Security.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 215a8a, 6, 100000000000001}

*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
Probably caused by : IDSvia64.sys ( IDSvia64+3d250 )

Followup: MachineOwner
---------
Description here ..... Driver Reference Table - IDSvia64.sys

Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Moreover, AVG exists there, and making the system crash on itself.
Code:
fffff880`0374e418  fffff880`049dbe34Unable to load image \SystemRoot\system32\DRIVERS\avgidsdrivera.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgidsdrivera.sys
*** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
 avgidsdrivera+0x24e34
It might be a leftover of an earlier AVG installation? Uninstall AVG using AVG Remover.

You have only one HDD .... so RAID setup is not needed there. Marvell's drivers are poor, often problematic. Though it is already determined that it is norton that is causing the Ntfs.sys error there, better you get rid of Marvell, too.
Uninstall it ..... Marvell 91xx driver. then follow Drivers - Clean Left over Files after Uninstalling to remove the leftover, if any.

Update the drivers of your Razer products ..... http://www.razersupport.com/index.ph...nloads&_a=view
Code:
Start Menu\Programs\Razer\Razer BlackWidow 
Start Menu\Programs\Razer\Razer Synapse 2.0
Let us know the results.
My System SpecsSystem Spec
06 Apr 2013   #3

Windows 7 Home 64 Bit
 
 

Arc,

Thanks a ton for the quick reply! I removed Norton and AVG (didn't realize I hadn't gotten rid of it), also got rid of the Marvell driver as well. Though eventually I do want to get a second HDD, what would I have to do so that it doesn't cause a problem down the road when I want the second one?

The only downside is that I tried updating the razer blackwidow and not it doesn't work any more. I've tried troubleshooting and I just can't get it working. Apparently it's common with that brand so I'm going to return it.

Everything seems to be working fine and I haven't had a BSOD since I did what you said. Thank you so much for the help, can't say how nice it is to have help on these issues. Saved me money time and a headache.
My System SpecsSystem Spec
.


06 Apr 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Quote   Quote: Originally Posted by k4nc3r View Post
Arc,

Thanks a ton for the quick reply! I removed Norton and AVG (didn't realize I hadn't gotten rid of it), also got rid of the Marvell driver as well. Though eventually I do want to get a second HDD, what would I have to do so that it doesn't cause a problem down the road when I want the second one?
Nothing special is to be done .... just plug the SATA and power in, tighten the HDD screws, that's all

Quote   Quote: Originally Posted by k4nc3r View Post
The only downside is that I tried updating the razer blackwidow and not it doesn't work any more. I've tried troubleshooting and I just can't get it working. Apparently it's common with that brand so I'm going to return it.
You may try to roll back the driver.
Device Manager - Roll Back Driver

Quote   Quote: Originally Posted by k4nc3r View Post
Everything seems to be working fine and I haven't had a BSOD since I did what you said. Thank you so much for the help, can't say how nice it is to have help on these issues. Saved me money time and a headache.
Good to know
Now observe what happens there. If you find that the issue is over, mark this thread as solved. If there are more BSODs, execute the diag tool again
My System SpecsSystem Spec
09 Apr 2013   #5

Windows 7 Home 64 Bit
 
 

Just wanetd to say thanks again for the quick help. Unfortunately I'm having some issues again. I was recently playing BioShock after a few days worth of no BSOD's when all of sudden it starts happening again. It looked like one of the issues was AVG, which I had purchased after having problems with Norton BSODing my computer. I've uninstalled that, though it would be nice to have it back, but it still is BSODing after the uninstall. I'm at a loss here, so any help would be great. Here's the new grab all. Thanks again
My System SpecsSystem Spec
09 Apr 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Intel rapid storage is failing here.
Code:
fffff880`08e561c8  fffff880`0128325bUnable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
 iaStor+0x2e25b
Download and install this particular version of Intel Rapid Storage Driver:
Also, as a caution, Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.


Let us know the results.
My System SpecsSystem Spec
16 Apr 2013   #7

Windows 7 Home 64 Bit
 
 

Ok, sorry to constantly annoy here but I've run into another series of BSOD's. I installed that verison of the driver and it kept BSODing. I did the memory test, and there were no issues. After that it was nearly a week of smooth sailing. I played games that really taxed my system and had no problems so I thought I was out of the woods. Then I try to turn my computer off last night and it BSOD'd me. So it seems to be a pattern of it being okay for about a week and then it starts crashing. It's entirely possible that I didn't analyze the memory correctly, I'm still a newb really. I'm at a loss as usual. Here's the WhoCrash Log and a new grab. Thanks again!

On Tue 4/16/2013 10:54:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041613-15724-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x99, 0x215A8A, 0x6, 0x100000000000001)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
My System SpecsSystem Spec
16 Apr 2013   #8
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

information   Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

warning   Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
17 Apr 2013   #9

Windows 7 Home 64 Bit
 
 

I wasn't able to run driver verifier, but it crashed it crashed immediately and over and over when I got home today. Basically within a minute of start up it BSOD's. Here's the WhoCrashed message and also the newest dump files. It looks like its back to the old system service exception again. I'm 8 days away from the date that I can set up call tags without restocking fees for any hardware I've purchased so I'm a bit anxious to get this solved, or atleast understand it better. I appreciate all the help, it's really been huge to have this resource so kudos to all :}

On Wed 4/17/2013 9:57:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041713-78452-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003541173, 0xFFFFF88006798DA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
My System SpecsSystem Spec
18 Apr 2013   #10
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

My System SpecsSystem Spec
Reply

 BSOD Seemingly At Random, error KMODE_EXCEPTION_NOT_HANDLED




Thread Tools



Similar help and support threads for2: BSOD Seemingly At Random, error KMODE_EXCEPTION_NOT_HANDLED
Thread Forum
Solved BSOD at seemingly random intervals error 0x0000003B BSOD Help and Support
BSOD seemingly at random, error 0x000000d1 BSOD Help and Support
Daily BSOD, seemingly random error messages BSOD Help and Support
Seemingly random BSOD - didn't manage to get the error code BSOD Help and Support
BSOD Error 0x00000f4 Seemingly random BSOD Help and Support
Seemingly Random BSOD (System Exception Error) BSOD Help and Support
Solved Random BSOD, error 0x0000001e KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 06:59 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33