Microsoft Robots to Watch Kids 544
Archangel Michael writes "Microsoft announced today that is testing a new toy / robot
to watch over kids. My question is, if the toy BSOD does it take the
kid with it? Now we are letting inanimate objects raise our kids! When
will it end?"
Re:BSOD (Score:2, Informative)
Re:BSOD (Score:2, Informative)
Patrick
Re:BSOD (Score:1, Informative)
Re:BSOD (Score:3, Informative)
C:\> ping localhost [enter] [F7] [enter] [f7] [enter] [f7] [enter]
STOP CONDITION...
Not fixed until SP4 (or was it 6?)...
But yeah, I haven't seen XP BSOD without turning off "immidiately reboot on crash" either
Re:BSOD (Score:5, Informative)
1. Start regedit. (If you are unfamiliar with regedit, please refer to this FAQ)
2. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
3. Create a new DWORD value and name it CrashOnCtrlScroll
4. Right-click on this newly created value and click on Modify
5. Enter 1 in the Value data field and click on OK.
6. Close regedit and reboot your system.
7. Now you can blue screen (crash) your system by holding the right CTRL key and pressing "Scroll Lock" twice.
Note:
Your system may reboot or show a blue screen whenever this crash is initiated. If your system reboots after initiating the crash, and you want to see the blue screen, follow these steps:
1. Go to Control Panel > System
2. Click on the Advanced tab
3. Under Startup and Recovery, click the Settings button.
4. Under System failure, uncheck the option Automatically restart.
Happy crashing...
cudos to http://www.tweakxp.com/article140073.aspx [tweakxp.com]
Re:BSOD (Score:2, Informative)
I'm a Linux user, and I have had blue screens on every Win OS between 95 and Win2k3 Server. Win 3 used to just freeze or drop back to DOS.
Re:BSOD (Score:3, Informative)
Re:BSOD (Score:3, Informative)
I'd say on average I get one or two BSODs in a month. Mostly this is driver related (e.g. Nvidia + HL2), but I have instances where the machine has blue screened for no apparant reason whatsoever. The machine was under some kind of load, e.g. a compiler + some apps and then *poof* it blue screened with some kind of NTOSKRNL exception. Considering that I reboot my machine everyday so that it never runs for more than 16 hours, I'd say this is pretty poor. And yes my box is service packed, drivers are up to date etc. etc.
OS X isn't perfect either, but in the two years and several iterations of 10.x, I've only seen two panics. Panics on Linux have been rarer than hens teeth. The only time I've seen that crash at all was when I've been screwing around with the kernel source and forgotten to do important something such as mkinitrd or whatever.
Re:BSOD (Score:3, Informative)
If you think XP is all that you are dreaming. I've seen XP machines so infested with spyware and whatnot that BSOD's are a common occurance.
Re:BSOD (Score:3, Informative)
You may notice that the original poster said I know it's physically capable of a BSOD, but really, has anyone ever seen XP or 2000 SP3 actually BSOD on a regular basis. My experience is that XP itself is incredibly stable. Infinitely more so than 95 or 98.
Note he said XP/2000 don't regularly bluescreen, he did not say they never bluescreen. Please learn to read more carefully.
MS Support Tells You How-to: (Score:3, Informative)
i imagine this is very, very helpful to some developers who work with data protection and need to test-crash junk all the time.
Re:BSOD (Score:3, Informative)
MTW
Re:BSOD (Score:2, Informative)
Re:Look, he made a BSOD joke! He's funny AND origi (Score:3, Informative)
Then I RTFA and see it's a baby monitoring device. Everyone can simma down nah.
Re:agh (Score:5, Informative)
Besides, this isn't just old news [cnn.com]. It still happens [themacobserver.com].
Re:BSOD (Score:3, Informative)
Ahh, yes, the joys of having a $300 audio card that BSOD's because Windows doesn't deal with the drivers well. I had a very similar problem
Remove all drivers in Safe Mode. Make sure nothing is in the 'Recycle (preserve viruses) Folder. Delete all temporary files. Reboot, and install up-to-date drivers.