I bought a new Windows XP System from Wales, got it shipped down, installed an OS and everything, and all was fine. I left it on that night, woke up to find it stuck on a BSOD (I automatically disable automatic reboot when I install). Since then i've been having so much trouble. It started with SP2, i'm now back on a standard XP Version, straight from the CD - no service packs or updates at all, and no other software (Firewall running through network - so not a great chance of getting anything serious)

didnt seem to post the rest

Here's the system info that i'm aware of, for any more info, ill take a look :P
• 400W PSU
• ASRock K7VT4A / K7S8X DDR400
• AMD Sempron 3000+
• Standard Floppy Drive
• 80GB ATA133 7200RPM IDE HDD
• Sony 16xDVD-ROM
• LiteOn DVD-RW/+RW 16x Dual
• 128MB GeForce FX5200 DDR x8 (AGP)
• 256DDR 333 PC2700

I had three BSODs, straight after one another, after another boot. The causes were the same, and i seem to be getting two DIFFERENT BSODs. Here's the info i have:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 18/05/2005
Time: 20:34:10
User: N/A
Computer: X8
Description:
Error code 1000008e, parameter1 c0000005, parameter2 80537215, parameter3 f0fedb80, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 38 30 35 33 37 32 31 35 80537215
0040: 2c 20 66 30 66 65 64 62 , f0fedb
0048: 38 30 2c 20 30 30 30 30 80, 0000
0050: 30 30 30 30 0000

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 18/05/2005
Time: 20:33:42
User: N/A
Computer: X8
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0x9b606a2c, 0x00000000, 0xf9d70906, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini051805-03.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

As you can see, the system name is 'X8', don't quite know why... but that has no relavance to the problems, as the name was previously 'DAN'

Any help would be VERY much appreciated

DaN

Originally Posted by dhbedson

I bought a new Windows XP System from Wales, got it shipped down, installed an OS and everything, and all was fine.

If you bought a new XP system why did you have to install an OS ?

oops! XP-Supported, like almost all systems these days, capable of running XP sorry about that confusion!

(XP was the recommended OS for the system)

was this machine tested before you got it ? it may be a hardware maybe RAM issue..

not that I was aware, no. It was a newly built system, but of course, hardware could still be a problem. I guessed that it COULD be the video drivers. I updated them, but no luck.

I also used Microsoft's Memory Diagnostics Checks, in extended mode. All tests passed twice, could that still mean that its a RAM issue?

Thanks again

I googled this and most of the answers seem to point to hardware maybe RAM..when you first got the machine and installed XP did it ever work ?

as soon as I installed XP, i immediately upgraded to SP2. All was fine, started installing software in the morning, with many reboots, instead of installing bundles of software and rebooting in just 'one go'. All was fine, I left the system on and connected to the internet overnight to find the BSOD the next morning. It was the same error as the first one provided ^^. I have googled quite a lot myself (thats what brought me here). but I did run Diagnostics, maybe I should try some more, maybe an hour's worth or something?

Thanks again

For a more detailed error report do the following:

Go to start | search (type in) .dmp
Note the location of your latest .dmp file.

Then:

1) Download and install the
Debugging Tools from Microsoft
2) Download and install this
debugwiz
3) Open the Wiz & Browse to, or paste in the path to, your latest .dmp file.
4) After the Wiz creates a Text document attach it back to this thread.

hmm... i used the browse button provided, selected the file and....

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini051905-01.dmp]
Could not open dump file [C:\WINDOWS\Minidump\Mini051905-01.dmp], Win32 error 1392
"The file or directory is corrupted and unreadable."

lovely