[attachment=32194:viber image.jpg]

I started getting this sudden shut downs about 3 weeks ago. This first time it started it was really scary, I thought I my computer was permanently damaged because it kept looping between blue screen error message - restart with very long fixing time - complete blank screen where absolutely nothing happened (and I have to force-shutdown) - blue screen error message. Finally after about 6 hours (tbh my heart was in my mouth all the while ... I didn't really keep track of time , but it felt like it continued for well over 6 hours)... after this long fixes, it seems my computer was fully restored -or so I thought

...I thought the problem was all over. But I was wrong. Now it still regularly suddenly shuts down and restarts with this blue screen abruptly appearing without warning (causing me to loose hours of work several times) to restart again. Sometimes 3 times a day, sometimes with a gap of 2/3 days in between. Though it never does the 6 hours thing again, I need to fix permanently , Not being an expert here I don't want to tinker with the Window 10

Searching for BAD POOL HEADER took me on a wild goose chase with many people suggesting many things - particularly for older versions of Windows.

Anyone have a clue of whats going on and how I can fix it or diagnose for a permanent fix? Or maybe its a well known problem with a ready fix?

(During the most recent blue screen, while shut out of Windows 10, I didn't have access to print-screen so I took a picture of the screen)

Many thanks

Edit: I found this recently, suggesting a number of fixes. Anyone know if any of these works better than relying on windows fixes?

Can you use BlueScreenView to check the parameters and then consolt this MSDN page?

Looking at the MSDN page indicates that it originates in a kernal driver somewhere.

before you do anything, BACKUP YOUR DATA BEFORE IT WON'T BOOT AT ALL!

you could be in serious bad mojo land here, do NOT take chances.

back it up, then start futzing with it.

worse comes to worse, reinstall - cause you have a backup now!

but seriously. back it up, very first thing. she might be going down. you don't want it to take all your source code and assets with it.

in the end its sounds like a corrupt config file or maybe a bad spot on the hard drive at an unfortunate location (like where win10 system files are).

back it up, start with a checkdisk, then work your way up from there.

WhoCrashed is the easiest tool for reading dump files - and it's free !

Thanks everyone for the advice, I am checking each advice you have given

Things are getting worse, I just got this

[attachment=32226:crash2.jpg]

I should have expanded the "Show details" first before closing it, but me being in panic mode now means I am missing out on some things at times

So I first need to back up my stuff on one drive

I do back up of course Like Noman Barrows says, but I just never backed up on onedrive before. I need to do that first because my normal external disk space is not large enough

Then afterwards see what the reported damage is all about. What's the possible consequences if I ignore "shutdown, don't use until repair" warning?

Does any one know if microsoft's onedrive is a good place for backups, particularly considering security and privacy issues?

Thanks everyone for the advice, I am checking each advice you have given

Things are getting worse, I just got this

crash2.jpg

I should have expanded the "Show details" first before closing it, but me being in panic mode now means I am missing out on some things at times

So I first need to back up my stuff on one drive

I do back up of course Like Noman Barrows says, but I just never back up on onedrive before. I need to do that first because my normal external disk space is not large enough

Then afterwards start the recovery process

Does any one know if microsoft's onedrive is a good place for backups, particularly considering security and privacy issues?

I think you can cover the security issue by using a archiving (7Zip, WinRar, Etc) (even if it is just using the minimum compression ratio) to and encrypting the contents.

You mentioned that the crashes are more frequent now. Is there an average (even a rough guess at one) up time your machine has between crashes? If it's reliably a couple of hours you can index the files on your hard drive (a powershell script would do it just fine, and quickly) and then set up a schedule to compress/upload/copy-to-thumb-drive pre-sized chunks of data in order of importance. It would suck to be in the middle of backing something up and then have your computer do a hard restart and corrupting your backup.