Overclock.net › Forums › Intel › Intel CPUs › SYSTEM_THREAD_EXCEPTION_NOT_HANDLED BSOD yet again. DMP analysis included.
New Posts  All Forums:Forum Nav:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED BSOD yet again. DMP analysis included.

post #1 of 31
Thread Starter 
I've been getting random SYSTEM_THREAD_EXCEPTION_NOT_HANDLED BSODs. At first they were only happening while gaming. I was just browsing Facebook looking at an album while downloading The Witcher 2, and boom, BSOD. This has been an ongoing issue which seemed to have spawned around the time I decided to install my second 5850, or sound card.

Things I have done already.

1. Complete reinstall of Windows.

2. Ran Memtest86, was going strong with no errors after I woke up (11 hours).

3. Ran Prime95 Blend to ensure CPU stability, was going strong after I woke up (11 hours).

4. Reinstalled display drivers. Uninstalled 11.4, restarted, installed 11.5b, restarted.

5. Ran a chkdsk, found no errors or bad sectors.

Someone linked me to this hotfix, from MS. At first I thought it fixed my previous SYSTEM_THREAD_EXCEPTION_NOT_HANDLED BSODs, but it's still here.. and now it's happening while NOT gaming.

I am totally and completely out of ideas. I can't think of anything that can be causing this. I don't believe it's my 2600k overclock. It's 11 hours stable and I'm already pumping 1.35 core voltage into it.

DMP file:
Quote:
On Sun 5/29/2011 9:41:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052911-21637-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x5141)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880012F4141, 0xFFFFF880093A8920, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 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=Segoe UI, Arial]
[/FONT][FONT=Segoe UI, Arial]

[/FONT]
Edited by pjBSOD - 5/29/11 at 3:10pm
post #2 of 31
are the 5850's running at stock ?
Gaming Rig
(13 items)
 
  
CPUMotherboardRAMOS
4790k @ 4.8GHZ z97 sabretooth mark s 290 Win 7 64bit 
KeyboardMouse
Saitek Saitek 
  hide details  
Reply
Gaming Rig
(13 items)
 
  
CPUMotherboardRAMOS
4790k @ 4.8GHZ z97 sabretooth mark s 290 Win 7 64bit 
KeyboardMouse
Saitek Saitek 
  hide details  
Reply
post #3 of 31
Thread Starter 
Quote:
Originally Posted by masonkian;13679670 
are the 5850's running at stock ?

Yes, always have been except for the very few times I tried overclocking the first 5850 I owned. But yes, they're at stock.

Here's my only theory..

My only theory is that my Hard Drive is dying. I mean, I BSOD'd while downloading The Witcher 2 off of Steam, and the % complete went from mid 30s to 18%.

Sounds like corruption to me, no?

Edit: Ran chkdsk, no bad sectors or errors.
Edited by pjBSOD - 5/29/11 at 3:10pm
post #4 of 31
tried new card on its own for abit to eliminate it ?

sound card could be at fault also take it out for abit see if you can replicate the BSOD
Gaming Rig
(13 items)
 
  
CPUMotherboardRAMOS
4790k @ 4.8GHZ z97 sabretooth mark s 290 Win 7 64bit 
KeyboardMouse
Saitek Saitek 
  hide details  
Reply
Gaming Rig
(13 items)
 
  
CPUMotherboardRAMOS
4790k @ 4.8GHZ z97 sabretooth mark s 290 Win 7 64bit 
KeyboardMouse
Saitek Saitek 
  hide details  
Reply
post #5 of 31
Thread Starter 
I have not tried either of those. I see my buddy Ganja in the users viewing! Haha.

I just ran a chkdsk, no errors or bad indexes, so that eliminates my HDD theory.
post #6 of 31
Send me the crash dump E-Peen.

I'll gladly help you figure out what likely is causing it.
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
post #7 of 31
Thread Starter 
Quote:
Originally Posted by GanjaSMK;13679782 
Send me the crash dump E-Peen.

I'll gladly help you figure out what likely is causing it.

If you help me fix this, I seriously wouldn't know how to thank you. I can't take much more of this.

How would I go by sending you the crash dump file? To get that analysis I used a free program called "WhoCrashed", so I don't exactly know how to "officially" view crash files.
post #8 of 31
More voltage imo
post #9 of 31
Thread Starter 
Quote:
Originally Posted by Rucka315;13679822 
More voltage imo

frown.gif I already have 1.35 core voltage going into it.
post #10 of 31
Quote:
Originally Posted by E-Peen;13679808 
If you help me fix this, I seriously wouldn't know how to thank you. I can't take much more of this.

How would I go by sending you the crash dump file? To get that analysis I used a free program called "WhoCrashed", so I don't exactly know how to "officially" view crash files.

Ok, navigate to C:\Windows\Minidump

You'll find a bunch of in there unless you have things set to overwrite the dumps. Send me the latest one you've gotten, either via Megaupload or some other sharing site, or here via PM. thumb.gif
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › SYSTEM_THREAD_EXCEPTION_NOT_HANDLED BSOD yet again. DMP analysis included.