Random BSOD New build 0x800... event id 1001

x BlueRobot said:

Okay, and the test will run itself, it's just when you get errors you will need to start doing some more through testing and swapping around etc.

Ya just found that out this morning. So far I have ran 5 going on 6 passes and no errors. But, I noticed on the screen it says under RAM settings that it is DDR1600 instead of 1866 for some reason. Is this normal or do I need to change a setting for 1866?

Well I ran 9 passes and no errors. I went back into windows and opened chrome and that's when I got a blue screen again. This time it said: memory management

Should I redo the SF diagnostic to show you the report? I am not sure what to do from here..

Please upload the folder from the SF Diagnostic Tool. The clockspeed for the RAM is normal, most RAM is half or lower than the speed labeled, I believe is for stability, the maximum speed which can be achieve would be 1866MHz.

x BlueRobot said:

Please upload the folder from the SF Diagnostic Tool. The clockspeed for the RAM is normal, most RAM is half or lower than the speed labeled, I believe is for stability, the maximum speed which can be achieve would be 1866MHz.

Okay here is the new report.

Code:

BugCheck 1A, {41287, 10, 0, 0}

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

Code:

Usual causes:  Device driver, memory, kernel

The first parameter indicates that internal memory management structures have become corrupted. I've done some searching, and the MSDN Library, suggests that this parameter indicates an illegal page fault has occurred.

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

• SFC /SCANNOW Command - System File Checker

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

x BlueRobot said:

Code:

BugCheck 1A, {41287, 10, 0, 0}

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

Code:

Usual causes:  Device driver, memory, kernel

The first parameter indicates that internal memory management structures have become corrupted. I've done some searching, and the MSDN Library, suggests that this parameter indicates an illegal page fault has occurred.

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

• SFC /SCANNOW Command - System File Checker

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

Ok I ran the scannow command and got no errors. I set the driver verifier settings and rebooted. I am going to let it sit at idle for 24 hrs and see what happens. I am not sure if I need to actually do anything with it like run programs because all it said is use your computer normally.

Just do whatever you do normally on your computer.

x BlueRobot said:

Just do whatever you do normally on your computer.

Okay, about 18.5hrs in I figured I would try running various things to see if it would blue screen. So I opened chrome and went on youtube, where it crashed last time. It started to load a video and it didn't blue screen, but instead the screen got all these black and white lines across it. Then the whole thing froze like that and I was forced to use the reset switch.

For now I am going to continue to run the computer for the rest of the 24hrs and try different things to see if it will blue screen as I wait for your response. I think what I need to do is then disable the driver verifier and upload the new sf diagnostic folder, correct me if I am wrong.

Also thank you for all the help so far, I really appreciate it.

Welcome, and upload the SF Diagnostic folder when it crashes again (BSOD), and Driver Verifier will cause some freezing and reduce the usual performance of your computer since it checking for corrupted drivers.

If it didn't crash after 24 hours, then disable Driver Verifier.

x BlueRobot said:

Welcome, and upload the SF Diagnostic folder when it crashes again (BSOD), and Driver Verifier will cause some freezing and reduce the usual performance of your computer since it checking for corrupted drivers.

If it didn't crash after 24 hours, then disable Driver Verifier.

Okay I got that screen again with the white lines, no bsod first or anything, just the lines and everything freezes. Is this the crash I am looking for? If it is, should I just leave it and let it do its thing instead of resetting? I have already reset after the second screen freeze, so I will try to replicate the bsod again.