Solved BSOD on computer after motherboard upgrade

[essenbe]

OK, that's fine. But now you know how to get there and how to change it if you need to. Today wasn't a total loss. You learned something.

 

[Anthony07]

Thanks running long generic test right now says it will be like 2 and a half hours if you have anything else you see off the screen shots please let me know i will try to monitor forum

 

[essenbe]

Enable driver verifier but first create a restore point. The link of how to create one is below. Then enable driver verifier. Sort the drivers by provider and enable all drivers NOT provided by Microsoft. Then use your computer any way you want and do anything you want to. It will seem kind of slow and sluggish. If there is anything that you do that usually causes a BSOD, do that often. Driver Verifier puts extra stress on the drivers, trying to make the computer crash. Hopefully, the driver causing problems will be caught. Keep it on for 24 hours of actual use. Again, there are no restrictions on what you can do. Run it as hard as you want. But, do keep an eye on the CPU temps.

   Warning

Be sure to create a Systm Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[essenbe]

The screen shots look OK. I will just wait until you find the results of the test. After that we will enable Driver Verifier, but wait for the test to finish.

 

[Anthony07]

Driver verifier

Now that you bring that up i was looking at other posts and seen to try driver verifier so i did but now that i think about it i might still have that running i dont remember shutting it off is there any way to check if it is still running if it is i will restart it

 

[essenbe]

The link in the post tells you how to enable or disable it http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Anthony07]

Thanks

 

[Anthony07]

verifier bsod

ok so enabled verifier blue screened upon reboot until i went to safe mode and disabled here is the dmp file

 

[Anthony07]

enabled it a second time same thing bsod when booing windows here is dmp file from that

 

[essenbe]

Here is the first BSOD

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {e1, fffff9800149efb8, 0, 0}
*** WARNING: Unable to verify timestamp for GUBootStartup.sys
*** ERROR: Module load completed but symbols could not be loaded for GUBootStartup.sys
Probably caused by : [COLOR=red]GUBootStartup.sys[/COLOR] ( GUBootStartup+103c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000e1, Synchronization object address is bogus or pageable.
Arg2: fffff9800149efb8, Synchronization object address.
Arg3: 0000000000000000
Arg4: 0000000000000000

That is GlarySoft - Glary Utilities Startup Manager Tool driver

 

[essenbe]

The second one was the same thing. Uninstall it and any other alterations you have made to system files.

 

[Anthony07]

I have uninstalled program and restarted driver verifier at desktop now with driver verifier enabled

 

[essenbe]

No BSOD?

 

[profdlp]

Sorry to butt in, but CPU-Z shows you using slots 3 & 4 for your memory. Is that what the manual recommends?

You are in good hands with essenbe, just tossing that into the mix.

 

[essenbe]

Good catch, Prof. I missed that one.

 

[profdlp]

Most boards don't care, as long as you're using two "paired" ones for Dual-Channel. But you never know...

 

[Anthony07]

I have not seen anymore bsod i work 12 hour shifts so have not been able to work with computer for to long but i have to check my manual about ram i think i originally had them in slot 1 and 2 but when getting bsod i switched them trying to make sure slots were not bad will try to do more with computer in morning when i get off work

 

[essenbe]

OK, no problem, check your manual. I think they usually go in slots 2 and 4 or 1 and 3.

 

[profdlp]

essenbe is correct on the Ram slots. The most frequent mistake people make is placing them next to each other instead of staggered. (See pic)

Swapping them is not a bad idea, though Asus recommends using the blue slots for the best chance at compatibility and stability. CPU-Z says you're in Dual-Channel, but they miss one one in a while. Sorry if all of this is irrelevant, but it never hurts to ask.

A couple screen grabs from the manual for your board:

 

[Anthony07]

I will check when i get off as to the ram being staggered i have them in every other slot right now i never install directly side by side not sure why it says it like they are side by side and not sure but i thought i had them in the blue slots but i will check then