A few minidump files.Hardware or software?

[martin10522]

i used whocrashed and 1 of it was caused by hardware..is it true??

 

[usasma]

Lot's of different errors. That, most often, will point to a hardware issue - but let's see what the dump files say....

Running all 21 now....

FYI - I haven't worked with XP dump files in quite a long while. I don't expect there to be any differences, but I'm just not up to speed on XP anymore.

 

[usasma]

I would start with updating the drivers for your video card and for your network card. Those are the most common errors in the dump files.

Then I'd update the drivers in the list below - they are mostly from 2001 and that's just too durned old for reliable functioning IMO.

If the BSOD's continue after that, then locate another video card and network card to test with. Test one at a time to see if either fix the issues.

After that, if the issues still occur - please post back for more things to try.

Here's a listing of older drivers that also should be updated:

dxgthk.sys   Fri Aug 17 16:53:12 2001
admjoy.sys   Wed Mar 20 20:48:14 2002
audstub.sys  Fri Aug 17 16:59:40 2001
Beep.SYS     Fri Aug 17 16:47:33 2001
BOOTVID.dll  Fri Aug 17 16:49:09 2001
Dxapi.sys    Fri Aug 17 16:53:19 2001
dxgthk.sys   Fri Aug 17 16:53:12 2001
Fs_Rec.SYS   Fri Aug 17 16:49:37 2001
fsvga.sys    Fri Aug 17 16:57:21 2001
ftdisk.sys   Fri Aug 17 16:52:41 2001
HDAudBus.sys Thu May 26 11:46:29 2005
kdcom.dll    Fri Aug 17 16:49:10 2001
mnmdd.SYS    Fri Aug 17 16:57:28 2001
mouhid.sys   Fri Aug 17 16:47:57 2001
ParVdm.SYS   Fri Aug 17 16:49:49 2001
ptilink.sys  Fri Aug 17 16:49:53 2001
rasacd.sys   Fri Aug 17 16:55:39 2001
raspti.sys   Fri Aug 17 16:55:32 2001
RDPCDD.sys   Fri Aug 17 16:46:56 2001
USBD.SYS     Fri Aug 17 17:02:58 2001
WMILIB.SYS   Fri Aug 17 17:07:23 2001
WudfPf.sys   Thu Sep 28 21:55:43 2006

Here's a summary of the BSOD's:

Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Sat Nov 14 20:27:38.187 2009 (GMT-5)
System Uptime: 0 days 0:00:20.171
BugCheck 6, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeUnstackDetachProcess+118 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  tintsetp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Sat Nov 14 23:36:15.125 2009 (GMT-5)
System Uptime: 0 days 3:06:42.115
BugCheck 100000BE, {f79a0000, 13f89121, b32deca4, a}
Probably caused by : win32k.sys ( win32k!EnterCrit+14 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  msnmsgr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Sun Nov 15 06:06:38.468 2009 (GMT-5)
System Uptime: 0 days 2:45:25.445
BugCheck 1000000A, {10, 2, 1, 804ea960}
Probably caused by : memory_corruption ( nt!MiInsertPageInList+1e4 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Mon Nov 16 09:41:50.875 2009 (GMT-5)
System Uptime: 0 days 0:15:44.472
BugCheck 1000000A, {a880, 2, 1, 80702a79}
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : aswMon2.SYS ( aswMon2+68ac )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  GTAIV.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Mon Nov 16 10:18:27.046 2009 (GMT-5)
System Uptime: 0 days 0:21:45.037
BugCheck 1000000A, {54, 1c, 1, 804e2630}
Probably caused by : ntkrnlmp.exe ( nt!KiUnlinkThread+0 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  GTAIV.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Thu Nov 19 07:02:56.328 2009 (GMT-5)
System Uptime: 0 days 1:42:32.314
BugCheck 1000000A, {1de48a36, 1c, 0, 804e78c7}
Probably caused by : win32k.sys ( win32k!GreReleaseSemaphore+a )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  GOnline.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp2_gdr.090804-1412
Debug session time: Fri Nov 20 01:21:10.046 2009 (GMT-5)
System Uptime: 0 days 0:17:40.021
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : HTTP.sys ( HTTP!UlpThreadPoolWorker+f9 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Fri Nov 20 05:34:29.046 2009 (GMT-5)
System Uptime: 0 days 1:52:27.645
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
BugCheck 1000008E, {c0000005, bd20cf83, b22a7b08, 0}
Probably caused by : nv4_disp.dll ( nv4_disp+1faf83 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  GOnline.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Fri Nov 20 06:59:19.625 2009 (GMT-5)
System Uptime: 0 days 1:24:24.624
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
BugCheck 1000007E, {c0000005, bd120110, b2513c5c, b2513958}
Probably caused by : nv4_disp.dll ( nv4_disp+10e110 )
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
PROCESS_NAME:  war3.exe
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Fri Nov 20 08:12:22.046 2009 (GMT-5)
System Uptime: 0 days 1:01:05.649
BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+d0 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Fri Nov 20 21:08:28.843 2009 (GMT-5)
System Uptime: 0 days 1:09:34.454
BugCheck 1000000A, {78b8a2fc, 2, 0, 804e8eb4}
Probably caused by : memory_corruption ( nt!MiRemovePageByColor+19 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Fri Nov 20 22:21:02.515 2009 (GMT-5)
System Uptime: 0 days 1:12:08.130
BugCheck 100000D1, {be70, 2, 0, b4aa4212}
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
Probably caused by : portcls.sys ( portcls!CPortPinWaveCyclic::GetPosition+38 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  war3.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Sat Nov 21 00:21:23.468 2009 (GMT-5)
System Uptime: 0 days 0:23:53.458
BugCheck 1000000A, {912815ff, 2, 1, 80702a8e}
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
Probably caused by : memory_corruption
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  war3.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Sat Nov 21 02:41:06.031 2009 (GMT-5)
System Uptime: 0 days 1:40:02.011
BugCheck 100000D1, {a692, 1d, 0, a692}
Probably caused by : ntkrnlmp.exe ( nt!KiIpiServiceRoutine+5e )
PROCESS_NAME:  war3.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Sat Nov 21 05:56:11.984 2009 (GMT-5)
System Uptime: 0 days 3:14:39.592
BugCheck 1000000A, {912815ff, 2, 1, 80702a8e}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  war3.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Sat Nov 21 21:46:13.531 2009 (GMT-5)
System Uptime: 0 days 1:38:39.525
BugCheck 1000000A, {4c004100, 1c, 0, 804eeacf}
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*** WARNING: Unable to verify timestamp for cpuz132_x32.sys
*** ERROR: Module load completed but symbols could not be loaded for cpuz132_x32.sys
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*** WARNING: Unable to verify timestamp for l1e51x86.sys
*** ERROR: Module load completed but symbols could not be loaded for l1e51x86.sys
*** WARNING: Unable to verify timestamp for ATMFD.DLL
*** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for drmk.sys - 
Probably caused by : nv4_disp.dll ( nv4_disp+165272 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  war3.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Sun Nov 22 04:00:13.578 2009 (GMT-5)
System Uptime: 0 days 1:50:04.585
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
BugCheck 1000007E, {c0000005, bd120110, 8ca3dc5c, 8ca3d958}
Probably caused by : nv4_disp.dll ( nv4_disp+10e110 )
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
PROCESS_NAME:  war3.exe
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Mon Nov 23 08:42:57.906 2009 (GMT-5)
System Uptime: 0 days 0:00:30.916
BugCheck 100000D1, {d5165aa9, 7, 1, b6a46a54}
Probably caused by : hardware ( USBPORT!USBPORT_RootHub_PowerAndChirpAllCcPorts+68 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  Idle
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Mon Nov 23 19:27:14.906 2009 (GMT-5)
System Uptime: 0 days 10:15:23.514
BugCheck 1000000A, {912815ff, 2, 1, 80702a8e}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  Thunder.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Tue Nov 24 08:31:22.234 2009 (GMT-5)
System Uptime: 0 days 1:52:17.836
BugCheck 24, {1902fe, b29b731c, b29b7018, 8055270b}
Probably caused by : Ntfs.sys ( Ntfs!ExAllocateFromPagedLookasideList+27 )
PROCESS_NAME:  java.exe
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp_sp3_gdr.090804-1435
Debug session time: Tue Nov 24 11:18:59.787 2009 (GMT-5)
System Uptime: 0 days 2:47:45.086
BugCheck 100000D1, {10003c4, 2, 0, b450c63f}
Probably caused by : TDI.SYS ( TDI!CTEpEventHandler+32 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  System

 

[martin10522]

I would start with updating the drivers for your video card and for your network card. Those are the most common errors in the dump files.

Then I'd update the drivers in the list below - they are mostly from 2001 and that's just too durned old for reliable functioning IMO.

If the BSOD's continue after that, then locate another video card and network card to test with. Test one at a time to see if either fix the issues.

After that, if the issues still occur - please post back for more things to try.

Here's a listing of older drivers that also should be updated:

i've tried updating video card driver and network card driver for motherboard,still i get BSOD.
And those 2001 driver should be xp's system file/driver as i think this xp is from 2001,now im trying another windows and see if i still get BSOD or not.
If i still get it i guess its hardware problem?

edit:does the network things cause by MC DTC?because in my error log there is always a cross with MC DTC.
Also will it cause by disconnect?because i always get disconnect..