BSOD on startup (sometimes) WHEA Uncorrectable.

A

abody519

Member
Joined
Sep 28, 2013
Posts
10
Hello,

I just built a new system and this is starting to frustrate me. Every time install a fresh copy of windows 8 everything will boot fine until I have all the drivers and updates installed. Then it will BSOD on start sometimes. It will NEVER BSOD after startup (if successful). The only old parts (from previous computer) I am using is the Ram and PSU. Everything else is new.

· OS - Windows 8
· x64 (64-BIT)
· Non, new SSD
· full retail version of windows 8
· All new except for PSU and ram. Those are about 11 months old
· Just reinstalled 3 times...

· CPU - I7 4770K
· GPU - 2 X EVGA GTX 770 4GB in SLI
· MB - Asus Maximus VI Formula
· Power Supply - Corsair AX1200
Ram - Corsair Vengeance LP (4 x 4gb) 1600 mhz
CPU Cooler - H100i

Nothing was/is overclocked.

Any help is much appreciated!!

View attachment Abody519.zipView attachment Health Report.zip
 
Hi,

In regards to the perfmon:

Symptom:
Device drivers are not installed.
Cause: A driver has not been installed for this device preventing it from working properly.
Details: The device driver for G19 Gaming Keyboard (Display interface) has not been installed. This device will not be available until the correct device driver is installed.
Resolution: 1. Try installing the drivers using Windows Update.
2. Install the drivers that are on the installation media that came with the device.
3. Check with the manufacturer for an updated driver.
Click to expand...

and

Symptom:
Device drivers are not installed.
Cause: A driver has not been installed for this device preventing it from working properly.
Details: The device driver for MF5900 Series has not been installed. This device will not be available until the correct device driver is installed.
Resolution: 1. Try installing the drivers using Windows Update.
2. Install the drivers that are on the installation media that came with the device.
3. Check with the manufacturer for an updated driver.
Click to expand...

Is this intentional? Also, there are no dumps located in your jcgriff output folder. Can you please manually navigate to C:\Windows\Minidump and zip up any and all dumps there and attach it here?

Regards,

Patrick
 
Hello Patrick,

Thank you for the reply. I did install the last 2 drivers but the problem persists.

To be honest i just followed the instructions for the output folder and have no idea how to tell if there is a dump in there. I also went to c:\windows but cannot find that folder. Sorry I am very new to trouble shooting BSOD's. Is there any further direction you can give me to help diagnose the issue?
 
When my computer BSOD's (im running windows 8) it will say something like preparing diagnostic or something and give a % but it just stays at 0% so i usually just reset my system. Is that preventing the dump from happening when i BSOD?

Thanks!

-Andy
 
Yes, that's exactly why no dumps are being generated. For reference, *124 bugchecks are fatal hardware errors and imply more than 9/10 times hardware failure. Without the dumps though to analyze, I can't say for sure. The NOT dumping though is a definite sign of hardware failure in some way. I am going to recommend two things for now, two hardware diagnostics:

1. Run a Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

2. If Memtest shows no errors after ~8 passes, run Seatools:

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick
 
I will definitely do the mem test and report back! I have tried 2 different ssd's with same results as well as 2 diff MB's so i am almost sure its my ram if you suspect it to be a hardware issue. Thanks again Patrick!!
 
Hi Patrick,

Since we last talked, I have been running the mem test (via usb key). It started the test upon boot so i did not modify any settings. So far it has run 5 passes in the last 8.5 hours without error. Should i let it keep running until i hit 9?
 
I see, I will let it keep running then. I was just wondering if nothing was caught at 5 passes, would it make a difference at 8 passes. I'm almost hoping its a ram hardware issue as it is an easy fix... =(
 
Right, yea, I've done a lot of *124 cases and they are mostly a CPU issue actually. However without the dumps it's impossible to say, of course. We'll go through the ring of diagnostics though and get it worked out on why you can't generate dumps though, no worries.

Regards,

Patrick
 
That sounds good. Its currently at pass 7 with 0 errors. Should i still run the seatool diagnostic even though i replicated this error with 2 different SSD's? Or should i just drive over to Fry's electronics and buy a new CPU and pop that in and give it a go... (not sure if there is any definitive way to ID the CPU hardware failure). I was always under the impression that if CPU hardware issues exist = no bootup at all..
 
Is the SSD at its latest firmware? If Memtest passes and your SSD's are at their latest firmware, there could be some OS reasons why it won't dump either which we can take a look at. If you want to buy a new CPU that's entirely up to you. I am not recommending anything because I haven't been able to analyze anything yet. I'd hate to see you buy a new CPU and let's say it turns out to simply be an OS setting that needs tuning in Advanced System Settings, a motherboard issue, etc.

If your computer is not generating DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Regards,

Patrick
 
Sounds good. I will take your advice and hold off on the CPU purchase. Its a 15 minute drive for me so I can go any time. I have already checked that both my SSD's are on the latest firmware. I will follow the instructions above and let you know what happens. (after my computer finished its 8th pass on memtest)
 
Alright.. so i made all the changes to the above and I BSOD'ed on startup. I made it a point to wait 5 minutes at the BSOD screen... nothing happened. And on the the restart i get into windows normally (it seems almost as if I BSOD every other startup). I attached a screen of the BSOD and checked the Minidump file and it is empty...
BSOD.jpg
 
If everything is set in regards to the dump generating, memory is passing, and SSD's are latest firmware, we're down to the board / CPU. You mentioned earlier that you presumed if CPU was the issue, it wouldn't boot. Yes and no, it depends entirely on the severity. For example, if I had access to the dumps (unfortunately I don't) I'd be able to see the type of error you are getting. When a CPU is faulty, if it is, it can be faulty in more than just the typical 'CPU is dead, computer won't boot, time to replace'. The cache on it can become faulty (L1, L2, etc), it could be overheating, etc. There are tons of variables. Speaking of overheating, how are the temperatures of the your hardware? You can use software such as Speccy to determine this - Speccy - System Information - Free Download

Nothing is overclocked, right? Also, you have an Asus board. If you have any Asus bloatware installed (anything Asus software at all really... AI Suite, etc) uninstall it ASAP. I always see it causing *124's, and I've dealt with it in the past too many times.

Overall, without dumps to analyze it's a 100% guessing game. You could go out and replace the CPU, put it in, and all could be well... or it doesn't change a thing.

Regards,

Patrick
 
Hello Patrick,

I have finally solved the issue. It was really a rookie mistake on my end I want to sincerely apologize for all the time I have taken from you. I neglected (and also forgot myself) that I have a Asus AC66 PCE adapter installed. I just realized it this morning and did some research and indeed that was what was causing the issue. There is no firmware/driver compatible for z87 chipsets for that particular adapter.

Again I want to thank everyone that contributed and am very glad I am finally able to get my computer back up and running.

Thank you again Patrick!!!
 
Hi,

Absolutely no apologies necessary, and thank you very much for updating on what the issue was. Glad to hear everything is working as intended now. Good work.

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top