Random BSOD - ntoskrnl and systemsys? For over a week now.

ZeroAgainst · 02 Jun 2013

Hi, I custom built my computer over five months ago and hadn't had any problems until about 13 days ago. It now randomly crashes and blue screens (bsod closing in about three seconds). Thankfully it did give me mini dump files and et cetera to share with you and I'd really appreciate any feedback you can give me.

As for when it happens, I'm not too sure. I could just be talking to someone on Skype and it would crash or I could be playing League of Legends and it will blue screen without warning in the middle of the game.

Thanks in advance!

koolkat77 · 03 Jun 2013

Hi, do you get BSOD's in safe mode?

Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 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. How to Test and Diagnose RAM Issues with Memtest86+

Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

Tip

Do this test overnight.

Drivers:

Please update your Microsoft Intellipoint Mouse Driver to its latest Driver Reference Table - NuidFltr.sys

Code:

NuidFltr.sys                Fri May  8 14:53:31 2009

Tip

If you have an SSD, make sure the following are up to date:

SSD firmware
BIOS Version
Chipset Drivers
Hard disk controller drivers/SATA drivers
If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Thanks to Writhziden for the steps above.

Hard Drive/Storage

Post disk summary using CrystalDiskInfo software: CrystalDiskInfo Standard Edition

For how to upload a screenshot or file, read here

Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

For errors on your Hard drive(s): How to Run Disk Check in Windows 7

SFC /scannow to check windows for corruption:

How to Repair Windows 7 System Files with System File Checker
1. Click Start

2. In the search box, type Command Prompt
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type

sfc /scannow

and hit enter.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sun Jun  2 12:23:00.419 2013 (UTC + 6:00)
System Uptime: 0 days 0:56:48.371
BugCheck 24, {1904fb, fffff8800357e5d8, fffff8800357de30, fffff80002eee753}
Probably caused by : ntkrnlmp.exe ( nt!RtlSplay+85 )
BUGCHECK_STR:  0x24
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sun Jun  2 09:49:00.178 2013 (UTC + 6:00)
System Uptime: 0 days 2:26:28.130
BugCheck 1A, {41790, fffffa80010d6c10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  SearchFilterHo
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat Jun  1 04:26:46.188 2013 (UTC + 6:00)
System Uptime: 0 days 0:14:20.156
BugCheck 1A, {41790, fffffa80010d6be0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  Skype.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri May 31 05:09:08.587 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:57.913
BugCheck 51, {1, fffff8a00ab68410, 52d5f000, 465}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+37285 )
BUGCHECK_STR:  0x51
PROCESS_NAME:  TrustedInstall
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue May 28 06:24:13.445 2013 (UTC + 6:00)
System Uptime: 0 days 3:48:21.772
BugCheck 1A, {41790, fffffa80010d6c10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  Skype.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue May 28 00:53:26.706 2013 (UTC + 6:00)
System Uptime: 0 days 0:11:14.659
BugCheck 1A, {41790, fffffa80010d6be0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue May 28 00:41:15.952 2013 (UTC + 6:00)
System Uptime: 0 days 1:12:10.279
BugCheck 1A, {41790, fffffa80010d6be0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  rads_user_kern
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``