Weird reboot..

[klarrix]

Hey,

Every so often (once every fortnight or so) my PC suddenly decides to restart in the middle of whatever i'm doing.

Out of nowhere it will momentarily switch to an MS DOS style blue screen with far too much writing on it for me to understand what it's on about, before promptly rebooting. It tends to happen during me playing video games or running something visual, but just now it happened mid-MSN convo with nothing else going on in the background.

When it comes back to the desktop after starting up again I get a "Windows has recovered from a serious error" box, with (incase this helps at all) the following details:

BCCode : d1 BCP1 : 7500830D BCP2 : 00000002 BCP3 : 00000000
BCP4 : F3574A0E OSVer : 5_1_2600 SP : 1_0 Product : 768_1

Means nothing to me, but someone might make sense out of it (it has to be there for a reason, right?)

Can anyone explain what is happening and how to prevent it doing this again?



System: AMD Athlon XP barton 2500 (running Win XP)
Abit NF7-s
512Mb PC2700 184pin DDR DIMM Memory
GeForce FX5600 128Mb Ultra/760 TV-DVI

[Howard]

Have you been doing any overclocking?

These BSODS (Blue Screen of Death) are usually caused by instability or hardware conflicts. Most likely the former if you've been OCing

[klarrix]

As it happens, Mick kept on pestering me to overclock when i first got my system but i never did because i was afraid of the instability, so no.

[GreenPiggy]

Could be wrong but that tends to happen to me when i'm maxing out the RAM when overclocking. Try running memtest on it or the Prime95 RAM torture test.
What make is that RAM?

[mike_w]

Try turning off the option to automatically reboot at BSODs (in Windows 2000, its Control Panel/System/Advanced/Startup and Recovery. Just untick the check box "Automatically reboot" so that you have a look at the stuff on screen.

What temps you at? Might be the hot weather causing it.

Might also be the PSU, what is it?

[nichomach]

kirb, next time it reboots, can you make a note of just the top couple of lines? It should actually give an error code (might start IRQL_NOT_LESS_OR_EQUAL or something followed by a short hex code, or list a device driver or file in which the error's occurred). Believe it or not, this can help narrow the field down a bit. An error code might read something like STOP : 0x00000079, and that error code tells the tale.

[klarrix]

i'll try, but it honestly hangs in the blue for two to three seconds, and when i don't understand what i'm reading it may mean i give the wrong info.


I'll bump this thread next time it happens

[nichomach]

Follow Mike w's advice re: turning off the automatic restart and it should stay on screen long enough for you to fully enjoy every last line of utter gibberish that it throws up, mate.

Also, if you can maybe grab a decent shot of the screen w/digicam, that might help, you could always post a link to it here and we can scratch our heads, look puzzled and say "Yep, that's definitely a BSOD".

[sybrows]

Follow Mike w's advice re: turning off the automatic restart and it should stay on screen long enough for you to fully enjoy every last line of utter gibberish that it throws up, mate.

Also, if you can maybe grab a decent shot of the screen w/digicam, that might help, you could always post a link to it here and we can scratch our heads, look puzzled and say "Yep, that's definitely a BSOD".

Good Plan Stanley
BrOw

[klarrix]

OK guys took all the advice, and as it happens the whole thing kicked in again ten mins ago so i caught what it showed me. Here it comes...

The problem seems to be caused by the following file: Ntfs.sys

Page_fault_in_nonpaged_area

Technical information:
stop: 0 X 00000050
(O X AFE878D7, 0 X 00000000
0 X F83D6811, 0 X 00000000)

Ntfs.sys- address F83D6811 base at F83D6000

Datestamp 3d6de5cl

[nichomach]

OK...are you using a USB reader at all with it as per http://support.microsoft.com/default...b;en-us;817197 ? Or have you added any hardware recently? The other immediate thought is that slightly older builds of Roxio EasyCD Creator 5 sometimes throw up this sort of error under XP, so it can be worth downloading the latest update. Defective memory has to be your prime suspect, though. Have a look at http://www.microsoft.com/resources/d...d_stp_ccgm.asp, and also http://www.memtest86.com/ .