KMODE_EXCEPTION_NOT_HANDLED at random times

[BABYpanda]

Hi all,

Lately I'm experiencing annoying BSODs while just doing my things. It does not happen at a specific time or when I run a specific program. Sometimes it happens 2 times after another, sometimes a few days it's fine and sometimes I just get it randomly 5 times a day (like now).

It is really frustrating, I'm losing the work I done before the BSOD and it is just taking the piss pretty much.

I hope someone is able to help me here, as you are pretty much my last resort. I've tried the most common things myself already like memtest, prime95 etc etc, though it doesn't solve.

I am able to give you all the details you need to help me out, your time is much appreciated.

Thanks in advance.

PS. These BSODs started to appear when I moved all my components to another case. I changed from casing because in my old case the temperature was really high. This one has more fans and better airflow.

 

[BABYpanda]

I got a BSOD a minute ago right after I started Google Chrome.. I really hope someone is able to help me, I'm getting really really frustrated with them.

 

[Arc]

Blue Screen of Death (BSOD) Posting Instructions

 

[BABYpanda]

My apologies, here are the logs.

Note: I just bought new RAM this morning, did a complete reinstall of Windows 7 Ultimate but the blue screens still occur..
I am really desperate as I have no idea what I can do more.. I hope someone is able to tell me what is wrong with this thing..

 

[Arc]

Probably caused by : mouclass.sys ( mouclass!MouseClassServiceCallback+47e )

If you remove the Razer DeathAdder 3.5G and apply any other mouse there, does the BSOD continue? Let us know.

 

[BABYpanda]

Thank you so much for your reply!
I am trying that out immediately. You will hear from me soon.

Again, thanks for your time and support.

 

[BABYpanda]

I had no BSOD for a short period, but unfortunately it happened again.

Here is a new zip file attached. I hope you're able to support me with it - thanks so far )

PS. Right after you said I should try another mouse I plugged my Razer mouse in a back hub USB (3.0). I receive a BSOD. After that I connected a whole different mouse in the front hub (2.0) and receive the last BSOD.

 

[Arc]

Update teh network driver from Realtek (the Win7 and Server 2008 R2 Auto Installation Program one).

Uninstall Daemon tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

See how it goes. Let us know.

 

[BABYpanda]

I removed Daemon Tools, and tried to update the network driver.
When I executed the network driver update it only gave me the options "repair" and "remove". Obviously I did repair, but I am unsure if that updated the driver.

I will keep you updated on the circumstances, so far so good.

 

[Arc]

The instruction is supplied in the zip you downloaded. If you have followed that, the update should be done.

 

[BABYpanda]

I just did another complete reinstall. I first installed the network driver (the one you provided), then I did ALL the windows updates. And I had no BSOD during these.

Right after I installed Catalyst Control Center + Intel Chipset Drivers I got another blue screen. I attached the logs to this post. I think they could be usefull now as I only installed a handful of drivers (no programs at all installed!).

Thanks in advance!!

 

[Arc]

Right after I installed Catalyst Control Center + Intel Chipset Drivers I got another blue screen.

Which drivers you have installed and how?

Asking because the crash dump is not saying anything precisely about the BSOD.

 

[BABYpanda]

I installed latest available catalyst control center driver, which doesn't seem to be causing issues as I restored to an earlier point. I dont currently have a chipset driver installed and no issues so far.

I suspect its the intel chipset driver, because it thrown BSOD at me pretty much after I installed the driver.
The Intel Chipset Driver I installed was V9.3.0.1021.

My chipset info is Intel(r) 7 Series C216, so I have no idea what chipset driver I should install other than that one..

Are you able to provide me a (better) driver which doesn't cause issues for me?
I installed mine from https://www.asus.com/Motherboards/P8Z77M_PRO/HelpDesk_Download/ > Windows 7 64 bit > Chipset > first link (V9.3.0.1021)

 

[BABYpanda]

Here another log of everything.. I really out of ideas..

I think this computer is just completely dead as I've been spending the past couple of days fixing this without any progress. If I only knew what was causing this..

 

[Arc]

Well ......

CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
[COLOR=Red]CurrentSpeed: 3502[/COLOR]

Stop overclocking right now. As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.

How To Clear CMOS (Reset BIOS)
​

Then see how it goes. Let us know.

 

[BABYpanda]

Thanks for your reply!

I didn't even know my pc was overclocked.. There appeared to be a switch on my motherboard called "EPU" and "TPU". I disabled them both and I will see how the PC runs now.

Thanks in advance

 

[BABYpanda]

No blue screen so far - I disabled TPU and seems to work great )

Thanks for your help Arc, you've been great to solve this.
I will see it for a week and if it's doing great I will mark as solved.

 

[Arc]

Welcome. Let us know for any further issue.

 

[BABYpanda]

I will do

Just out of interest: I've always run my system like this (overclocked). Now that it throws issue like thewe, does that mean the processor is unstable / damaged because it doesn't want to be overclocked anymore?

If so - how can I check whether the cpu is healthy or not ?

 

[Arc]

Stress test the Graphics Card using Furmark. It will let you know.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.