Computer gone wonky

Tusky

Over the last few weeks my pc seems to have gone haywire. Im getting regular blue screen of deaths which results in the computer restarting by itself. Ive also been having issues with both firefox & IE, both of which I have updated. I dont know whether the problems are related but they began around the same time.

Streaming videos wont play fully in firefox and firefox will randomly close itself. IE will often freeze and then close itself.

Ive updated adaware & AVG and done full scans but it hasnt helped.

TerrorFirmer

The first thing to do is get the blue screen codes and post them here...

Tusky

TerrorFirmer wrote: »

The first thing to do is get the blue screen codes and post them here...

It only flashes up for about a second. Is there another way to retrieve them ?

PogMoThoin

Right-click My Computer, and then click Properties. Click the Advanced tab. Under Startup and Recovery, click Settings to open the Startup and Recovery dialog box. Clear the Automatically restart check box, and click OK the necessary number of times. Restart your computer for the settings to take effect.

Tusky

PogMoThoin wrote: »

Right-click My Computer, and then click Properties. Click the Advanced tab. Under Startup and Recovery, click Settings to open the Startup and Recovery dialog box. Clear the Automatically restart check box, and click OK the necessary number of times. Restart your computer for the settings to take effect.

Done. Cheers.

Tusky

Ok, I just got the blue screen again. Heres roughly what it said.

'A process of thread crucial to system operation terminated etc'

Then it asked if I have installed any hardware recently (which I haven't) or software (which I have).

The only code it gave is as follows, STOP 0x000000F4 (0x0000003, 0x89E61788, 0x89E618FC, 0x805D13B6)

It suggests changing shadowing & caching options in the BIOS menu.

The bluescreen happens when I'm not using any software (apart from IE or Firefox) so I assume that means the software isnt to fault ?

Any ideas ?

kleefarr

0x000000F4: CRITICAL_OBJECT_TERMINATION

One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive; compare KB 330100.

Tusky

kleefarr wrote: »

0x000000F4: CRITICAL_OBJECT_TERMINATION

One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive; compare KB 330100.

'when resumed from standby'.

My problem happens when I'm using the computer. No standby involved.

kleefarr

Re: KB330100

"or

0x000000F4 (0x00000003, Parameter2, Parameter3, Parameter4)
Note Parameter2, Parameter3, and Parameter4 in the stop error may vary.

This problem occurs on a computer in which Windows XP or a later operating system is installed on a hard disk that is configured as a subordinate and no other device is connected to the same IDE controller channel (primary or secondary).
Back to the top

CAUSE
This behavior may occur when you use Windows XP or a later operating system with some motherboards. Microsoft is researching this problem and will post more information in this article when the information becomes available."

Any good? Seems like a known problem that the F4 stop error refers to.

Tusky

kleefarr wrote: »

Re: KB330100

"or

0x000000F4 (0x00000003, Parameter2, Parameter3, Parameter4)
Note Parameter2, Parameter3, and Parameter4 in the stop error may vary.

This problem occurs on a computer in which Windows XP or a later operating system is installed on a hard disk that is configured as a subordinate and no other device is connected to the same IDE controller channel (primary or secondary).
Back to the top

CAUSE
This behavior may occur when you use Windows XP or a later operating system with some motherboards. Microsoft is researching this problem and will post more information in this article when the information becomes available."

Any good? Seems like a known problem that the F4 stop error refers to.

Cheers mate. Unfortunately sounds like there isnt a fix for it...

kleefarr

Yep, doesn't look very promising dos it.
Did you try any other tests? Memory or HDD tests? (Just a thought)

zilog_jones

An easier way of reading BSOD errors is to look in the event viewer in Computer Management afterwards (IIRC it always records them there).

BSODs in XP are usually some form of hardware issue.

Do you know if Windows is installed on a slave drive with no other present drives? I forget how to check that as I don't have admin rights on the PC I'm using here...

Tusky

kleefarr wrote: »

Yep, doesn't look very promising dos it.
Did you try any other tests? Memory or HDD tests? (Just a thought)

No. Wouldnt know how to go about it. Care to elaborate ?

zilog_jones wrote: »

An easier way of reading BSOD errors is to look in the event viewer in Computer Management afterwards (IIRC it always records them there).

BSODs in XP are usually some form of hardware issue.

Do you know if Windows is installed on a slave drive with no other present drives? I forget how to check that as I don't have admin rights on the PC I'm using here...

I know there is only one hard drive on the pc. There are two copies of windows installed on it. Not sure about the slave drive as I dont know what that is. Im guessing its a drive that doesn't have a OS on it ?