The following information is all I could ascertain from Microsoft stuff. Essentially I went away to show someone something and came back to find everything had disappeared, a blue screen & white text telling me to close down, reboot if it was the first occurrence and if not to follow the additional instructions.

Microsoft's error report messages were:
BCCode : d1 BCP1 : F6A87328 BCP2 : 00000002 BCP3 : 00000000
BCP4 : F6A87328 OSVer : 5_1_2600 SP : 2_0 Product : 768_1

The relevant error report files are:
\DOCUME~1\Wendy\LOCALS~1\Temp\WER71c4.dir00\Mini09 1505-01.dmp
\DOCUME~1\Wendy\LOCALS~1\Temp\WER71c4.dir00\sysdat a.xml

And after I rebooted I found a link to this MS error report message: http://oca.microsoft.com/en/response.aspx?SGD=f06f2698-8094-490e-9493-a19f97b0e835&SID=10

As I havent added any new hardware devices I am worried silly. and dont know how on earth to find the device that caused this serious error?

Is it likely to happen again and if so what do I do to prevent a recurrence?

if it's only happened once then I wouldn't worry about it.

Originally posted by Cyclone
if it's only happened once then I wouldn't worry about it.

Well thats sorted that then. :hihi: :hihi:

In my experience of IT, if it has happened once it is more than likely to happen again.

This is borne out by my previous history of computers dating back to the dodgy dealer in 1997. If anyone feels they need to know the catastrophic string of disasters which destroyed my confidence in the IT industry and its ability to deliver products that are fit for for purpose please PM me with your email address and I will forward all of the facts in due course.

I am therefore not at all reassured that anything has been sorted out. In the meantime, I would feel far more reassured if someone would please explain what all of this stuff means.

Many thanks

Wendy,

You've experienced the Blue Screen of Death, a phenomenon well known to most Windows users! :)

It usually means that Windows found soemthing messy when booting up, but before it got to the 'user friendly' part of the program. Typically this can indicate corrupt files or a momentary hardware 'glitch'.

If it KEEPS happening, then I'd start getting concerned.

Joe

Originally posted by wendygs
In my experience of IT, if it has happened once it is more than likely to happen again.

This is borne out by my previous history of computers dating back to the dodgy dealer in 1997. If anyone feels they need to know the catastrophic string of disasters which destroyed my confidence in the IT industry and its ability to deliver products that are fit for for purpose please PM me with your email address and I will forward all of the facts in due course.

I am therefore not at all reassured that anything has been sorted out. In the meantime, I would feel far more reassured if someone would please explain what all of this stuff means.

Many thanks

It happens at random because of the dodgy nature (and shear size) of the codebase for windows.
Seriously, if it just happens once, don't get all worried about it.

If it starts happening regularly, then get worried.

I've had a similar problem recently, tracked it down to a dodgy version of ZA that conflicted with some of the latest patches...
Only seemed to happen on resume though, and particularly if I immediately started a game and put stress on the system.

OK, unless it recurs I'll put that on the back burner for the time being and thanks again for taking the time to reply more substantially.

If you are using XP it might be worth running sfc /scannow from the Run box Wendy. At least that will fix any corrupt Windows files :)

Originally posted by vidster
If you are using XP it might be worth running sfc /scannow from the Run box Wendy. At least that will fix any corrupt Windows files :) what do you run if using windows 98,as ive had similar to wendy 3 times this week,once its eventually booted it runs ok,its just the first boot that causes trouble,thanx,

Just to clarify any misunderstandings, this problem happened while I had a range of applications open. I dont know what happened to cause the problem because I was out of the room at the time of the incident and only discovered it on my return.

PS Hi depoix. Hope you have a great night this evening and that you had loads of fun on your birthday. Got to dash. Have a great weekend. Bi for now wendy:clap: :clap:

Originally posted by depoix
what do you run if using windows 98,as ive had similar to wendy 3 times this week,once its eventually booted it runs ok,its just the first boot that causes trouble,thanx,

I don't think sfc /scannow works with win 98 depoix. 98 is before my time but i found this while browsing:
The Windows 98 Registry Checker utility has two files: Scanreg.exe and Scanregw.exe. The first is used after starting the computer to an MS-DOS prompt, and the second is used after starting the computer into Windows. These utilities can be used to restore registry backups or to repair the registry.

By default, Windows 98 makes a backup of your registry every time you start your computer. It keeps one backup for each of the last five days the system was successfully started. If your system has a corrupted registry, you may be able to restore a backup that was made before the corruption occurred. Otherwise, you can use Scanreg.exe to attempt to repair the registry files.

It's worth a try :wink:

Originally posted by vidster
I don't think sfc /scannow works with win 98 depoix. 98 is before my time but i found this while browsing:


It's worth a try :wink: thanx mate,ran it and it says back up was created, maybe its just a glich but thanx for your time:D