Blue screen of death
Joined: Jul 2015
Aviation Qualifications: CPL
Posts: 140
Likes: 29
From: Miles away
Yes, many times. It is a sign of a possible major malfunction. Rebooting usually sorts thing out.
But if it reoccurs, take a note of the error code and Google that for help.
But if it reoccurs, take a note of the error code and Google that for help.
Joined: Jun 2002
Aviation Qualifications: PPL
Posts: 7,176
Likes: 297
From: Nanaimo (CAC8)
Yes, turn it off and on again. If the BSOD is still there, you turned the monitor on and off. Try the computer next time! 
On a more serious note, see here:
https://en.wikipedia.org/wiki/Blue_Screen_of_Death
On a more serious note, see here:
https://en.wikipedia.org/wiki/Blue_Screen_of_Death
Joined: Apr 2008
Aviation Qualifications: Spotter
Posts: 612
Likes: 249
From: on the ground
Joined: Oct 2007
Posts: 1,003
Likes: 16
From: Here
If it's a one off, don't worry about it.
Note that any of the below steps could stop the computer from working. you need good backups of critical files. Saying that, I would do these steps on my computer but I don't really have super critical stuff on it.
If it is recurring -
1.
Consider undoing any recent changes to the computer that may have made it occur.
2.
check operating system integrity with
chkdsk /r
sfc /scannow
If sfc reports that it can not fix it use
DISM /Online /Cleanup-Image /RestoreHealth
and repeat sfc /scannow -
If that dism command reports that it can't fix it it is more complex than I can deal with.
Sometimes you need to repeat the sfc /scannow - I think it tells you that it is not finished.
3.
Check the windows logs with Event Viewer for messages that indicate a serious problem shortly before the crash.
Windows Logs/Application
Windows Logs/System
4.
Enable minidump and use a dump analyser to see if the crash is being consistently caused by a particular file. If that file is associated with some particular software consider re-installing it. Everyone should enable minidumps anyway - else on a crash the system will write the whole active virtual memory to a file which takes a LONG time. I would get fed up and turn the machine off which MAY compound the problem.
Finally - I am not recommending the installation of any software off of the Internet - you need to research such software yourself and evaluate the risk.
[B} below has some good stuff
You can also start by that:[list]
Note that any of the below steps could stop the computer from working. you need good backups of critical files. Saying that, I would do these steps on my computer but I don't really have super critical stuff on it.
If it is recurring -
1.
Consider undoing any recent changes to the computer that may have made it occur.
2.
check operating system integrity with
chkdsk /r
sfc /scannow
If sfc reports that it can not fix it use
DISM /Online /Cleanup-Image /RestoreHealth
and repeat sfc /scannow -
If that dism command reports that it can't fix it it is more complex than I can deal with.
Sometimes you need to repeat the sfc /scannow - I think it tells you that it is not finished.
3.
Check the windows logs with Event Viewer for messages that indicate a serious problem shortly before the crash.
Windows Logs/Application
Windows Logs/System
4.
Enable minidump and use a dump analyser to see if the crash is being consistently caused by a particular file. If that file is associated with some particular software consider re-installing it. Everyone should enable minidumps anyway - else on a crash the system will write the whole active virtual memory to a file which takes a LONG time. I would get fed up and turn the machine off which MAY compound the problem.
Finally - I am not recommending the installation of any software off of the Internet - you need to research such software yourself and evaluate the risk.
[B} below has some good stuff
You can also start by that:[list]
- Update all possible drivers
- Uninstall all unused programs
- Run chkdsk /r /f and sfc /scannow
- Perform a clean boot: http://support.microsoft.com/kb/929135
- Disable temporary all security softwares you have
- Run memtest86+ to check your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support for assistance
[A] https://www.ghacks.net/2018/03/16/us...sues-sfc-cant/
[B] https://social.technet.microsoft.com...m=winservergen
[C] https://www.raymond.cc/blog/how-to-a...dump-dmp-file/
Administrator
Joined: Mar 2001
Aviation Qualifications: PPL
Posts: 8,121
Likes: 686
From: Twickenham, home of rugby
Good thoughts there from Helix and Jim.
On the hottest day of the year, one of my hard disks shut down - a 7.2K spinning disk. Not the CPU or graphics card, or system disk (SSD), just the data drive. I assume it was due to the heat, although tests didn't indicate an overtemp event. Everything is backed up, but I didn't need to restore, as the disk came back once everything had cooled down. I will continue to use it, on the basis that it's backed up regularly.
My experience has been that BSODs in PCs are very often down to faulty memory or failing PSUs in particular.
On the hottest day of the year, one of my hard disks shut down - a 7.2K spinning disk. Not the CPU or graphics card, or system disk (SSD), just the data drive. I assume it was due to the heat, although tests didn't indicate an overtemp event. Everything is backed up, but I didn't need to restore, as the disk came back once everything had cooled down. I will continue to use it, on the basis that it's backed up regularly.
My experience has been that BSODs in PCs are very often down to faulty memory or failing PSUs in particular.
Joined: Apr 2008
Posts: 565
Likes: 21
From: Passed away on Sept 6th
Just something that hasn't been mentioned - not likely, but worth asking...
You're not by any chance still using Windows XP would you? or even Windows h eight?
BSOD frequent before I moved to 7, only twice since then, yonks ago.
You're not by any chance still using Windows XP would you? or even Windows h eight?
BSOD frequent before I moved to 7, only twice since then, yonks ago.
Joined: May 2009
Posts: 611
Likes: 62
From: Down under
Wot the Rev Jim said - with emphasis. Not altogether uncommon on XP - a semi regular occurence or 98 / 95 (is there anyone other than me that goes back that far?).
Not seem on w7 or w10 - but there's still time
Not seem on w7 or w10 - but there's still time
Administrator
Joined: Mar 2001
Aviation Qualifications: PPL
Posts: 8,121
Likes: 686
From: Twickenham, home of rugby
I started using IBM & compatible PCs back in the mid 1980s, with whatever version or flavour of DOS was to be found on a 5.25" floppy. Oh the luxury of having 2 floppy drives! The really fortunate had internal hard drives with as much as 10MB of storage! Like PDR1, my first experience of Windows was monochrome, I can't remember what version, but I do remember Windows 3.0 in full colour, running on DOS 4 (or 5, it's a bit hazy). By the time that Windows 3.1 came out and was actually pretty usable, DOS was definitely at 5.0. Windows 3.11 for Workgroups on DOS 6.2 was my first MS Certification - I have a 4-digit MCP number, which no-one believes is genuine! It was challenging to get all the drivers you needed loaded into high memory in those days, it's far too simple now.
BSODs were the norm, not the exception.
SD
BSODs were the norm, not the exception.SD
Gnome de PPRuNe
Joined: Jan 2002
Aviation Qualifications: Spotter
Posts: 15,198
Likes: 1,201
From: Too close to Croydon for comfort
I had a BSOD on a desk top a few years ago - rebooting didn't help, neither did our help desk. IT engineer came round, switched off and said "leave it five minutes". It worked, something to do with letting residual power ebb away.
Had a dodgy lap top as well, recommendation there was to remove battery and disconnect CMOS battery as well for a few mins. That also worked.
Had a dodgy lap top as well, recommendation there was to remove battery and disconnect CMOS battery as well for a few mins. That also worked.
Joined: Nov 2002
Posts: 171
Likes: 6
From: Tapping the Decca, wondering why it's not working.
Of course the owners of BBC Micro, Sinclair Spectrum, Radio Shack TRS-80 and similar devices can top that.
'a
Last edited by aerobelly; 2nd August 2019 at 19:31.
Joined: May 2009
Posts: 611
Likes: 62
From: Down under
Pah! W95 is the johnie-come-latey. My first home machine ran DOS 3.1 and WIndows 386, but I'd been using them in the office back to DOS 2.11 and occaisionally firing up Windows 2.03 (on a twin-floppy machine with a monochrome display).
My first computer was the TRS80 model I with a cassette tape storage system . I later spent a small fortune on an external interface box with floppy drives (single sided - 360KB) and TRSDOS 1.3. Of course I used a hole punch and a notch to make floppies into flippies - double the capacity. With 360k disks at $4 each, it was something of a saving. I later bought a TRS80 model IV; I still have it. I get it out every so often to listen to the sounds of floppy drives and their musical clunk. I must connect up my original Epson MX-80 printer ($850 back in the early 80s) for extra sound nostalgia.
No BSODS in those days - they worked as expected and the screen was green anyway. TRS80s are making a comeback amongst hardware geeks. There are clever interfaces available to put everything ever written for them on a single SD card. I'm not sure what happens after that. Perhaps they also have a dot matrix printer running off the Centronics port ....
Thread Starter
Joined: Nov 2007
Posts: 600
Likes: 2
From: Thailand
Thanks for all the advice!I shall get on to it in the morn.I have a three year old Acer laptop which is a backup for my main and has hardly any progs on it .I mainly take it when I am away from home.it started as perhaps once a week but now its every 15 mins so i guess I will have to be quick!!
Joined: Mar 2013
Aviation Qualifications: Non-Aircrew
Posts: 78
Likes: 0
From: UK
Joined: Jan 2008
Aviation Qualifications: CPL
Posts: 598
Likes: 3
From: turn L @ Taupo, just past the Niagra Falls...
If it's a one off, don't worry about it.
Note that any of the below steps could stop the computer from working. you need good backups of critical files. Saying that, I would do these steps on my computer but I don't really have super critical stuff on it.
If it is recurring -
1.
Consider undoing any recent changes to the computer that may have made it occur.
2.
check operating system integrity with
chkdsk /r
sfc /scannow
If sfc reports that it can not fix it use
DISM /Online /Cleanup-Image /RestoreHealth
and repeat sfc /scannow -
If that dism command reports that it can't fix it it is more complex than I can deal with.
Sometimes you need to repeat the sfc /scannow - I think it tells you that it is not finished.
3.
Check the windows logs with Event Viewer for messages that indicate a serious problem shortly before the crash.
Windows Logs/Application
Windows Logs/System
4.
Enable minidump and use a dump analyser to see if the crash is being consistently caused by a particular file. If that file is associated with some particular software consider re-installing it. Everyone should enable minidumps anyway - else on a crash the system will write the whole active virtual memory to a file which takes a LONG time. I would get fed up and turn the machine off which MAY compound the problem.
Finally - I am not recommending the installation of any software off of the Internet - you need to research such software yourself and evaluate the risk.
[B} below has some good stuff
You can also start by that:[list]
Note that any of the below steps could stop the computer from working. you need good backups of critical files. Saying that, I would do these steps on my computer but I don't really have super critical stuff on it.
If it is recurring -
1.
Consider undoing any recent changes to the computer that may have made it occur.
2.
check operating system integrity with
chkdsk /r
sfc /scannow
If sfc reports that it can not fix it use
DISM /Online /Cleanup-Image /RestoreHealth
and repeat sfc /scannow -
If that dism command reports that it can't fix it it is more complex than I can deal with.
Sometimes you need to repeat the sfc /scannow - I think it tells you that it is not finished.
3.
Check the windows logs with Event Viewer for messages that indicate a serious problem shortly before the crash.
Windows Logs/Application
Windows Logs/System
4.
Enable minidump and use a dump analyser to see if the crash is being consistently caused by a particular file. If that file is associated with some particular software consider re-installing it. Everyone should enable minidumps anyway - else on a crash the system will write the whole active virtual memory to a file which takes a LONG time. I would get fed up and turn the machine off which MAY compound the problem.
Finally - I am not recommending the installation of any software off of the Internet - you need to research such software yourself and evaluate the risk.
[B} below has some good stuff
You can also start by that:[list]
- Update all possible drivers
- Uninstall all unused programs
- Run chkdsk /r /f and sfc /scannow
- Perform a clean boot: http://support.microsoft.com/kb/929135
- Disable temporary all security softwares you have
- Run memtest86+ to check your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support for assistance
[A] https://www.ghacks.net/2018/03/16/us...sues-sfc-cant/
[B] https://social.technet.microsoft.com...m=winservergen
[C] https://www.raymond.cc/blog/how-to-a...dump-dmp-file/
Joined: Oct 2007
Posts: 1,003
Likes: 16
From: Here
:-)
Joined: Jun 2009
Posts: 164
Likes: 13
From: UK
These days the highest probabilities (If a complete shutdown and reboot doesn’t fix it ) are
1). Same error every time.
Incorrect driver installed ( sometime by windows update)
Corrupt OS file (which may be listed in the Error message) or found as above with SFC
2). Different errors every time
Power supply, virus, memory (fault or bad contact with socket), disk( fault or bad contacts) ,
1). Same error every time.
Incorrect driver installed ( sometime by windows update)
Corrupt OS file (which may be listed in the Error message) or found as above with SFC
2). Different errors every time
Power supply, virus, memory (fault or bad contact with socket), disk( fault or bad contacts) ,