Regular BSODs, both light and heavy usage.

[lsaw2]

Hi 7forums.

In Dec13 I bought a new rig and had BSOD problems, you guys helped me diagnose a faulty motherboard and a ram stick, which I RMA'ed and had replaced respectively. (thread here - http://www.sevenforums.com/bsod-hel...win7-install-bsod-issues-ntoskrnl-win32k.html)


Since then it has run great. Recently i've started to experience more BSODs, both when running 2 steam games at once and streaming AND when absolutely idle.

As per the initial responses in my last thread, I ran memtest and didn't get any errors after a few hours (with both sticks in). My temperatures seem fine as per last time, I cant see anything that i've installed recently that could have been the trigger for these bsods.

My next step was to try and run driver verifier. I am experiencing problems with this though. Enabling it and then restarting gets me to the windows login screen, enter password and it cuts to black screen and wont load. Loads fine in safe mode. But im not sure what to think of that so any help would be appreciated.

I also ran crystaldisk info to check my ssds and they both came back as fine.


I include the DM zip file of computer info and a speccy screenshot.


http://speccy.piriform.com/results/LBzECWVye5qh6IQIsiNCs7j


Thanks in advance


lsaw2

 

[Arc]

Hi lsaw2.

Update the BIOS to Version 2501 from Motherboard | P8Z77-V LX2 | ASUS UK

   Warning

Please be aware that BIOS update is a risky process and if it is done improperly then it may be fatal for the motherboard. If you dont have any previous experience with BIOS updates, better you get it done by somebody who knows it, or take help of professional tech near you.

​

Also Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

 

[lsaw2]

My hero Arc from last time!

Thank you very much sir I will update the BIOS and return forthwith.

Much appreciated.

 

[lsaw2]

BIOS updated without complications thankfully. Will leave memtest running over night and get back to you with the results.

thanks once again for the quick reply

 

[Arc]

Welcome. Will wait to know the result.

 

[lsaw2]

I feel like a naughty school child :s

i've not followed instructions. I left memtest going over night, 12 hours in and it's just over half way through the 3rd pass. I couldnt wait any longer, zero errors up until then though.


What next driver verifier again?

 

[Arc]

Sorry mate. Memtest86+ is not very reasonable for less than 8 minimum consecutive passes.

As you are impatient about the time it consumes, you may wait and observe how it goes after the BIOS update. Report us for any further BSOD.

But if then the situation still demands to run memory test, complete it. OK?

 

[lsaw2]

Sorry mate. Memtest86+ is not very reasonable for less than 8 minimum consecutive passes.

As you are impatient about the time it consumes, you may wait and observe how it goes after the BIOS update. Report us for any further BSOD.

But if then the situation still demands to run memory test, complete it. OK?

yes ofc, I knew I was doing something bad, I just use this computer for everything so to have it offline for 48 hours running memtest makes me sad.


If I turn ON driver verifier, I get the same problem, restart computer, enter login information and the screen just goes to black and I have to turn off at the plug and start up in safe mode to turn it off again.

can I select only one non microsoft driver at a time to see if one specific driver is the cause?

thanks for the super quick reply.

 

[Arc]

I am online now.

Apparently there is no specific need for a driver verification based on the dumps included in the zip posted in the original post. But if you want to go for it, you know the precautions.

Driver Verifier - Enable and Disable
​

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

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, 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 too, do a System Restore to a point you made earlier.

 

[lsaw2]

The only thing that was new to the system slightly recently, was a new razer keyboard which came with some software. I've uninstalled that and then gone back to asking driver verifier to run. And NOW it gets past the login window and the computer starts up and is useable. so far no bsods !

Hopefully it was just this software causing my issues, I will continue to use and test the rig and if it BSODs again i'll get straight back here!

thanks very much as usual for the quick responses Arc.

 

[Arc]

Razer drivers are generally caught by DV at the very first chance.

If the computer runs stable without it, that is well and good.

 

[lsaw2]

if I could hit the positive feedback button a few thousand times more I would.

once will have to suffice, thanks very much.