Sign in with
Sign up | Sign in
Your question

Random BSOD - System Thread Exception Not Handled

Tags:
  • Windows 7
Last response: in Windows 7
Share
March 25, 2014 12:14:25 PM

Hi everyone,

First of all here's my rig:

Intel i7 4770K @ stock clock + CM hyper 212evo
MSI z87-gd65 mobo
16GB GSkill 1866MHz RAM (4x4)
Sapphire Radeon 7870OC
120GB Samsung EVO SSD
1 TB WD Caviar Black + 1 TB Seagate + 1 TB Samsung HDDs
Thermaltake Toughpower 750W psu
Carbide 400R case + couple of case fans
Win 7 x64 Ultimate

Been using this system for a while but just two days ago I had my first BSOD. And today the second one. I was just idling on the desktop.

I've downloaded Blue Screen Viewer (BSV) and found out that the error name is System Thread Exception Not Handled

BSV saying that the first one is caused by pci.sys and the second one is caused by ndis.sys.

Also ntoskrnl.exe is involved.

Any idea what should be the real cause?

Also I can copy paste the logs if you tell me which part of the dump log you need.

Looking forward to hear from you guys. Thank you

Best

More about : random bsod system thread exception handled

March 25, 2014 12:29:48 PM

To find out the cause I need you to copy the dump files onto the desktop. Compress them into a .zip archive then upload them to a website like www.mediafire.com then post the link.
m
0
l
Related resources
March 25, 2014 1:55:36 PM

Any idea?
m
0
l
March 25, 2014 2:09:57 PM

Right, you appear to have issues with your USB 3.0 Extensible Driver. Can you please update it here:

https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y...

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80003582f21, fffff88003393618, fffff88003392e70}

Unable to load image \SystemRoot\system32\DRIVERS\iusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
Probably caused by : pci.sys ( pci!PciDispatchPnpPower+146 )

fffff880`04a12000 fffff880`04ad5000 iusb3xhc T (no symbols)
Loaded symbol image file: iusb3xhc.sys
Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
Image name: iusb3xhc.sys
Timestamp: Fri Mar 29 12:36:19 2013 (51558AC3)
CheckSum: 000C59AC
ImageSize: 000C3000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

EDIT

You also have a problem with your Killer E2200 Ethernet controller driver. Can you please update it by following this link:

http://www.mypcdrivers.com/results/download.php?item_id...

(It's the Killer e2200 PCI-E Gigabit Ethernet Controller (NDIS 6.20) option.)

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88001504780, fffff88009e35198, fffff88009e349f0}

Unable to load image \SystemRoot\system32\DRIVERS\e22w7x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e22w7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys
Probably caused by : e22w7x64.sys ( e22w7x64+9241 )

fffff880`04a00000 fffff880`04a27000 e22w7x64 T (no symbols)
Loaded symbol image file: e22w7x64.sys
Image path: \SystemRoot\system32\DRIVERS\e22w7x64.sys
Image name: e22w7x64.sys
Timestamp: Wed Mar 20 21:35:41 2013 (514A2BAD)
CheckSum: 00031967
ImageSize: 00027000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
m
0
l
March 25, 2014 2:22:26 PM

I haven't been using any USB3 device for a long time. But I'm updating it right away.

Is that the thing that giving me the two BSODs?

Update: Also updating the NIC driver.
m
0
l
March 25, 2014 2:44:16 PM

Updates done.

How did you find these are the cause of the BSODs. Is there another software to debug the dumps?

I'm also wondering why I haven't been experiencing these BSODs before? Been using the same drivers for months. But now two blue screens in a short period of time. Was just updated the gpu driver recently.

Do I also need to do memtest? Or is it certain that it's not memory related?

I'll also keep you updated if I have any BSOD or not in upcoming days.
m
0
l
March 25, 2014 3:37:20 PM

I use some software called Windows Debugger which is pretty advanced so if you aren't that familiar with how windows internals work and why certain BSODs happen then I would just stick to bluescreenview or whocrashed. If you are technically inclined and you are really interested like me and know some basic knowledge of BSODs then I would highly recommend Windbg.

No, you shouldn't need to run a memory test as there are no indications of failing ram or pool corruption.
m
0
l
March 25, 2014 4:08:59 PM

Allright, thanks a lot again. :) 

I'll keep you updated.
m
0
l
March 29, 2014 12:24:00 PM

Hey again TheMooMooTV

Just got another BSOD 5 mins ago. I was just surfing on the net, Facebook etc...

This time a different Bug Check String: System Service Exception

And a different cause: wind32k.sys

I've uploaded the dump file

http://www.mediafire.com/download/4u7j5eq35kpv5gr/dump2...

Any idea what is the real cause this time?

m
0
l
March 30, 2014 11:46:04 AM

hmm, Driver Verifier should be able to help us out on this one.
Enable it by following these intructions.

WARNING, before doing the following you should change your startup programs because I've had numerous cases where it will BSOD as soon as it starts up, even in safe mode. Can you follow these instructions.

1. Open the Start Menu.
2. In the search line, type msconfig and press Enter.
3. If prompted, click on Continue for the UAC prompt, or type in the administrator's password.
4. Click on the Startup tab.
5. disable all programs that are unnecessary. DON'T DISABLE YOUR ANTI VIRUS.


1. Start typing verifier.exe into the start menu, and open Verifier.
2. Select "Create custom settings (for code developers)", and hit Next.
3. Make sure Standard settings, Force pending I/O requests, and IRP Logging are selected, and hit Next.
4. Select "Select driver names From a list", and hit Next.
5. Click on "Provider" at the top to sort the list by manufacturer; select all drivers not provided by Microsoft Corporation, Macrovision or Unknown.
6. Click finish and restart your PC.
m
0
l
March 31, 2014 6:09:22 AM

TheMooMooTV said:
hmm, Driver Verifier should be able to help us out on this one.
Enable it by following these intructions.

WARNING, before doing the following you should change your startup programs because I've had numerous cases where it will BSOD as soon as it starts up, even in safe mode. Can you follow these instructions.

1. Open the Start Menu.
2. In the search line, type msconfig and press Enter.
3. If prompted, click on Continue for the UAC prompt, or type in the administrator's password.
4. Click on the Startup tab.
5. disable all programs that are unnecessary. DON'T DISABLE YOUR ANTI VIRUS.


1. Start typing verifier.exe into the start menu, and open Verifier.
2. Select "Create custom settings (for code developers)", and hit Next.
3. Make sure Standard settings, Force pending I/O requests, and IRP Logging are selected, and hit Next.
4. Select "Select driver names From a list", and hit Next.
5. Click on "Provider" at the top to sort the list by manufacturer; select all drivers not provided by Microsoft Corporation, Macrovision or Unknown.
6. Click finish and restart your PC.


Thanks for the answer TheMooMooTV

Unfortunately I've installed a fresh windows yesterday to see what happens.

But during the installation I got another BSOD with bug check IRQL_NOT_LESS_OR_EQUAL

Then I had to install from scratch.

It really gets annoying and I feel a little deperate.

I start suspecting from the ram. Did a memtest86 for 14 hours but no error.

It's just really random so far. 2 or 3 days without any hiccups then a BSOD, and I have no idea how to troubleshoot this...

Any idea what else should I do?
m
0
l
April 1, 2014 8:37:49 AM

Alright, it's either a device driver compatibility issue or a hardware fault.
Please download Prime95 and run it for around 2 hours. Then if no errors are found please run IntelBurnIn test on the default setting.
Can you also download and run Furmark to stress test your graphics card, let us know the temperature and leave the test running for around 30 minutes.
m
0
l
April 9, 2014 6:44:49 AM

Hello again.

I've upgraded to Win8.1 pro. No hiccups for almost a week but then today I had another BSOD around 1 hour after I start my computer.

Here's the new dump. http://www.mediafire.com/download/t4au6q62f5nhwvg/dump3...

And also I've already done a 4-5 passes of memtest86 without an error.

Also I'm sure that I'm not having an ovrheating problem since my cpu temperatures under heavy load is around 50-55C.

I start suspecting a memory issue but still not sure and this is so annoying. I feel a bit desperate right now...
m
0
l
April 9, 2014 12:20:37 PM

Right, you are getting memory corruption, can you run memtest86 but please run it for at least 8 passes.
If you get no errors then please enable driver Verifier again, it should be the same set up on Windows 8.
If you get errors then your RAM is faulty, replace it.
But move your RAM around the DIMM slots in the motherboard as sometimes a faulty motherboard slot is the cause and not the RAM modules themselves.
m
0
l
April 9, 2014 3:02:31 PM

Right, I will do that. Thanks.

I'll keep you updated.
m
0
l
October 12, 2014 9:37:31 AM

TheMooMooTV said:
Alright, it's either a device driver compatibility issue or a hardware fault.
Please download Prime95 and run it for around 2 hours. Then if no errors are found please run IntelBurnIn test on the default setting.
Can you also download and run Furmark to stress test your graphics card, let us know the temperature and leave the test running for around 30 minutes.


Hello TheMooMooTV, my computer is crashing and after search online I found this thread. I try to run Prime95 but when it start it crash after 5-10seconds. I don't know what is the problem because every time it crashes it's a different message. I don't know if you can help me but here it's the Dump file: https://mega.co.nz/#!T4JEnTzL!4GxHCcMxvdBJs5rsLJcgDbE8pNkgfFFteQbwCsYj03s

Let me know if you can find out what is the problem. Thanks.

m
0
l
!