Solved Random BSODS, cause: ntoskrnl.exe, tcpip.sys, Ntfs.sys, dxgmms1.sys

[lillem4n]

Hello,

I'm getting random BSODS mostly on startup and during casual browsing eg. tasks which isn't that demanding but also occasionally during gaming.

I've searched around but I'm still clueless and I hope somebody is more familiar with these error codes than I am. Trying to debugg these BSODS without much experience has proven pretty difficult.

I have done a two runs with Memtest without any errors.

Best regards,
Fredrik

 

[koolkat77]

Welcome to the forum.

BugCheck C8, {2, 0, 0, 0} 
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1e2e2 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck C5, {fffff8100e81b6b0, 2, 0, fffff8000e7c0a4e} 
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+192 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck D1, {41, 2, 1, fffff88001850c0e} 
Probably caused by : memory_corruption 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 50, {fffff88048345f40, 0, fffff88001253c0a, 5} 
Probably caused by : memory_corruption 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck FC, {fffff880091739d0, 8000000399ed2963, fffff880091732d0, 2} 
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44dfc ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck C5, {fffff8100e8516b0, 2, 0, fffff8000e7f6a4e} 
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+192 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1000007E, {ffffffffc0000005, fffff8800f0203cf, fffff880023717b8, fffff88002371010} 
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+9cb ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Please follow the steps below:

Based on the bugchecks, I would recommend you follow and complete the steps given below:

1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

4. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:

• Piriform - Speccy
• CPUID - HWMonitor

Update these drivers:

SSPORT.sys Fri Aug 12 05:07:32 2005 (42FBDA34)
Samsung printer driver
Driver Reference Table - SSPORT.sys

nusb3hub.sys Fri Dec 10 10:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3hub.sys

nusb3xhc.sys Fri Dec 10 10:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3xhc.sys

If no updates are available, uninstall the software.

• To perform a clean install of a driver, follow this tutorial:
  • How to Clean Left Over Driver Files with Driver Sweeper

• Revo Uninstaller "Free"
  • Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling. This allows you to remove leftover registry entries of the software.
    • Link to download: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Let us know the results.

 

[lillem4n]

Welcome to the forum.

Let us know the results.

Thank you for welcoming me and for your much appreciated guidance.

It took some time but now I have followed the steps with a few exceptions which I have noted in the readme file. I also took the liberty to update the "Windows seven diagnostics tool" files and added some manually which I noticed were created empty with the tool.

Some information is in swedish and I have tried to translate some essential bits but since I have "home premium" I cannot change the system language. I hope this wont be to much of a problem and I'm happy to translate anything you find troublesome.

 

[lillem4n]

I have now been without a BSOD for 5 days since lowering the RAM frequency from 1600mhz to 1333mhz(1600mhz is native with XMP for this RAM model).

When I bought the mobo there was some problems with the XMP so the recommendation was to manually set the frequency to 1600mhz which I did. Now after updating bios the XMP problem seem to have been solved, will try using XMP later.

However, this was a RAM related issue where the RAM did not get enough power most likely.

Solved!