Link to home
Start Free TrialLog in
Avatar of saminco
saminco

asked on

XP BSOD / Reboots No device conflicts

Might anyone shed some light on the below error message?  This system reboots at any given time as well as BSOD.  There is no device conflicts nor any new hardware installed....A mini dump is created, but I have yet to find a .dmp viewer....

Much Thanks


Event Type:       Error

Event Source:    System Error

Event Category: (102)

Event ID:           1003

Date:                8/31/2004

Time:                9:44:34 AM

User:                N/A

Computer:        

Description:

Error code 0000009c, parameter1 00000000, parameter2 805366f0, parameter3 a2000000, parameter4 84010400.

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 53 79 73 74 65 6d 20 45   System E

0008: 72 72 6f 72 20 20 45 72   rror  Er

0010: 72 6f 72 20 63 6f 64 65   ror code

0018: 20 30 30 30 30 30 30 39    0000009

0020: 63 20 20 50 61 72 61 6d   c  Param

0028: 65 74 65 72 73 20 30 30   eters 00

0030: 30 30 30 30 30 30 2c 20   000000,

0038: 38 30 35 33 36 36 66 30   805366f0

0040: 2c 20 61 32 30 30 30 30   , a20000

0048: 30 30 2c 20 38 34 30 31   00, 8401

0050: 30 34 30 30               0400
Avatar of saminco
saminco

ASKER

Everything looks to point to the Video card.  Currently nVidia MX 4000 with current driver.  Maybe bad ram?

Avatar of saminco

ASKER

Just ran the MS Memory check tool and everything was successful.  Might there be a problem with the MX 4000 chipset on XP?  As his card ran perfect on win2k.
Can you give any more information on your system setup?  Is the video on-board?  Why do you say that "everything looks to point to the video card"?  If that is the case, can you remove (or disable) the current video and try another?  Are you using the drivers that came with XP?  If so, I would *highly* recommend using the drivers from NVidia.  http://www.nvidia.com/object/winxp_2k_61.77

Write back and let me know....
Avatar of saminco

ASKER

P4 2.6
40gig
512 DDR ram
Win XP Pro
nvidia MX 4000 128meg AGP video

I have tried other (chaintech and someother local bought card) "nVidia" chip set cards, and the same thing happens.  I am tempted to go out and buy an ATI card ($100.00).  61.77 is the driver I have on his machine.  
And you've not found any rhyme or reason to this behavior?  It's not during a game or something?  You just boot up, wait awhile, and the system will reboot itself?  I'm still not sure why you're leaning toward the "video card" in this.  Can you give any insight there?

In my experience, random reboot issues typically have to do with heat.  You'll have the system off for awhile, boot up, everything looks fine, and then the box just resets itself.  Very strange.  I had a server, though, where I didn't have the fan/heatsink on the CPU exactly right and it exhibited the same behavior.  No strange error messages or codes.  It might be fine for an hour, or just 10 minutes, but it would ALWAYS reboot!  It's not rebooted itself once since figuring out that I hadn't seated the heatsink properly.

Do you see the same behavior if you boot into "SAFE MODE"?
Avatar of saminco

ASKER

Well, the onyl reason I think it's the video card is that this card worked on his win2k pro system.  And I read a post somewhere about the MX 4000 chipset and XP issue.  Maybe someone else was also just reaching for "the stars" so to speak.  This is a workstation (no games; besides the XP ones).  the system can stay up for 2 hours or 2 days.  No ryme or reason to blus screens or random reboots.  The MB is a Asus P4S800.

Thanks
ASKER CERTIFIED SOLUTION
Avatar of chumplet
chumplet
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of saminco

ASKER

Well, I'll try the new chipset for the MB.  And i'll grab an ATi card tonight, as i'll eave the system on over night.  If it's crashed in the morning....ATi time. I think the new chipset driver "might" /me crosses fingers work.  Since his current driver is from 2001 and not signed.  We'll see here shortly.

Thanks for the prompt replies and support :)
Avatar of saminco

ASKER

I updated the chipset MB driver and left on over night and still logged in the same session....no BSOD.  We'll see.  Opted to stick with the nVidia card.