Windows 10: BSODs during general use, numerous error codes

Been randomly getting BSODs on Windows 10 for a while, and I haven't been able to determine the source, mainly because I've been getting such a range of different stop codes. My PC will also occasionally restart itself or completely freeze. I'm assuming these are related since they started happening at around the same time as the BSODs.

Here is a list of everything I have tried so far:

• Ran chkdsk c: /r
• Scanned my HDD using 3 different programs - all tests passed without errors
• Scanned my memory using Windows and MemTest86 - no errors reported
• Updated my graphics drivers
• Updated Windows
• Checked device manager for any yellow exclamation marks - none were there

Here are the dump files: dump files - Google Drive
Several of my recent dump files aren't there since my minidump folder got wiped for some reason, but you get the idea. Hardly any consistency.

And here is my system info: Attachment 139038

:)

 

Windows 10 = Bad_Pool_Header Blue Screen

I too have experienced the BSOD with a Bad Pool Header error. I reinstalled and was fine for about a week and now it's doing it again! :-(

What are the most likely culprits? There is no alpha-numeric code associated with the "Bad_Pool_Header" BSOD.

 

Windows Update Fail

Although this error occurred during win 10 update, the real problem with this

machine is numerous blue screen reboots with various error codes, e.g.;

IRQL-Not-Equal-or-less and some others. These appear to be random after

operating up to a few hours between them.

 

Hi PHVNTOM,

Welcome to the 10forums *Smile

It seems your Windows installation has been refreshed (due to the update you mentioned?), because you have saved the dumps somewhere else the only downside of this is possible important logs that are lost.

I don't assume the chkdsk logs are from after Windows refreshing?

Could you provide screenshots/photos of the results of the programs you used to scan your HDD.


Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

 

Hi axe0, thanks for the reply.

Yeah, I think it was the Creators Update that caused the dumps etc. to be lost. My bad. There should be some info in the zip folder though, including my most recent dump file. And I believe the chkdsk logs are from before Windows refreshing, because I updated Windows after running chkdsk c: r/ (unless Windows automatically did a chkdsk scan after a BSOD, I don't fully recall).

I've also updated my system specs as best I could.

And here are the screenshots of the HDD scans I did:

Attachment 139359
Attachment 139360
Attachment 139361

 

That was the leanest and cleanest event log I have seen.
Did you recently do a clean install?
Only 578 entries.
Saw one unexpected crash.
8/11 dumps in your log were related to memory.

Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.
Memtest86+ - Advanced Memory Diagnostic Tool

 

Diagnostics Test

HDD TEST
*Arrow 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.

 

Here are the screenshots from HD Tune:

Attachment 139603
Attachment 139605
Attachment 139604

I'll leave memtest86+ running overnight and report back tomorrow with results. *Smile

 

Results of memtest86+:

Attachment 139831

 

Windows driver verifier is a tool which is used to stimulate drivers and find drivers that are misbehaving.
When the misbehaving drivers/applications are found they are uninstalled.
Another driver or application is then found and tested to make sure it does not misbehave with Windows driver verifier testing.

Windows driver verifier is designed to keep producing bsod until it is turned off or until all misbehaving drivers have been fixed. It is extremely important to understand how to turn windows driver verifier off so that you can return to the desktop and then uninstall the misbehaving driver/application. WIndows driver verifier is then turned on again and the next misbehaving driver is found and uninstalled. It's a repetitive process until there are no longer any bsod. Then windows driver verifier is run for an additional 36 hours with the computer under typical use. If there are no more bsod then windows driver is turned off. The misbehaving drivers will have been removed that were producing bsod and preventative maintenance will be performed by identifying drivers in the current computer environment that could have produced bsod in the future.

In order to use windows driver verifier you will need to navigate through the windows recovery or advanced troubleshooting menu to safe mode with command prompt. When in safe mode with command prompt you will enter the command verifier /reset
Verifier /reset turns off Windows driver verifier. It allows you to reboot to the desktop. When back on the desktop you will use software that will immediately analyze the minidump files from the windows driver verifier produced bsod. The software will provide information about a driver or application and many of these can be troubleshooted by uninstalling the driver or the application.

Once the driver or application is uninstalled there are typically two choices. Choice one is to continue using windows driver verifier to find the next misbehaving driver/application. Choice two is to find a replacement driver or application to install and to restart windows driver verifier testing the new driver/application. It's personal preference whether to find an immediate replacement or whether to continue uninstalling all misbehaving drivers/applications first.

Eventually the goal is uninstall and replace all misbehaving drivers and applications. Sometimes the most up to date drivers are well tested and best and other times they misbehave because they were not tested for the latest windows version. In these cases an older driver may be more suitable. Sometimes applications such as Cyberlink or antivirus software produce bsod. At times the software can be uninstalled and reinstalled and other times an alternative software needs to be chosen.

To practice navigating the windows recovery or advanced troubleshooting menu open administrative command prompt and type or copy and paste this command: shutdown /r /o /f /t 00
The computer will reboot to the windows advanced troubleshooting menu. Navigate to startup options then select choice #6 safe mode with command prompt. When you need to turn off windows driver verifier type: verifier /reset
At this time you can exit or reboot.

Once you have your files backed up, have created a restore point, and feel comfortable navigating through the windows advanced troubleshooting menu you should be ready to use windows driver verifier. To start using windows driver verifier you will type verifier in the left lower corner search. A pop up will appear. You will need to customize the settings. A link is provided below for the customized settings.

You will download and install each Bluescreenview and Whocrashed. They often have similar analysis but at times one may give additional information that is useful. In addition you will update the initial zip file or create a new one so that we can help you with the debugging: BSOD - Posting Instructions - Windows 10 Forums


Blue screen of death (STOP error) information in dump files.
Resplendence Software - WhoCrashed, automatic crash dump analyzer


Before using windows driver verifier it is best to modify the startup and recovery settings so that there is no automatic restart. In order to accomplish this the box for automatic restart needs to be unchecked. This will allow you time to view the bsod window. When using windows driver verifier it will display a stop code. Typically it is driver verifier detected violation. Sometimes it may display the misbehaving driver in this form *.sys If you see this please record it.

BSOD Finding and fixing them - Microsoft Community

To launch windows driver verifier use the custom settings in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

 

@zbook, where did you get the dump files? The zip file in this thread has only 1 dump.

PHVNTOM, assuming you have been getting BSODs since you started this thread, could you note down the bugchecks including parameters and let us know them.

 

axe0, I actually haven't gotten any BSODs since making this thread weirdly enough. I've had a few freezes though. It's very random; I'll have 2 BSODs in the space of a day and then nothing for 5 days. Is there not much you can do with those dumps I uploaded to Google Drive?

And zbook, I'll have a go with that Windows driver verifier when I have the time and can properly sit down and focus on it, don't want to mess anything up. I'll keep you posted.

I've attached my system info again in case anything useful has popped up.

Attachment 139945

 

Diagnostic Test

CPU TEST
*Arrow Run Prime95 - Stress Test Your CPU - Windows 10 Forums CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums



Note If you're overclocking anything, please stop it and set everything back to default while troubleshooting


Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
Make a photo of the results and post them.

 

Here you go axe0. Sorry for the late reply, been caught up in college work lately.

Attachment 140959
Attachment 140964
Attachment 140963
Attachment 140962
Attachment 140961
Attachment 140960
Attachment 140965

 

What are the temps of the CPU?