Windows 'preventing damage' to my PC

baby-mechanic

Hi folks

Switched PC on this morning to see it start it's normal boot-up regime, then to be met with a blue screen and the following message:

A problem has been detected and windows has been shut down to prevent damage to your computer.

If this is the first time you've sen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Disable or uninstallany antivirus, disk defragmentation or back up utilities. Check your hard drive configuration, and check for any updated drivers. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.

Technical information:

*** STOP: 0x00000024 (0x00190203, 0x82F34A98, 0xC0000102, 0x00000000)

I've restarted the PC and got the same screen, but can't seem to get to anywhere where I can run the CHKDSK, or soft boot.

Know enough to get me by on a day-to-day basis with my PC, but this is the first time I've seen this, and feel that i need any suggestions in words of less than one syllable

Thanks in advance

kwikbreaks

Won't it start up in safe mode?

Have you added any hardware recently? This is usually a driver problem. There is usually more displayed which you can search on than the stop code.

baby-mechanic

how do i start it in safe mode ?

personal brain cell off-line today, as that's waht i meant by soft boot !!

tronator

baby-mechanic wrote: »

how do i start it in safe mode?

http://lmgtfy.com/?q=windows+safe+mode

Press F8 at the beginning of the boot process.

baby-mechanic

No new hardware added.

Managed to use F8, and get that screen.

'Safe mode' option gives me the same blue screen.

'Start Windows normally' gives me the same blue screen.

'Last known good configuration' gave me a 'flash' of something, then a blank, black screen, and when I tried again, the blue screen.

Any other options ?

John_the_Boy

Do you have the original OS disc? If so boot with that in your CD and opt to repair you OS rather than reinstall.

baby-mechanic

Techie friend popped round, and was able to get the CHKDSK /F function running, and now sorted.

Thanks for looking in guys, and for the suggestions