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.
remlabAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

syedasimmeesaqCommented:
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
venom96737Commented:
could you check the event viewer to see if it can tell what process is causing the mess.
asian_niceguyCommented:
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
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

venom96737Commented:
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.
remlabAuthor Commented:
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.
cpc2004Commented:
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,
samb39Commented:
This guy had similar problems and after a lot of work concluded that it was bad RAM.

http://www.techspot.com/vb/all/windows/t-38871-Bucheck-Codes--Random-Reboots--Help-Analysing-please.html

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mohammed HamadaSenior IT ConsultantCommented:
Download memtest and run to check if it's faulty RAM..
http://www.memtest86.com/
Don't forget to use a bootable floppy disc..
remlabAuthor Commented:
i downloaded it.. ran the test and the ram failed.... which really sucks... newer ram Super Talent CL2 1gig: 2 x 512

they lifetime warrenty so i guess its not that bad.


Thanx guys
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.