Kmode_exception_not_handled

Remove (at least to test):

Code:

Start Menu\Programs\avast! Free Antivirus

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

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.

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.

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.

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..

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

That's good to know :)

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.