Microsoft investigates Windows 7 'screen of death'
- Thread starter dekez
- Start date
Associate
- Joined
- 9 Aug 2009
- Posts
- 1,517
- Location
- Internet
I switched to a 4650 from a 4770 for awhile since i was just surfing the net since there was no games to plays, after doing the hardware change i started to get this black screen a lot but was mainly coming out of sleep mode, i got it twice during day to day use.
After getting sick of the issue i switched back to my 4770 and the black screens stop after that so i have no clue what was causing the problem.
After getting sick of the issue i switched back to my 4770 and the black screens stop after that so i have no clue what was causing the problem.
Associate
- Joined
- 3 Jan 2007
- Posts
- 1,107
- Location
- Scotland
look like to be fake: http://windowsitpro.com/windowspaul...microsoft-black-screen-of-death-is-bogus.html
Shouldn't need to. Windows automatically restarts Explorer if it crashes. It's had this behaviour since about Windows 2000 if I remember correctly.
...funny that, because i had this black screen of death a couple of days ago. My monitor all of a sudden reported there was no video signal and my PC crashed.
After a reboot i expected an error report, but nothing. PC has ran fine since ........
After a reboot i expected an error report, but nothing. PC has ran fine since ........
Windows crashing isn't news.
On a related note, does it crash for people who know what they're doing with it? I know even less about windows than I do about linux, so I tend to blame myself when either system goes down. I'd be interested to know if blue screens/black screens/general eating of work is unavoidable with windows or down to user error.
On a related note, does it crash for people who know what they're doing with it? I know even less about windows than I do about linux, so I tend to blame myself when either system goes down. I'd be interested to know if blue screens/black screens/general eating of work is unavoidable with windows or down to user error.
As mentioned, a stable setup just "crashing" is extremely rare. I saw a Windows NT server with an uptime of something daft like 18 months last year - and I'm sure people have seen Windows uptimes that dwarf that.
Windows crashes are usually the result of failing hardware, bad drivers and/or malware. I'm not saying Windows is perfect and never crashes - it's just nowhere near as much as people make out.
Windows can be a victim of its own success sometimes. It supports virtually anything you throw at it hardware-wise and is a relatively easy platform to program for. It is also massively dwarfs the other OS's in terms of the amount of users.
Put all that together and you will get crap software, badly coded drivers and the inevitable crashes. The fact that something like 90% of computers use Windows you get to hear about it, a lot.
OSX on the other hand is lovingly crafted to suit Apples equally lovingly crafted hardware. It's anal beyond belief. When you don't let anyone near it it is much easier to make it more stable. Having said that you pay a hefty premium for the privilege. Plus you look like a pretentious tit. I still want a Macbook Pro though! lol
Linux on the other hand is still very much the preserve of the geek. So in most cases if something goes wrong someone turns off WOW and goes and fixes it. If they screw up there are 200 other people with their own fixes.
In my view none of the above OS are bad and they all have some really great ideas. The fact is which you choose is down to how you like to roll. Any one of them can be made to crash if you install rubbish software.
Put all that together and you will get crap software, badly coded drivers and the inevitable crashes. The fact that something like 90% of computers use Windows you get to hear about it, a lot.
OSX on the other hand is lovingly crafted to suit Apples equally lovingly crafted hardware. It's anal beyond belief. When you don't let anyone near it it is much easier to make it more stable. Having said that you pay a hefty premium for the privilege. Plus you look like a pretentious tit. I still want a Macbook Pro though! lol
Linux on the other hand is still very much the preserve of the geek. So in most cases if something goes wrong someone turns off WOW and goes and fixes it. If they screw up there are 200 other people with their own fixes.
In my view none of the above OS are bad and they all have some really great ideas. The fact is which you choose is down to how you like to roll. Any one of them can be made to crash if you install rubbish software.
Device drivers (i.e. kernel drivers that control some hardware) are *usually* OK these days. It's been a long time since I've had any such issues anyway. But that may be because all my PC's and friends/family have Intel PCs which tend have to rock solid chipset drivers.
However, other forms of kernel driver, particularly those related to security software or CD/DVD burning tend to be ****. That is because they are effectively "rootkits". They hook into all sorts of areas in the kernel that they really shouldn't be. Their authors *think* they know what they're doing but actually they only know half of what they need to know. It's so easy to not spot a concurrency issue in kernel space.
Thankfully the problem is not as bad on Windows x64 because the 64-bit kernel has something called PatchGuard that actively tries to prevent these hooks from being inserted. But even still, you get companies like "PrevX" that see this as a challenge and try to circumvent it. Only to be scratching their heads on the next Patch Tuesday when their customers PC's stop working because Microsoft changed the PatchGuard algorithms again.
However, other forms of kernel driver, particularly those related to security software or CD/DVD burning tend to be ****. That is because they are effectively "rootkits". They hook into all sorts of areas in the kernel that they really shouldn't be. Their authors *think* they know what they're doing but actually they only know half of what they need to know. It's so easy to not spot a concurrency issue in kernel space.
Thankfully the problem is not as bad on Windows x64 because the 64-bit kernel has something called PatchGuard that actively tries to prevent these hooks from being inserted. But even still, you get companies like "PrevX" that see this as a challenge and try to circumvent it. Only to be scratching their heads on the next Patch Tuesday when their customers PC's stop working because Microsoft changed the PatchGuard algorithms again.
I used to have a Pentium 2 400MHz as an ADSL router (amongst other things). With the help of an APC UPS, I achieved this:
