BLEEPINGCOMPUTER NEEDS YOUR HELP!
BleepingComputer is being sued by Enigma Software because of a negative review of SpyHunter.
A case like this could easily cost hundreds of thousands of dollars. If we have ever helped you in the past, please consider helping us. To learn more and to read the lawsuit, click here.
CONTRIBUTE TO OUR LEGAL DEFENSE
All unused funds will be donated to the Electronic Frontier Foundation (EFF).
LET OTHERS KNOW
You can press escape or click on the X to close this box.
Fatal System Error 0x00000402
Posted 16 January 2010 - 04:39 PM
anything I should be made aware of so that I don't massacre my comp?
BC AdBot (Login to Remove)
Posted 16 January 2010 - 04:45 PM
Read the topic...download the debugging tool...post any dump logs here.
Posted 16 January 2010 - 06:44 PM
Posted 16 January 2010 - 08:48 PM
1. Click Start, point to Settings, and then click Control Panel (Start>Control Panel in Vista).
2. Double-click System.
3. Click (Advanced system settings link in Vista, then --->)the Advanced tab, and then click Settings under Startup and Recovery.
4. Make sure, there is a checkmark in Write an event to the system log.
5. In the Write debugging information list, click Small memory dump (64k).
Posted 17 January 2010 - 02:36 AM
(Start>Control Panel in Vista)
You have the wrong forums, this is the XP forums... and my settings are right, ive debugged BSoD's before
Posted 17 January 2010 - 02:45 AM
Did the error happen just once?
Posted 17 January 2010 - 02:55 AM
I got home, my dad had the comp off (which is abnormal) I turned it on, the monitor didnt do anything til I noticed my dad turned off the monitor too, so I turned that back on, it loaded windows, flashed a cyan-like color and then hit the BSoD
Posted 17 January 2010 - 03:03 AM
just a FATAL SYSTEM ERROR. SYSTEM WILL NOW SHUT DOWN.
Posted 17 January 2010 - 12:22 PM
For some reason, it even didn't create any dump file, so there is really not much you can do at this moment, unless it happens again and gives you some info.
normally I wouldnt get a headache over it
Posted 17 January 2010 - 01:02 PM
This occurs when Windows switches into kernel mode and a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised. Security can no longer be guaranteed. Because Win XP canít run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can cause the system to stop responding. This Stop message also can occur as a result of malware infestation or when the computer is restarted after a system administrator has modified permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users