asked on

Random reboots on XP Sp2

This just started a few days ago... ill be sitting working on something or my PC will be idle then bam BSoD system halted.

I reboot everything is fine till later. Ive ran virus scans.. all my hardware seems to check out fine. below are links to my minidump files. i cannot figure out what the deal is.

www.ddnhub.com/minidump

This is the error that windows shows after the reboot:

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000005, 0x00000002, 0x00000000, 0x804f8c19). A dump was saved in: C:\WINDOWS\Minidump\Mini042306-02.dmp.

If you need to know anything else about my system let me know. Everything is up to date software wise.

syedasimmeesaq

Well have you tried system recovery to an earlier date before the problem started? Sometime it helps and is very simple before you take some serious measures into consideration.
Thanks

venom96737

could you check the event viewer to see if it can tell what process is causing the mess.

asian_niceguy

did you install any programs before this happened? any new hardware?

try running:
start -> run -> "sfc /scannow"

also try reinstalling windows using the REPAIR option (this will keep your data, and just overwrite windows system core files) using your windows XP cd. Usually this takes an hour so only use this as a last resort

venom96737

the error code provided says 0x00000005 this is an Invalid process attach attempt. so find the process and theres your answer and you say it happens when it idls so my thought would be power management or hibernation mode is causeing the issue try disabling both of these features and see what happens.

remlab

ASKER

After it happend the first time... i formated the PC installed fresh windows.. all new upated drivers... no hardware has been added to this box it atleast a few months. it happends when at random times... idles or running any programs.

the only thing i see in the event viewer is

Error code 1000000a, parameter1 00000005, parameter2 00000002, parameter3 00000000, parameter4 804f8c19.

OR
The server {F3A614DC-ABE0-11D2-A441-00C04F795683} did not register with DCOM within the required timeout.

cpc2004

Probably it is caused by faulty memory or Norton AV. The Norton AV may be conflict with the device driver.

Suggestion
1. De-install Norton AV and Install AVG
2. Run memtest to stress test the ram.
3. Run 3DMark 2005 to test your video card

Debug report
Mini041606-01.dmp BugCheck 1000008E, {c0000005, 80521bfb, b9cfd5b0, 0}
Probably caused by : win32k.sys ( win32k!ReferenceW32Thread+11 ) <-- Faulty ram or video memory

Mini042106-01.dmp BugCheck 4E, {99, 0, 0, 0}
Probably caused by : SiWinAcc.sys ( SiWinAcc+1292 )

Mini042106-02.dmp BugCheck 4E, {99, 0, 0, 0}
Probably caused by : SiWinAcc.sys ( SiWinAcc+1292 )

Mini042106-03.dmp BugCheck 100000D1, {1, ff, 8, 1}
Probably caused by : SYMEVENT.SYS ( SYMEVENT+e767 )

Mini042106-04.dmp BugCheck 4E, {99, 0, 0, 0}
Probably caused by : SiWinAcc.sys ( SiWinAcc+3b4 ) <-- faulty ram

Mini042206-01.dmp BugCheck C2, {7, cd4, 857feed0, 859243d8}
Probably caused by : ntkrnlpa.exe ( nt!ExFreePoolWithTag+2a0 )

Mini042206-02.dmp BugCheck 1000000A, {0, 2, 1, 804f9982}
Probably caused by : SiWinAcc.sys ( SiWinAcc+325 )

Mini042206-03.dmp BugCheck 1000000A, {0, 2, 1, 8051e106}
Probably caused by : win32k.sys ( win32k!PALLOCMEM+2c )

Mini042306-01.dmp BugCheck 10000050, {e6ed62c8, 0, bf808a0c, 2}
Probably caused by : win32k.sys ( win32k!EXLATEOBJ::bSearchCache+3c ) <-- Faulty ram or video memory

Mini042306-02.dmp BugCheck 1000000A, {5, 2, 0, 804f8c19}
Probably caused by : SiWinAcc.sys ( SiWinAcc+325 )

It is unlikely it is the software error at SiWinAcc as I don't find similar hit at goggle,

ASKER CERTIFIED SOLUTION

samb39

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Mohammed Hamada