|
19 Jul 2003, 17:03
|
#1
|
Hamster
Join Date: Apr 2000
Location: Crewe, England
Posts: 3,606
|
[WinXP] Blue Scree Hardware Errors
Ive been getting a number of these for the last couple of weeks (roughly one a day). The problem however is the Blue screen flashes up and then the machine immediatly reboots. This is obviously little use for identifying the problem.
So My question is does windows keep a record of these errors anywhere and if so where?
__________________
Wakey
PD and Suggestions Moderator
Co-founder of [F-Crew]
The Farnborough Crew
Cos anything else is just an alliance
Join our public channel at #f-crew
|
|
|
19 Jul 2003, 17:28
|
#2
|
First Disciple of Aldur
Join Date: Jul 2000
Location: The Vale of Aldur
Posts: 1,470
|
Control panel > system > advanced > Start up and Recovery "settings" > untick Automatically Restart
Control panel > Administrative tools > Event Viewer > system > Look for "save dump" in the 'Source' column. It will tell you what the bugcheck was.
__________________
Yeah.
|
|
|
19 Jul 2003, 18:05
|
#3
|
Gubbish
Join Date: Sep 2000
Location: #FoW
Posts: 2,323
|
Don't worry, it's just the heat.
__________________
Gubble gubble gubble gubble
|
|
|
19 Jul 2003, 19:15
|
#4
|
-=Murderous Plush Toy=-
Join Date: Nov 2001
Posts: 971
|
I had that, but it was with Win98SE, and it happened every time I booted up and it was during winter....
sorry, not help here, just wind back to a previous setup when it was working fine.
__________________
-Lucky #plush
__________________
Does anyone actually play this anymore?
|
|
|
21 Jul 2003, 12:01
|
#5
|
Hamster
Join Date: Apr 2000
Location: Crewe, England
Posts: 3,606
|
Cheers
__________________
Wakey
PD and Suggestions Moderator
Co-founder of [F-Crew]
The Farnborough Crew
Cos anything else is just an alliance
Join our public channel at #f-crew
|
|
|
22 Jul 2003, 04:03
|
#6
|
Registered User
Join Date: Jun 2003
Location: stow, london
Posts: 78
|
i had that problem when i got hold of a copy of XP and was attempting to put it on my gf's pc...
i got it onto her comp, but her comp couldnt handle it well, it didnt meet the minimum requirements... so the blue screen kept coming up most reboots...
and yes, the earlier post about checking out bug report will give you more details on what it is up. i think you should make sure the pc meets the requirements. if it does, save everything (if your computer is even accessable anymore) and format the HDD, and reinstall XP (unless ofc bug report helps)
__________________
You know you love meh
|
|
|
22 Jul 2003, 10:22
|
#7
|
Hamster
Join Date: Apr 2000
Location: Crewe, England
Posts: 3,606
|
More than Meets the spec and has been working fine for over a year now. It only really does it when I try and use anything too graphically intensive (playing video files is the worst)
__________________
Wakey
PD and Suggestions Moderator
Co-founder of [F-Crew]
The Farnborough Crew
Cos anything else is just an alliance
Join our public channel at #f-crew
|
|
|
22 Jul 2003, 12:07
|
#8
|
Throwing Shapes
Join Date: Apr 2000
Posts: 797
|
My mate had a problem playing video on his new system (and to that end opengl / direct3d) - caused exactly the same problem. Couldnt play video and (ir)regular blue screen/mem dumps.
It turned out to be the memory (was sold the wrong type). Replacement memory fixed the problem straight away.
Im not saying you've changed the memory but it may be simply due to a faulty memory or video memory chip (Yep sometimes its not Windows )
|
|
|
22 Jul 2003, 18:16
|
#9
|
Born Sinful
Join Date: Nov 2000
Location: Loughborough, UK
Posts: 4,059
|
Now you've been told how to stop it restarting, would you mind letting us in on what the error is?
Just speculating on the info you've given, a couple of likely causes could be bad memory (as mentioned allready), or the graphics card itself overheating.
__________________
Worth dying for. Worth killing for. Worth going to hell for. Amen.
|
|
|
23 Jul 2003, 10:29
|
#10
|
Hamster
Join Date: Apr 2000
Location: Crewe, England
Posts: 3,606
|
Quote:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xe2865008, 0x00000002, 0x00000000, 0x805e42a1). A dump was saved in: C:\WINXP\Minidump\Mini072003-02.dmp.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
|
Been trying to hunt down some more info on what this is.
As for bad memory I personally doubt its this. Having been burnt by buying cheap mem in past and thus having all sorts of problems, I always make sure i'm buying good quality RAM. Not to mention this has already been checked with my two 256mb chips being replaced by the two chips out of the second machine and the single 512 chip in the third one. All which give the same errors
__________________
Wakey
PD and Suggestions Moderator
Co-founder of [F-Crew]
The Farnborough Crew
Cos anything else is just an alliance
Join our public channel at #f-crew
|
|
|
23 Jul 2003, 11:39
|
#11
|
Born Sinful
Join Date: Nov 2000
Location: Loughborough, UK
Posts: 4,059
|
If you have stopped it from restarting as soon as it bluescreens, next time it happens write down the message on the bluescreen itself (don't bother with the memory addresses - they probably only mean anything to a few MS engineers and certainly don't mean anything to me).
__________________
Worth dying for. Worth killing for. Worth going to hell for. Amen.
|
|
|
|
All times are GMT +1. The time now is 00:57.
| |