R
Ray Parrish
Hello,
I booted into Windows XP, SP3 on my EMachine T3410 this morning for the
first time in about a week and a half [I dual boot Ubuntu and have been
using that for the most part] and got the error in the subject line
before everything had completely loaded in Windows.
I rebooted to see if the error persisted and noted that on the second
boot that almost everything had loaded, but the chat program [Windows
Live Messenger] was still trying to sign in when the BSOD happened again.
The last time I was in Windows successfully I only used my checking
account program, then shut down, When shutting down I noted that Windows
had downloaded updates as it warned me it was going to install them upon
shutdown.
I've researched it briefly using google, and it seems to be a widespread
occurrence with varying causes. It was recommended that one run
Microsoft's verifier [driver verifier] and also to run a memory test.
I'm pretty sure it's not the memory as I'm running just fine in Ubuntu,
so it must be the update that was just installed.
Does anyone have any other tips on what I might try to do to solve the
problem?
Later, Ray Parrish
I booted into Windows XP, SP3 on my EMachine T3410 this morning for the
first time in about a week and a half [I dual boot Ubuntu and have been
using that for the most part] and got the error in the subject line
before everything had completely loaded in Windows.
I rebooted to see if the error persisted and noted that on the second
boot that almost everything had loaded, but the chat program [Windows
Live Messenger] was still trying to sign in when the BSOD happened again.
The last time I was in Windows successfully I only used my checking
account program, then shut down, When shutting down I noted that Windows
had downloaded updates as it warned me it was going to install them upon
shutdown.
I've researched it briefly using google, and it seems to be a widespread
occurrence with varying causes. It was recommended that one run
Microsoft's verifier [driver verifier] and also to run a memory test.
I'm pretty sure it's not the memory as I'm running just fine in Ubuntu,
so it must be the update that was just installed.
Does anyone have any other tips on what I might try to do to solve the
problem?
Later, Ray Parrish