Error message

  • Thread starter Thread starter Ron
  • Start date Start date
R

Ron

Have recently built new custom computer MSI Mainboard,
Celeron 2.4g Processor 256 mb Ram XP Home sp1 and loaded
all device drivers and software and did windows updates.
Loaded PC Cillen and updated. All worked like a dream
Customer took it home and loaded their Canon printer and
scanner. Computer returned next day as it would power on
and before windows would normally be on screen just went
blank screen. I got it going again by removing HDD
(Nothing else wanted to play the game) checking it over
as a slave to another xp based system , put the HDD back
and booted ok but to a error report , do you want to send
it to Microsoft..did send it and also checked the error
out. This is the manifest of the error..

Server=watson.microsoft.com
UI LCID=1033
Flags=123152
Brand=WINDOWS
TitleName=Microsoft Windows
DigPidRegPath=HKLM\Software\Microsoft\Windows
NT\CurrentVersion\DigitalProductId
RegSubPath=Microsoft\PCHealth\ErrorReporting\DW
ErrorText=A log of this error has been created.
HeaderText=The system has recovered from a serious error.
Stage2URL=
Stage2URL=/dw/bluetwo.asp?
BCCode=23&BCP1=000E00E0&BCP2=F99A77D8&BCP3=F99A74D8&BCP4=F
25A89BC&OSVer=5_1_2600&SP=1_0&Product=768_1
DataFiles=C:\WINDOWS\Minidump\Mini082704-
01.dmp|C:\DOCUME~1\Owner\LOCALS~1\Temp\WER1.tmp.dir00
\sysdata.xml
ErrorSubPath=blue


Microsoft reported that the error may be a device driver.
As I have loaded a few of these computers with the same
components I wasn't accepting that it would be a computer
hardware fault.
I went through event viewer thoroughly and found the
error only started happening after the Canon printer
(BJC210) was installed.
I un installed it and reinstalled using the XP Home
drivers as reported by Canon support.
I was then able to reboot the computer without any
further error message on that day.
Rebooted the computer today and low and behold the
blastered error message is back. So my effort of blaming
the Canon driver is wrong now I am mysterfied as to what
the cause is. Have looked in Event Manager and see a log
of the errors and when they occurred reorts error in
category 102 and event 1003 would presume this would
relate to a device driver.

Just to make the matter even more ridiculous is that I
have just finished building a P4 3GIG Prescott on Asus
P4P800 Board 512Ram Windows xp Home all updates done
Norton System works 2003 did 12 hours of loading software
and updates with testing and just installed the 12x
DVDRAM Drive and loaded its software rebooted and got the
same type of error message as above slightly different
numbers and or alpha but same message from microsoft that
it is a device driver causing the error.

No errors are reported in either computer in Device
Manager. This computer also reoprts category 102 and
event 1003 in Event viewer
My gut feel is that is something to do with Windows update

Wonder if anyone else out there has a similar problem and
how best to tackle it

Regards

Ron
 
Solved the problem myself on both instances.
I checked out the error reporting details in My
Computer / Properties / Advanced /Error reporting and
clicked on choose programs. I found an entry in bottom
section of "do not report errors for these programs" and
had one listed with a tick on it but the line was blank.
I just removed the blank line and presco no further
problems. I have no idea what this was associted with but
obviously it got in there somehow as other xp machines I
have do not have any such errors.
Just strange and conicidental that it happened on 2 new
machines that I was building
Regards
 
Your system is blue screening with the following:

0x00000023: FAT_FILE_SYSTEM
{0x000E00E0, 0xF99A77D8, 0xF99A74D8, 0xF25A89BC}

(In event log terms that's BCCode=23, BCP1=000E00E0, BCP2=F99A77D8, BCP3
=F99A74D8, BCP4=F25A89BC)

This is a disk corruption problem. You say it keeps happening when you
insert a HDD. Either those firewall/antivirus software is incompatible,
or the HDD is no good (run a thorough scandisk, with heavy sector
checking). This may be also caused by unseated hardware.

Make sure you check:

How to Troubleshoot a "Stop 0x00000023 FAT_FILE_SYSTEM" Message:
http://support.microsoft.com/?kbid=290182

And for general troubleshooting stuff:
http://www.aumha.org/win5/kbestop.htm
(esp. the general section. It also has details

You state you get event log errors of different numbers: is the BCCode=
23 in all of them, or does BCCode have a different number?




--
------------------------------------------------------------------------
oshah
Control Panel -> System -> Advanced -> Error Reporting -> Choose
Programs
-> Do not report errors for these programs:

Acrobat.exe
waol.exe
 
Most interesting indeed! Those entries exist under the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PCHealth\ErrorReporting
\ExclusionList

You can delete that program under this reg key. But before you do, can
you tell us what you have under that registry key? If you can't see the
characters in use, try copying into notepad and posting that text file.

PS
If you haven't guessed, the stuff in my sig represents the programs I
have in my list, and isn't a subliminal solution! ... Or Is It?


--
------------------------------------------------------------------------
oshah
Control Panel -> System -> Advanced -> Error Reporting -> Choose
Programs
-> Do not report errors for these programs:

Acrobat.exe
waol.exe

------------------------------------------------------------------------
 
Back
Top