I need help

[serat]

I am trying to understand why I keep getting BLUE SCREEN errors in XP pro SP2 done. I just did a fresh install and got newest drivers for EVERYTHING.

I looked at the Advanced System Information - Error Log section and found a lot of error codes. My question is can anyone tell me if there is a way to understand these errors?? I looked under system information, hardware resources, I/O and found the range of the most reoccuring error of the hex numbers correspond to "motherboard resources" am I on the right track at all?

Here are my errors since fresh install, I fixed some issues with the display driver for ATI card, but one in particular happens a lot more (6 Times) then others: Error code 0000004e, parameter1 00000099, parameter2 00002402, parameter3 00000000, parameter4 00000000.
Tom

ASUS P4P800S-X
ATI 9600XT 256
512MB DDR400
WD 200G 7200/8

ALL of it:
Advanced System Information - Error Log

Please wait while information is being collected...
100% (collecting Error Log information)
Refresh screen

Error Log

Date - Time Source Description

Tuesday, March 29, 2005 DCOM The server {601AC3DC-786A-4EB0-BF40-EE352 1E70BFB} did not register with DCOM within the required timeout.

Tuesday, March 29, 2005 System Error Error code 000000c5, parameter1 00000000, parameter2 00000002, parameter3 00000001, parameter4 8053a29d.

Tuesday, March 29, 2005 System Error Error code 0000004e, parameter1 00000099, parameter2 00002402, parameter3 00000000, parameter4 00000000.

Tuesday, March 29, 2005 BROWSER The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{9956736E- AFE9-4397-9FDF-1BDCF915B508}. The backup browser is stopping.

Tuesday, March 29, 2005 System Error Error code 100000ea, parameter1 818f5678, parameter2 8193da78, parameter3 81f09258, parameter4 00000001.

Tuesday, March 29, 2005 System Error Error code 0000004e, parameter1 00000099, parameter2 00002402, parameter3 00000000, parameter4 00000000.

Tuesday, March 29, 2005 System Error Error code 100000ea, parameter1 818f5678, parameter2 8193da78, parameter3 81f09258, parameter4 00000001.

Tuesday, March 29, 2005 System Error Error code 0000004e, parameter1 00000099, parameter2 00002402, parameter3 00000000, parameter4 00000000.

Tuesday, March 29, 2005 System Error Error code 100000ea, parameter1 818f5678, parameter2 8193da78, parameter3 81f09258, parameter4 00000001.

Tuesday, March 29, 2005 System Error Error code 0000004e, parameter1 00000099, parameter2 00002402, parameter3 00000000, parameter4 00000000.

Tuesday, March 29, 2005 System Error Error code 100000ea, parameter1 818f5678, parameter2 8193da78, parameter3 81f09258, parameter4 00000001.

Tuesday, March 29, 2005 Windows Update Agent Installation Failure: Windows failed to install the following update with error 0x80246007: Windows XP Service Pack 2.

Thursday, March 31, 2005 DCOM The server {520CCA63-51A5-11D3-9144-00104 BA11C5E} did not register with DCOM within the required timeout.

Thursday, March 31, 2005 DCOM DCOM got error "%1058" attempting to start the service SENS with arguments "" in order to run the server: {D3938AB0-5B9D-11D1-8 DD2-00AA004ABD5E}

Thursday, March 31, 2005 DCOM DCOM got error "%1058" attempting to start the service SENS with arguments "" in order to run the server: {D3938AB0-5B9D-11D1-8 DD2-00AA004ABD5E}

Thursday, March 31, 2005 System Error Error code 1000008e, parameter1 c0000005, parameter2 bf871918, parameter3 f365bc64, parameter4 00000000.

Thursday, March 31, 2005 System Error Error code 0000004e, parameter1 00000099, parameter2 000109c8, parameter3 00000000, parameter4 00000000.

Thursday, March 31, 2005 System Error Error code 0000004e, parameter1 00000099, parameter2 0000c315, parameter3 00000000, parameter4 00000000.

Thursday, March 31, 2005 Windows Update Agent Installation Failure: Windows failed to install the following update with error 0x80240017: Windows XP Service Pack 2.

Thursday, March 31, 2005 System Error Error code 1000008e, parameter1 c0000005, parameter2 80552ae5, parameter3 f7fe2638, parameter4 00000000.

W32Time The time service has detected that the system time needs to be changed by +42681599 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com (ntp.m|0x1|192.168.123.138:123 ->207.46.130.100:123) is working properly.

System Error Error code 0000000a, parameter1 070ffffd, parameter2 0000001c, parameter3 00000000, parameter4 804e1a6b.

Thursday, March 31, 2005 Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.

Tuesday, March 29, 2005 Applicatio n Error Fault bucket 01996285.

Thursday, March 31, 2005 Applicatio n Error Faulting application windowsxp product key viewer.exe, version 1.0.0.0, faulting module windowsxp product key viewer.exe, version 1.0.0.0, fault address 0x00001138.

Thursday, March 31, 2005 DrWatson The application, D:\XP_XTRAS\XP keygen\WindowsXP Product Key Viewer.exe, generated an application error The error occurred on 03/31/2005 @ 01:27:20.655 The exception generated was c0000005 at address 00401138 (WindowsXP Product Key Viewer)

Thursday, March 31, 2005 Applicatio n Error Faulting application mmc.exe, version 5.1.2600.2180, faulting module comctl32.dll, version 6.0.2900.2180, fault address 0x00028edd.

Thursday, March 31, 2005 Applicatio n Error Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.2180, fault address 0x0001295d.

Thursday, March 31, 2005 MsiInstall er Product: Symantec AntiVirus -- Internal Error 2203. C:\WINDOWS\Installer\25a3a1.ms i, -2147287008

 

[Assimilator]

Dunno if this will help.

Try reinstalling XP or XP with Service Pack 1. If you don't get STOP errors anymore, something in XP Service Pack 2 is causing this problem. If you still get STOP errors, then it's almost certainly some piece of hardware that's about to die on you (most likely your mobo).

Also, I see that the last line in the log file relates to anti-virus protection. It's always a good idea to disable anti-virus software when installing critical OS updates, as it can interfere.

Finally, downloading the newset drivers isn't always a good idea, as they can sometimes have more bugs than older, more stable drivers. Try to use older drivers that are certified compatible with XP SP2, and see if that works.

 

[serat]

Thank you! those are some good suggestions!
I too have a feeling it may be the motherboard, I'm going to do everything from scratch again see what happens.

I'm still curious though, does anyone know how to interpret those numbers, I mean to me they are hex register addresses or something, but I wish I knew where to look to try and match up those errors to a device or program or whatever.
Tom

 

[INSTG8R]

From what I see from the first there is something wrong with your Networking(I see obvious errors in your time settings,Networking is time/date dependant),I also see issues with your Product Key which may be hindering any updates at all.Also as Assimilator said never do any serious updating(installing) with AntiVirus on as some legitimate code is looked on as malicious by AV as it(XP) is changing itself and AV is trying to prevent(with best intentions Im sure LOL)

 

[serat]

Thanks again guys. INSTG8R the date issue was actually intentional, I was installing some pirated software that needed the date swap...

Looks like it was the RAM, thx for suggesting hardware failure Assimilator. I did Memtest and found over 300 first time then on another PC 20 or so. It may have been installed incorrectly would that cause more dunno? What memtest is good to use? Should there be absolutely ZERO errors or a "few" is OK?
Tom

 

[C&C Freak 2K]

There needs to be absolutely zero errors (or every error needs to be automatically corrected), as any errors would cause data corruption.

 

[serat]

Thanks C&C, I got the new RAM and everything is OK now