Error caused by a device driver messages - minidumps attached.

Status
Not open for further replies.
Hello all, 1st post so be gentle...

I have been having the seeming usual spurious crashed/ restarts in XP home for some time now and of course the MS report is always the same, Error Caused By A Device Driver etc.

I have attached the last 5 minidumps in the hope that someone will be able to identify the source of this recurring problem.

Thanks,

Axxe
 

Attachments

  • Mini102905-01.zip
    21.2 KB · Views: 5
Hi axeeman,

The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram


Your debug report
Mini102905-01.dmp BugCheck 1000008E, {c0000005, bf80427a, 9d492730, 0}
Mini102905-01.dmp Probably caused by : win32k.sys ( win32k!_GetDCEx+26c )

Mini103005-01.dmp BugCheck 100000D1, {c, 2, 0, 9d1175a0}
Mini103005-01.dmp Probably caused by : SYMTDI.SYS ( SYMTDI+1c4f7 )

Mini103005-02.dmp BugCheck 1000007E, {c0000005, 805a533b, f78d2798, f78d2494}
Mini103005-02.dmp Probably caused by : ntoskrnl.exe ( nt!PipProcessDevNodeTree+f7 )

Mini103105-01.dmp BugCheck 1000007E, {c0000005, 0, f78dec44, f78de940}
Mini103105-01.dmp Probably caused by : ntoskrnl.exe ( nt!ObpRemoveObjectRoutine+c3 )

Mini110205-01.dmp BugCheck 1000000A, {63286328, 2, 0, 804dc25d}
Mini110205-01.dmp Probably caused by : GoBack2K.sys ( GoBack2K+2f1c )
 
Thank you very much for that analysis.

At a best guess I was looking at either my graphics card which is a Radeon 9800XT or possibly one of the 3 512k memory sticks that is in the machine.

The reson that I suspected the AGP is that I have seen a lot of problems on forums from PC users and the 9800 is a common link in their systems. However in light of what has happened recently and your most helpful analysis, I have started my self to lean towards the memory as the root cause of the recurring problem.

My final question is what brand of memory do you recommend to (hopefully) avoid these problems...

Many thanks,

Axxe
 
Hi axeeman,

New Suggestion

1. Check the bios setting about memory timing and make sure that it is on
For example : DIMM1 and DIMM2 do not have the same timing.
DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
2. Make sure that your PSU have adequate power to drive all the hardware including USB devices
3. Run chkdsk /r at command prompt
4. Run 3DMark 2005 to test your video card
5. Upgrade BIOS to latest version

Attach the latest minidumps here
 
Thanks, I'll look at that although I don't remember seeing anything in the bios re memory timing.

The board is a Jetway V600DAP. There have never been any bios revisions released.

My PSU is 550w with protected rails to prevent any voltage fluctuations getting through - something which happened once before long ago and caused me some real troubles...

I will run the chkdisk (whatever that does)

3D mark 2005 I have never heard of but I gather it is a test routine?

Still wondering about replacing the memory though. Give me the necessary push to U/G to 3 Gb form 1.5...

Axxe
 
Status
Not open for further replies.
Back