Windows 10: Random Numerous BSOD majority are 133 errors

I have been having numerous random BSODs. Seems worse when running Google earth. They occur about once per day. Errors are: 0x7F, 0x133,0x50, 0x3B.

:)

 

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.

 

Random Blue Screens

Hello!

Lately I've been getting random MEMORY_MANAGEMENT BSODs.

I've run sfc/scannow with no errors, chkdsk with no errors, and 2 extended passes with the memory check tool, also no errors.

These BSODs seem to happen randomly every few days, and they're very annoying.

Here's a link to my 2 latest BSODs minidumps:

https://1drv.ms/f/s!Ao-fan5pgktlhOo6lzX6lMkBzbmjgg

Thank you for any ideas on fixing this!

 

Please have a go at uploading the zip file again. The one you posted is empty.

 

Attachment 152993Attachment 152993

 

I think you will need to re-run the log collector again a create a new zip. Please wait while the data is collected - it can take a while to generate some of the logs.

 

I have tried three times and they are always empty. I will try again.

The instructions are different than what I see on the screen when I am trying to perform those operations.

 

I just received a message that says "All files have now been collected and are in a zipped folder on your desktop ready for you to upload to the forum. Press any key to continue"

So I am going to try it again.

 

It didn't create a zipped file. I will try it again.

 

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan
When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

4) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)

5) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)

https://support.microsoft.com/en-us/...oot-in-windows

How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

6) shutdown /r (you will reboot the computer so that it is in clean boot)

7) Attempt the DM log collector when in clean boot and post the zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums

 

Attachment 153134Attachment 153134

 

I finally have a log file that is not empty, can someone take a look at it.

Thanks

 

There are a range of different BSOD errors as you pointed out, these tend to suggest that you may have a hardware issue.

Some of the possible causes identified by WinDbg are shown below:

Code: BugCheck 7F, {8, ffff8400885c8bf0, ffff840088c38000, fffff802d7f78d6d} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption BugCheck 3B, {c0000005, fffff80250f47fd9, ffffaa001f7eb6e0, 0} Probably caused by : hardware ( nt!PfpPfnPrioRequest+2c9 ) BugCheck 7F, {8, ffffd40095e4fbf0, ffffd4009b8c7ec0, fffff80227a3496c} Probably caused by : memory_corruption[/quote] Please test your RAM: Note: this will probably take more than a day to complete the testing.





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

When available please post the results of the steps in post #11.
When you were able to generate the DM log was it after all of the steps?
Had you tried it after steps 1 -3 and before clean boot or only after clean boot?

 

I never could get the DM log to create a suitable file. I copied the TPfile into the DM log folder.

I am going to start the mem test right now.

Thanks for your patience.

leo