Windows 10: New PC Build, Many Different BSOD Errors @ Random, Cannot Diagnose
New PC Build, Many Different BSOD Errors @ Random, Cannot Diagnose
Hello, after lurking these forums and looking into my issue I cannot find a solution. I am experiencing crashes on my new PC build.
Since my first day of building it, I have experienced BSOD errors/random crashes. I cannot seem to find something that will make it crash. In other words, I cannot replicate this problem. I cannot pinpoint it to one piece of software or action on my computer. I also do not know if this is a driver related problem, or a faulty hardware problem.
There are times where I can play a game for 3+ hours on end, and not experience a crash. There are times where I boot my pc, open up a browser, and it crashes before I can load the first webpage.
Some BSOD errors include:
IRQL NOT LESS OR EQUAL TO
KMODE EXCEPTION NOT HANDLED
DRIVER OVERRAN STACK BASED BUFFER
SYSTEM THREAD EXCEPTION NOT HANDLED
Attached is the zip file I created from the BSOD posting instructions
Note: Many of the errors point to LgBusEnum.sys. I believe I have corrected this error as I uninstalled the Logitech Gaming Software. This errors happened when using driver verifier. I no longer get them. Please take a look at the most recent BSOD's. I have tweaked settings/uninstalled some things during the period of these dump files.
Things I have tried/know:
- memtest86+ on a few occasions. One test included both sticks of ram with 13 consecutive passes. No errors were found.
- Tested my GPU on Unigen Heaven. It can run for hours at normal temperatures unless a random crash occurs.
- A 15 minute test on Prime95 resulted in no crashing/overheating etc
- I have tried my best to make sure that I have all up-to-date drivers, but I cannot say that I am 100% up to date.
- Driver verifier will run right now without finding any immediate errors (I fixed the LGBusEnum/ScpVBus errors). I can even play games on it without it finding an error/creating a BSOD. Something is odd though: After I try to shut down my PC with verifier on, a BSOD will appear as soon as I click the shut down button.
- One BSOD error was caused by a "single bit error" Doesnt this usually indicate faulty ram? I got no errors on MemTest though....
- I did a clean install of windows after getting fed up with it crashing. It does not seem like it helped at all.
I understand that a lot of these BSOD errors hint that memory might be defective. Although I have tested the memory, is it possible that it can still be faulty?
Thanks for looking at this. This community is awesome, and the support it provides is outstanding. I apologize if my BSOD errors are lacking. I reinstalled windows again and lost some of my earlier ones. I can post the latest dump files as my continues to crash.
Last edited by HighMule; 03 Dec 2016 at 22:34.
BSOD Crash Analyst
Welcome to the 10forums and apologies for the delay.
This month I have a few exams, I don't know exactly when but please don't hesitate to leave a PM if I haven't responded in 2 days
<div>Please disable fast startup</div><div>https://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html</div>
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial
Please run HDTune first, in the order posted!
Run HDTune to
- check the health,
- scan for errors, no quick scan but full scan
- run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
- the health,
- the error scan,
- the benchmark incl. following
- transfer rate,
- access time,
- burst rate,
- cpu usage.
Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.
Do not run SeaTools on an SSD as the results will be invalid.
Make a photo of the result and post it.
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
Thanks a lot for the reply, Axe0.
I am away from my desktop until this evening. I forgot to mention that I am using a single SSD for all of the storage on this rig. Will it be okay to run all of the tests for the SSD?
I am obviously going to skip the SeaTools test.
BSOD Crash Analyst
The mentioned storage tests can be run on all kinds of storage devices, the exceptions are mentioned
To be straight, it is OK to run the tests on your SSD
Thanks for the speedy reply. I can't to find out what my problem is!
I have conducted all of the tests you recommended, aside from the SeaTools test.
I think my SSD looks good.
Also attached is my most recent crash -> I had one more since starting this thread. Sorry that I did not configure the minidump before this happened. I looked at the debugging info, and I saw "memory corruption" inside of it several times.
I just experienced another crash while gaming. Attached is the .dmp.
Debug read this:
*** WARNING: Unable to verify timestamp for nvhda64v.sys*** ERROR: Module load completed but symbols could not be loaded for nvhda64v.sysProbably caused by : memory_corruptionFollowup: memory_corruption
Right clicking on the driver file in file manager and device manager reports that the driver is version 188.8.131.52. I did not install NVIDIA's graphics driver release from this week, but I have the next-latest one. In the documentation, my driver matches the second-latest NVIDIA released audio driver.
In my device manager, I do have 3 items under the sound, video, and game controllers:
-NVIDIA High Definition Audio
-NVIDIA Virtual Audio Device (Wave Extensible) (WDM)
-Realtek High Definition Audio
Could these be interfering and causing crashes?
What is going on here? Does this indicate that RAM might be faulty? Please let me know if I am wrong to suspect RAM even if memtest86+ did 13 consecutive passes. I am considering just using a single memory stick in a combination of slots to see if there is a faulty stick/slot.
There is a different error every time! It just happened to the the audio driver that failed this time.
Edit: Computer crashed a couple more times. Both are labelled with "memory corruption" stuff.
Last edited by HighMule; 07 Dec 2016 at 08:13.
There is a new BIOS version 2103 Improve system stability , you are still on 0311 first release.
One of the dumpfiles names Memory management
You are using 3200 mhz RAM did you enable xmp profile.
At what voltage are your modules running.
Check the timings.
How long ago did you run your memtest86+?
BSOD Crash Analyst
The model is 3200, but the RAM is running it SPD 2133.
@HighMule, it more likely indicates that the NVIDIA audio driver caused memory corruption. The nvhda64v.sys is not a graphics driver, but an audio driver.
You could uninstall the audio drivers of NVIDIA, they are not necessary.
@axeO I know thats why i said using 3200 mhz modules, because on some forums there are people mentioning problems if they have enabled xmp profiles on this mobo.
I've been having seemingly random BSOD's over the past couple of months. I recently reset my BIOS and this went away for a week, however, earlier today I received another. Oddly enough, the first time I ran the DM log collector utility this...
Hello. Since 2 months i'm getting several BSOD errors. They appear in random moments when i'm playing games, watching videos etc. I have really no idea how i can fix this :( Here is the dump file: 051816-14187-01.dmp - Google Drive
EDIT: added zip...
I've been getting random BSOD errors with no probable cause. It happens when the computer is idle or when I'm browsing the internet or while playing games. There's no time pattern to it neither is there a usage pattern.
I've tried some...
Been getting these 2-3 times a day, mainly while gaming.
Over the past couple of days I have been having reasonably frequent BSODs. Some have not created a dump file. I cant pinpoint anything in particular but it seems to be pointing to a driver issue but never identifies the driver from what I can...