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

[kenh536]

I recently built a new pc, installed windows 7 64bit, installed mobo drivers, installed video card drivers, then got all of windows updates. I got a BSOD randomly and it rebooted to windows fine. The next day it happened again about 2 hours after boot. The second time I saw it said: Page fault in nonpaged area, but then it flashed away and rebooted before I could read more. Then last night I fell asleep downloading something and woke up to it saying it recovered from an unexpected shutdown.

Not sure if this is related but Applications are crashing as well. I get error messages such as:
Catalyst Control Center: Host application has stopped working.
McAfee service host crash
Windows Explorer has stopped working
Also Chrome crashed very frequently when I tried to upload multiple photos.

Specs:
Cpu: AMD FX6300 6core
Motherboard: Gigabyte 990fxa-ud3 revision 3.0
Ram: Patriot Viper 2x4gb 1866mhz
Gpu: Sapphire 7870xt

Sorry for the long post, just trying to get as much info that is needed.

I have attached the .zip file from the Sf diagnostic tool, hope I did it right...
Thank you in advance for any help, it is MUCH appreciated!

 

[x BlueRobot]

[COLOR="Red"]BugCheck 109[/COLOR], {a3a039d89ac8d7b2, b3b7465eed45a718, fffff800037567c1, 1}

Probably caused by : ntkrnlmp.exe ( nt!CmpParseKey+721 )

Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

The bugcheck indicates that the Windows kernel has detected that some form of critical data corruption has occurred, this could be due to failing RAM whereby the kernel objects are being held, causing the held data to become corrupted. Poorly written drivers can cause this problems by directly modifying kernel code.

Remove:

Start Menu\Programs\McAfee
Start Menu\Programs\McAfee Online Backup

McAfee is known to cause BSODs with Windows 7, and uses many poorly written drivers which tend to cause memory access violations, the best method is remove all McAfee products completely using the McAfee Removal Tool, and then install these free and proven alternatives which work best with Windows 7.

Install and perform full scans with:

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

   Information

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:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

The bugcheck also indicates memory corruption, and illegal modification of code.

1: kd> [COLOR="SeaGreen"]!error ffffffffc000001d[/COLOR]
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

 

[kenh536]

[COLOR="Red"]BugCheck 109[/COLOR], {a3a039d89ac8d7b2, b3b7465eed45a718, fffff800037567c1, 1}

Probably caused by : ntkrnlmp.exe ( nt!CmpParseKey+721 )

Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

The bugcheck indicates that the Windows kernel has detected that some form of critical data corruption has occurred, this could be due to failing RAM whereby the kernel objects are being held, causing the held data to become corrupted. Poorly written drivers can cause this problems by directly modifying kernel code.

Remove:

Start Menu\Programs\McAfee
Start Menu\Programs\McAfee Online Backup

McAfee is known to cause BSODs with Windows 7, and uses many poorly written drivers which tend to cause memory access violations, the best method is remove all McAfee products completely using the McAfee Removal Tool, and then install these free and proven alternatives which work best with Windows 7.

Install and perform full scans with:

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

   Information

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:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

The bugcheck also indicates memory corruption, and illegal modification of code.

1: kd> [COLOR="SeaGreen"]!error ffffffffc000001d[/COLOR]
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

Thank you for the quick reply. I will remove Mcafee and install MSE and MalwareBytes and get back to you. It is worth noting that I got the first and possibly second crash before I installed Mcafee. I had MSE and only installed Mcafee because I had a license on my win7 laptop. As for the illegal modification of code... I don't know what happened there as I am no programmer and I would not do anything illegal on purpose...

 

[x BlueRobot]

Don't worry, you didn't do anything illegal, it means a driver did something which it didn't have permission to do so, and will look forward for the update.

 

[kenh536]

Okay literally 20 seconds after my last post my computer restarted, no blue screen, but it was strange... anyway I unistalled Mcafee in add/remove programs, downloaded MSE and malwarebytes, updated everything (including one windows update), then rebooted and ran full scans in MSE and Malwarebytes which came up with nothing. What should I do now? Wait and see if I get anymore Issues or...?

Edit: Well that didn't take long. Just now my screen completely froze up and waiting didn't do anything. I had to press the reset button. Then I got a message that said Your computer was unable to start. Then startup repair checked my system and it prompted me to do system restore. This issue is different and it seems to be evolving... I was reading files in event viewer and it said it could have been caused by sudden power loss...maybe one of my connections are loose? Also my 8 pin cpu power I routed behind the mobo, but I had to push down slightly to tighten the mobo... would this cause issues? Ugh I am no good at this and its really worrying me.

 

[x BlueRobot]

Check that all the slots on the motherboard are clear of dust, and then check all the cards (e.g. RAM) are properly connected, make sure your power cables are also connected properly.

What is the brand of your PSU? Do you know the specifications page for it?

 

[kenh536]

Okay so my PC was pretty clean as I have just built it a few days ago, but I went ahead and blew out any dust and checked all my connections again(RAM, Gpu, 24pin,8pin, etc) As far as the model of PSU it is a Cooler Master Silent Pro M700 RS-700-AMBA-D3 700W ATX12V V2.3 80 plus bronze certified:
Silent Pro M 700W - Cooler Master

There's the specs on the manufacturers website.

Edit: Also I was just thinking that it indicated RAM corruption. Now I ran the Windows memory diagnostic 3 times and it checked out ok. Maybe its just not catching it, should I try something like Memtest to make sure?

 

[x BlueRobot]

Testing the RAM wouldn't be a bad idea, here's the usual troubleshooting method we use:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-9 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.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[kenh536]

Testing the RAM wouldn't be a bad idea, here's the usual troubleshooting method we use:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-9 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.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Okay Ill give it a shot. But it will have to wait until tomorrow because I work graveyards and it sounds like the test takes some input and isn't automatic. Ill let you know when its done.

 

[x BlueRobot]

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.

 

[kenh536]

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?

 

[kenh536]

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

 

[x BlueRobot]

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.

 

[kenh536]

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.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]41287[/COLOR], 10, 0, 0}

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

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:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[kenh536]

[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]41287[/COLOR], 10, 0, 0}

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

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:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

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.

 

[x BlueRobot]

Just do whatever you do normally on your computer.

 

[kenh536]

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.

 

[x BlueRobot]

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.

 

[kenh536]

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.