Kmode_exception_not_handled

update: I reinstalled nvidia drivers once again but this time with "clean install". I noticed that the bluescreen involved nvidia drivers so this could help?

Just waiting for another bluescreen to surprise me...

GPU drivers did not do help. I got this bluescreen now. Could the root problem be the MoBo?

Code:

BugCheck 7F, {8, 80050031, 6f8, fffff88004a8d752}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1d6752 )

Code:

Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

Update:

Code:

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`048b7000 fffff880`05355000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 29 06:47:52 2012 (50DE9218)
    CheckSum:         00A7F96C
    ImageSize:        00A9E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The latest driver which has been released, is dated as the 5th January 2013:

• Latest NVIDIA ForceWare Video Drivers Windows 7

1. Download Driver
2. Start Type: Device Manager
3. Expand Display Adapters
4. Right-Click Driver Name, Uninstall
5. Reboot
6. Run Driver Sweeper
7. Reboot
8. Install Downloaded Driver

Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:

• Drivers - Clean Left over Files after Uninstalling

Scan for any missing, modified or corrupted protected Windows files with:

• SFC /SCANNOW Command - System File Checker

Could you please upload the OCCT graphs and did the BSOD occur with new RAM modules?

Scan with SFC /scannow command has been done and it said that no violations found.

I uninstalled NVIDIA drivers, rebooted, ran driver sweeper, rebooted, installed 310.90 NVIDIA drivers and rebooted. Now i ran OCCT GPU test for 10minutes and zipped graphs into attachement, the FPS drops at the begining was because i move the graphics window a few times.

I installed the new RAM back to my motherboard because it seems that it doesnt matter which ram i use. Anyways I'm preparing for next bluescreen again, although no indicators for that happening is present...

You need to run OCCT for least 1 hour, in order to gather a reliable judgment about the voltages and temperatures, to deal with any overheating issues you can remove any dust from inside the case and remove the side cover to provide better air circulation. Please ensure you have enabled the Error Checking ability in OCCT.

Any possible BIOS updates? It will best to check the motherboards website or your computer manufacturer:

Code:

[BIOS Information (Type 0) - Length 24 - Handle 0000h]
  Vendor                        American Megatrends Inc.
  BIOS Version                  2105   
  BIOS Starting Address Segment f000
  BIOS Release Date             07/23/2010

As i said earlier, that is the latest bios update. I've dusted my pc already. But good news, my computer has been stable for entire day as of now. By the way if i enable error checking in OCCT, the graphics window just freezes and does nothing.

2 days stable now :) I trust the blue screen issue is fixed now.

Thank you blue robot you are awesome. I believe that the number of different bluescreens were because of mixed GPU drivers. Although the problems begun when i installed the new memory sticks but maybe i also updated nvidia drivers that same day which caused the problems, i don't remember. Anyways it was most likely a driver issue and i hope the system won't crash tomorrow :)

Thanks for help!

Your welcome, and hopefully no more crashes will occur :)

The dump file seems to be corrupted for some reason, try recreating your page file if you haven't done so, by following these steps:

Delete/Recreate the Pagefile

1. Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
2. Click on the Advanced tab
3. Click on the Performance Settings button
4. Click on the Advanced tab
5. Click on the Virtual Memory Change button
6. Uncheck the "Automatically manage paging file size for all drives" box (it's the default)
7. If the above box isn't checked, then make a note of what the paging file settings are
8. Click on the "No paging file" radio button, then click on "Set"
9. Answer Yes to the confirmation dialog that pops up.
10. Click on OK 3 times (to close all the Windows)
11. Reboot the system (this will delete the paging file)
12. Once Windows starts, go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
13. Click on the Advanced tab
14. Click on the Performance Settings button
15. Click on the Advanced tab
16. Click on the Virtual Memory Change button
17. Place a checkmark in the "Automatically manage paging file size for all drives" box (it's the default)
18. If the above box wasn't checked at first, then re-enter the paging file settings that you noted in Step 7
19. Click on "Set" (it'll be greyed out if you checked the box 2 steps earlier
20. Click on OK 3 times (to close all the Windows)
21. Reboot the system (this will recreate the paging file

)

Have you ran Memtest86+ for least 9-10 passes yet?

I also wouldn't recommend using DriverEasy for updating drivers, since many third-party driver programs aren't very reliable at updating drivers; it's best to download the driver file from the manufacturer and then install through Windows Device Manager instead.

Code:

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************