Sign-in / Sign-up
Your question
Solved

New Asus Z87 Pro build, getting BSOD's

Tags:
  • Windows 7
  • Blue Screen
  • z87
  • Motherboards
Last response: in Motherboards
March 19, 2014 7:38:38 AM

Hello all,

I finally decided to do an mostly new component upgrade last night. I built a new PC with a Asus Z87 Pro, i74770K, 16gb of Corsair Vengeance XMP ram, a 256gb Samsung 840 pro, and a Corsair RM850 PSU. I carried over 2 components from my old PC: my 470 GTX and my Areca RAID controller and drives. My old PC was 110% rock solid, just a little long in the tooth and I wanted USB3 support and some other things.

The built went without issue. I installed Windows 7, no problem. When I installed the Nvidia driver, it BSOD'd halfway through the install, which was alarming. I rebooted and installed it again, no problem.

I played around with it for a few more hours. I again had a BSOD, this time when updating the CS6 suite. I rebooted and the update went OK. I also turned off the XMP profile in the BIOS. I am 99% sure there is no overclocking going on here but I'll be honest, the bios is a little confusing and it's hard to tell. CPU-Z says @3.50 so I believe that is stock.

Finally this morning I had another BSOD when shutting down the PC.

What I have done so far:

Ram memtestx86 all night. No errors.

Ran furmark for about 15 minutes. No errors.

Played Battlefield 4 for about 45 minutes. No issues.

Updated the bios to the most recent, 1802; it was running the original 1007 release bios. That was only about 20 minutes ago so not sure if this has or has not affected the situation, after the third BSOD (before the bios flash) I decided I needed to post on Tom's regardless.

What should I be doing next?

Here is the possibly relevant info:

1.) There are tons and tons of this in the event viewer:
.NET Runtime Optimization Service (clr_optimization_v4.0.30319_32) - 1>Failed to compile: System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 . Error code = 0x80131f06

2.) I have 3 dump files and a BSOD viewer, so I have a ton of information from them but am not sure what to post. 2 were caused by HAL.DLL at HAL.DLL+12903, the last one was win32k.sys+c40d1, type PAGE_FAULT_IN_NONPAGED_AREA. In all 3 of them, the crash address is ntoskrnl.exe+71f00

Thank you for looking, I'm kind of nervous that maybe it's a hardware issue.



More about : asus z87 pro build bsod

March 19, 2014 3:20:35 PM

Can you please upload the .dmp files to www.mediafire.com
I will give you a little insight as to those files that caused your BSODs. Those files didn't cause the BSODs itself but rather windows cannot find the actual cause and points it to the windows files that handles that type of operation. For example, one of the files was hal.dll, this file is the Hardware Abstraction Layer that basically consists of routines that communicates with the hardware itself, it then tells kernel mode files like device drivers information. If windows cannot identify which hardware device driver caused the issue it will point it to hal.dll, ntoskrnl.exe or other kernel system files.

ntoskrnl.exe is the kernel. I could spend hours explaining it so if you're interested I would recommend googling it.

You get the point I'm making.

EDIT: You said you were nervous that it could be hardware related, because it blue screened half way through driver install it does seem driver related, if it is then I will do the best I can to help you.
m
0
l
Related resources
March 20, 2014 8:14:55 AM

You have two bugchecks of 0x124 WHEA_UNCORRECTABLE_ERROR which indicates a fatal hardware error has taken place. I would recommend stress testing your processor with IntelBurnIn test and your Graphics card with Furmark. You also have a memory related issue, how many passes did memtest86 complete?
m
0
l
March 20, 2014 12:54:58 PM

TheMooMooTV said:
You have two bugchecks of 0x124 WHEA_UNCORRECTABLE_ERROR which indicates a fatal hardware error has taken place. I would recommend stress testing your processor with IntelBurnIn test and your Graphics card with Furmark. You also have a memory related issue, how many passes did memtest86 complete?


For memtest whatever the default is; it looks like the new version (green screen) doesn't run continuously by default like the old (blue screen) one did. I think it was 10 passes. I will take a better look at the settings and let it run overnight while I am at work.

I will try the Intel Burnin test and furmark some more. How long should I leave Furmark running? I know that's a particularly rough test.

I also left Unigine Heaven running last night; it ran from about 12 hours without issue if that is worth anything.

Thank you again.
m
0
l
March 20, 2014 2:00:13 PM

furmark should run for about half an hour. Keep monitoring it though as it can damage your gfx card if left and the temperature gets too high because it's not fail safe. Keep an eye on the temperature.
m
0
l

Best solution

March 21, 2014 1:18:50 AM

Right, it sounds like a driver issue. I'll take a further look into your drivers later on.
EDIT: Your graphics driver is up to date, I would recommend rolling the driver back to a previous version. Go to www.geforce.co.uk/drivers and select your settings then download the driver 314.22. It's old and won't allow you to play BF4 but just test it on some other games. If it works then create a system restore point then update the driver, if it fails restore the system back.

The BSOD you had was a system service exception which is generally caused by graphics drivers.
Share
March 21, 2014 6:00:05 AM

Ok, I just got home from work. Memtest ran overnight, 11 hours, 75 passes, zero errors.

I've uninstalled my video driver with DDU and reinstalled it (no problems) and ran 10 passes of CPU BurnIn on high stress, no problems.

Thank you again for your time on this, I really, really appreciate it.
m
0
l
March 21, 2014 7:46:44 AM

Has the problem been fixed or are you still getting BSODs?
m
0
l
March 21, 2014 6:33:04 PM

I don't know yet. I will update this when I do, I slept all day (I work nights) so haven't been able to mess with it today.

m
0
l
March 24, 2014 7:16:34 AM

I'm at college at the moment. I'm on my mobile. I'll try and have a look tonight if I'm not too busy.
m
0
l
March 24, 2014 11:17:25 AM

The dump files aren't giving any indication as to what caused the BSOD apart form the bugcheck 3B which is generally caused by graphics drivers but we can't know for sure.

Can you please enable Driver Verifier by following these instructions. It will help find the driver responsible.

WARNING, before doing the following you should change your startup programs because I've had numerous cases where it will BSOD as soon as it starts up, even in safe mode. Can you follow these instructions.

1. Open the Start Menu.
2. In the search line, type msconfig and press Enter.
3. If prompted, click on Continue for the UAC prompt, or type in the administrator's password.
4. Click on the Startup tab.
5. disable all programs that are unnecessary. DON'T DISABLE YOUR ANTI VIRUS.


1. Start typing verifier.exe into the start menu, and open Verifier.
2. Select "Create custom settings (for code developers)", and hit Next.
3. Make sure Standard settings, Force pending I/O requests, and IRP Logging are selected, and hit Next.
4. Select "Select driver names From a list", and hit Next.
5. Click on "Provider" at the top to sort the list by manufacturer; select all drivers not provided by Microsoft Corporation, Macrovision or Unknown.
6. Click finish and restart your PC.
m
0
l
March 24, 2014 11:23:25 AM

Ok, I've done the driver verifier. I ran it and selected any driver NOT unknown, MS, or Macrovision and rebooted. What now - nothing seemed to have happened.
m
0
l
March 25, 2014 12:23:10 PM

Let DV run for at least 24 hours.
It should BSOD if it's a driver issue.
If not then it's something different. Probably hardware.
m
0
l
March 25, 2014 2:35:25 PM

Ok, thank you. I just ran it again and rebooted, I'll check in tomorrow. Is there anything special I could or should do to try and trigger a bsod?
m
0
l
March 25, 2014 3:39:50 PM

No, just do what you normally do. Driver Verifier is like stress test but for drivers. It basically puts stress on old drivers an if they step out of line it generates a BSOD and 99% of the time it finds the correct driver which is causing the problems.
m
0
l
March 25, 2014 3:58:19 PM

Great, I'll report back when I have something. Thank you again :) 
m
0
l
March 30, 2014 4:33:50 AM

Alright, it's been a few days. 5, specifically. No problems with the PC at all, I've been doing all the stuff I normally do. I also did windows updates, which I had not doing previous to this - including SP1, all that stuff. Everything's up to date.

I really want to make sure 100% this is solved while still inside the Amazon return window (free shipping, cross shipping) instead of into the vendor RMA process (slower, pay for shipping. I ran driver verifier and checked ALL drivers, not just the non-windows one. That caused a BSOD loop.

https://www.dropbox.com/s/o302lpteb67a6qn/033014-4508-0...

https://www.dropbox.com/s/ly0dkei8qyknuo7/033014-83288-...

I went into safe mode and set the verifier back to the non-Windows & non-Macrovision one. I'm just sure if the above data is worth anything or not. Am I good to go?

Thank you again.
m
0
l
March 30, 2014 11:51:16 AM

Right, the Logitech Gamepanel Virtual HID Device Driver appears to be causing problems.
Please update it here:
http://www.logitech.com/en-us/support

fffff880`09997000 fffff880`09999480 LGVirHid T (no symbols)
Loaded symbol image file: LGVirHid.sys
Image path: \SystemRoot\system32\drivers\LGVirHid.sys
Image name: LGVirHid.sys
Timestamp: Tue Nov 24 01:36:48 2009 (4B0B38B0)
CheckSum: 00012CDE
ImageSize: 00002480
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Sonic CD/DVD burning driver is causing problems, I would highly recommend you actually uninstall this but you can update it if you wish, uninstalling it appears to solve it most of the time, I've had this driver cause BSODs before.

fffff880`012da000 fffff880`012e61a0 PxHlpa64 T (no symbols)
Loaded symbol image file: PxHlpa64.sys
Image path: \SystemRoot\System32\Drivers\PxHlpa64.sys
Image name: PxHlpa64.sys
Timestamp: Mon Oct 17 15:29:34 2011 (4E9C3BCE)
CheckSum: 0001C018
ImageSize: 0000C1A0
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
m
0
l