Windows 7: Kmode_exception_not_handled

rippe · 07 Jan 2013

Hello, I'm new to these forums and im lost with my BSOD issue, tried to find solved issues but no luck.

I've installed new set of ram to my computer a week ago, that's when the BSOD's started happening randomly during normal operation. I've tried to use my old RAM sticks but for some reason the blue screens kept happening (maybe I installed in different slots than before?). I've ran memtest86 without problems, i have run system file check without errors, i reinstalled windows 7, i've updated the latest bios, downloaded latest drivers for hardware and bunch of other little tweaks i have tried. Nothing works and I'm running out of ideas. I can buy new hardware but first i need to know which piece is broken (If this is happening because of my hardware).

The bluescreens happen when i use some application like browsing random website or playing some FPS games or phoning with skype and they seem to have different causes everytime. KMODE_EXCEPTION_NOT_HANDLED, NTFS_FILE_SYSTEM, PFN_LIST_CORRUPT, SYSTEM_SERVICE_EXCEPTION, SYSTEM_THREAD_EXCEPTION... One thing is common with all of them. They all are revolving around ntoskrnl.exe with other system files.

Here's the latest crash copied via BlueScreenView

010713-19702-01.dmp
7.1.2013 21:55:24
KMODE_EXCEPTION_NOT_HANDLED 0x0000001e
ffffffff`c0000005
fffff800`0328b1e1
00000000`00000000
ffffffff`ffffffff
aswSnx.SYS
aswSnx.SYS+d71d8
x64
ntoskrnl.exe+7efc0
C:\Windows\Minidump\010713-19702-01.dmp
4
15
7601
302
534

I'd appreciate any help I can get.

My setup is:
memory: KHX1600c9d3k2/8gx
OS: Windows 7 home premium
Board: M4A785TD-V
CPU: AMD phenom II X4 965
PSU: 550w (corsair maybe?)
GPU: GeForce GTX 460
Hardrive: 500gb Serial ATA

**x BlueRobot** · 07 Jan 2013

Remove (at least to test):

Code:

Start Menu\Programs\avast! Free Antivirus

Install and perform full scans with:

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system.

You can also view this thread for a complete free and lightweight security protection combination:

Good and Free system security combination.

Remove:

Code:

Start Menu\Programs\ASUS\Cool & Quiet

Remote control programs are known to cause problems such as BSODs, it's best to disable the program within the BIOS and then remove the program entirely.

ASUS®

Code:

BugCheck 4E, {7, 50a6b, ff000000000000, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3727b )

Code:

Usual causes:  Device driver, memory

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

Driver Verifier - Enable and Disable

More Help and Information with Driver Verifier - Using Driver Verifier to identify issues with Drivers

Memory:

RAM - Test with Memtest86+

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

rippe · 07 Jan 2013

Ok, im uninstalling avast, getting rid of registry traces with ccleaner and installing microsoft security essentials for now. I'll also remove cool'n'quiet once i restart my pc.

I also thought about the driver verification but last time i tried to do that, the driver verificator did not launch. I selected the option according to a guide i found and the verificator asked me to restart my computer to begin the verification. I did that but once i got back, nothing happened, just a normal windows boot (does it run on the background or something?).

I'll do another memtest when i go to bed, let it run again over night. Last time it did not report any problems, but it was only 2 passes.

I'll get back to you.

P.S i run malware software on quick scan, nothing.

**x BlueRobot** · 07 Jan 2013

It should run in the background I believe, and I wouldn't use ANY registry cleaner, as it can do serious damage to the Windows operating system and the registry itself.

rippe · 07 Jan 2013

Ok i try to avoid registry tampering.

another update: I noticed that i had my dual ram in wrong slots. They were in A1 A2 slots when they needed to be A1 B1 slots and now CPU-z identifies them as DUAL memory. Anyways just another tweak that could affect on stability.

rippe · 08 Jan 2013

another update: I let the memtest86+ run for full 8 rounds and 0 errors founds. That leaves only the driver verification left, and i dont think it is running in the backround at the moment..

rippe · 08 Jan 2013

It seems to be stable for now, but i've gotten my hopes up too soon before so ill get back once i have some bluescreen data to show

I'll be back within 2 days to mark this one solved or new bluescreen codes

**x BlueRobot** · 08 Jan 2013

That's good to know

rippe · 09 Jan 2013

NOT SOLVED

Had another blue screen today. It was stable for a long time but i still have problem with random sudden crashes.

Here is the latest bluescreenview paste

010913-34928-01.dmp
9.1.2013 17:28:54
SYSTEM_SERVICE_EXCEPTION
0x0000003b
00000000`c0000005
fffff800`0319ebd1
fffff880`0b630720
00000000`00000000
HTTP.sys
HTTP.sys+794c720
x64
ntoskrnl.exe+7efc0
C:\Windows\Minidump\010913-34928-01.dmp
4
15
7601
302
482

Hmm. I had similar BSOD with same bug code and caused driver just a few hours ago when i placed my PC back to the shelf where i keep my pc. It was on and may have gotten small vibration when i landed it. So i suspect there may be loose contacts somewhere, maybe ram isnt fitted perfectly to the slot?

I attached the dump files. does the error still indicate bad ram? should i try to fasten the RAM sticks to DIMM slots? or is it a driver problem?

**x BlueRobot** · 09 Jan 2013

Code:

BugCheck 3B, {c0000005, fffff8000319ebd1, fffff8800b630720, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+471 )

Code:

Usual causes:  System service, Device driver, graphics driver, memory

Have you looked for any updates for your graphics driver?

Code:

nvlddmkm.sys Sat Dec 01 03:24:02 2012 (50B97852)

Have you ran Driver Verifier for least 24 hours?

Other crash was Stop 0x7E, but did not provide much information like Stop 0x3B, here's the summary of common causes for 0x7E:

Code:

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

Have you checked for any BIOS updates:

Code:

BiosVendor = American Megatrends Inc.
BiosVersion = 2105   
BiosReleaseDate = 07/23/2010

Check inside the case of the computer for any loose or damaged components, and make sure everything is fully connected. Clean any dust carefully from the fans and the ports on the motherboard.[code]

Overclocking -
I recommend if you are overclocking any hardware, that you reset these values within the BIOS to their default values in order to increase the stability of your system.

Graphics Card:

NVIDIA/AMD Video Card - Test with OCCT

Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components.

It's also best to run the full scans for the security programs I provided.

Windows 7: Kmode_exception_not_handled

Kmode_exception_not_handled problems?