minidump - thread stuck in device driver M (100000ea)

  • Thread starter Thread starter ricardo.l
  • Start date Start date
R

ricardo.l

I am going crazy to troubleshoot this problem: after googling it and also
reading throughout this community I got several hints but still working on it.
I was doing nothing special when BSOD appeared. Since then I was not able
anymore to boot the system in anyway. Not even safe mode.
It just goes blank right after logo screen and stuck there.

If (unlikely) due to a new disk added on a sata channel, days ago, for data
storage, which is still healthy and with data on it, then it could be
boot.ini problem...but why did It work finely for days?
I remember that last program installation was the asus smart doc utility to
manage Gpu fan control (which I found noisy and wanted to monitor) but it
never worked, just got the error kinda "missing resource.." when trying start
that application.

Can you provide help from the piece of debugger log attached below?
I can only add that never had disk problems till now (nor BSOD), although
when I ran chkdsk /f on primary partition it found several file record
segments unreadable between 12380 and 12402, it recovered lost files, saying
it made corrections to file system. And that an unspecified error occurred.

Thank you for providing suggestions...
ricardo
-----
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [d:\windows\minidump\mini111807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Sun Nov 18 03:10:35.015 2007 (GMT+1)
System Uptime: 0 days 0:04:31.593
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Loading Kernel Symbols
...................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {870d0020, 89d0eed8, bacdfcb4, 1}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for
watchdog.sys
*** WARNING: Unable to verify timestamp for a347scsi.sys
*** ERROR: Module load completed but symbols could not be loaded for
a347scsi.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************


Probably caused by : ntoskrnl.exe

Followup: MachineOwner
---------

*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of
KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the
time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will
have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 870d0020, Pointer to a stuck thread object. Do .thread then kb on it
to find
the hung location.
Arg2: 89d0eed8, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bacdfcb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see
notes).

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************



MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9c

FAULTING_THREAD: 870d0020

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

LAST_CONTROL_TRANSFER: from 8053e2e3 to 80540c9f

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
b342b418 8053e2e3 badb0d00 00000001 000b0217 nt+0x69c9f
b342b494 00000000 badb0d00 00000000 00000240 nt+0x672e3


STACK_COMMAND: .thread 0xffffffff870d0020 ; kb

FOLLOWUP_IP:
nt+69c9f
80540c9f 8b2c24 mov ebp,dword ptr [esp]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+69c9f

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

GetPointerFromAddress: unable to read from 80557db4
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_ETHREAD ***
*** ***
*************************************************************************
89e403c8: Unable to get thread contents
start end module name
804d7000 806ce400 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Wed Feb 28 09:38:52 2007 (45E53F9C)
CheckSum: 001F9460
ImageSize: 001F7400
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
806cf000 806ef380 hal (deferred)
Image path: hal.dll
Image name: hal.dll
Timestamp: Wed Aug 04 07:59:05 2004 (41107B29)
CheckSum: 0002CFD1
ImageSize: 00020380
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
.....
long list of deferred modules, and unloaded as well
 
You Haven't Resolved the Symbols

1) Install microsoft debugging tools from
http://msdn.microsoft.com/msdnmag/issues/05/07/Debugging/
2) Create folder c:\symbols
3) Download and install the
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
4) Locate your latest memory.dmp file- C:\WINNT\Minidump\Mini011005-01.dmp
or whatever
4) Open a CMD prompt and cd\program files\debugging tools for windows\
5) Type the following stuff:

Code:
c:\program files\debugging tools>kd -z C:\WINNT\Minidump\Mini011005-01.dmp
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q

You now have a debuglog.txt in c:\, open it in notepad and post the content
to this thread

ricardo.l said:
I am going crazy to troubleshoot this problem: after googling it and also
reading throughout this community I got several hints but still working on it.
I was doing nothing special when BSOD appeared. Since then I was not able
anymore to boot the system in anyway. Not even safe mode.
It just goes blank right after logo screen and stuck there.

If (unlikely) due to a new disk added on a sata channel, days ago, for data
storage, which is still healthy and with data on it, then it could be
boot.ini problem...but why did It work finely for days?
I remember that last program installation was the asus smart doc utility to
manage Gpu fan control (which I found noisy and wanted to monitor) but it
never worked, just got the error kinda "missing resource.." when trying start
that application.

Can you provide help from the piece of debugger log attached below?
I can only add that never had disk problems till now (nor BSOD), although
when I ran chkdsk /f on primary partition it found several file record
segments unreadable between 12380 and 12402, it recovered lost files, saying
it made corrections to file system. And that an unspecified error occurred.

Thank you for providing suggestions...
ricardo
-----
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [d:\windows\minidump\mini111807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Sun Nov 18 03:10:35.015 2007 (GMT+1)
System Uptime: 0 days 0:04:31.593
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Loading Kernel Symbols
.................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {870d0020, 89d0eed8, bacdfcb4, 1}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for
watchdog.sys
*** WARNING: Unable to verify timestamp for a347scsi.sys
*** ERROR: Module load completed but symbols could not be loaded for
a347scsi.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************


Probably caused by : ntoskrnl.exe

Followup: MachineOwner
---------

*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of
KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the
time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will
have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 870d0020, Pointer to a stuck thread object. Do .thread then kb on it
to find
the hung location.
Arg2: 89d0eed8, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bacdfcb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see
notes).

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************



MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9c

FAULTING_THREAD: 870d0020

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

LAST_CONTROL_TRANSFER: from 8053e2e3 to 80540c9f

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
b342b418 8053e2e3 badb0d00 00000001 000b0217 nt+0x69c9f
b342b494 00000000 badb0d00 00000000 00000240 nt+0x672e3


STACK_COMMAND: .thread 0xffffffff870d0020 ; kb

FOLLOWUP_IP:
nt+69c9f
80540c9f 8b2c24 mov ebp,dword ptr [esp]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+69c9f

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

GetPointerFromAddress: unable to read from 80557db4
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_ETHREAD ***
*** ***
*************************************************************************
89e403c8: Unable to get thread contents
start end module name
804d7000 806ce400 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Wed Feb 28 09:38:52 2007 (45E53F9C)
CheckSum: 001F9460
ImageSize: 001F7400
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
806cf000 806ef380 hal (deferred)
Image path: hal.dll
Image name: hal.dll
Timestamp: Wed Aug 04 07:59:05 2004 (41107B29)
CheckSum: 0002CFD1
ImageSize: 00020380
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
....
long list of deferred modules, and unloaded as well
Click to expand...
 
Devil_Himself said:
You Haven't Resolved the Symbols .....
You now have a debuglog.txt in c:\, open it in notepad and post the content
to this thread
Click to expand...
I was amazed when I saw those commands work...I'd realized I was missing
something but didn't know how to go ahead with the analysis. It seems we are
on the right way, now the point becomes how to fix it... :)
There it goes:

* Bugcheck Analysis
*

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of
KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the
time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will
have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 870d0020, Pointer to a stuck thread object. Do .thread then kb on it
to find
the hung location.
Arg2: 89d0eed8, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bacdfcb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see
notes).

Debugging Details:
------------------
FAULTING_THREAD: 870d0020
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: csrss.exe
LAST_CONTROL_TRANSFER: from 806d1ca4 to 80540c9f

STACK_TEXT:
b342b3fc 806d1ca4 0000003d 89d71c44 8054075f nt!KiDispatchInterrupt+0x7f
b342b408 8054075f 000b0001 00000173 b342b494 hal!HalEndSystemInterrupt+0x54
b342b408 8053e2e3 000b0001 00000173 b342b494 nt!KiChainedDispatch+0x2f
b342b494 00000000 badb0d00 00000000 00000240 nt!KiTrap06+0x3bf


STACK_COMMAND: .thread 0xffffffff870d0020 ; kb

FOLLOWUP_IP:
nt!KiDispatchInterrupt+7f
80540c9f 8b2c24 mov ebp,dword ptr [esp]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiDispatchInterrupt+7f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9c

FAILURE_BUCKET_ID: 0xEA_nt!KiDispatchInterrupt+7f

BUCKET_ID: 0xEA_nt!KiDispatchInterrupt+7f

Followup: MachineOwner
---------

eax=ffdff13c ebx=89d0eed8 ecx=00000000 edx=00000000 esi=bac513a4 edi=88217ac8
eip=80540c9f esp=b342b3f4 ebp=b342b418 iopl=0 vif nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00080286
nt!KiDispatchInterrupt+0x7f:
80540c9f 8b2c24 mov ebp,dword ptr [esp]
ss:0010:b342b3f4=b342b418
ChildEBP RetAddr Args to Child
b342b3fc 806d1ca4 0000003d 89d71c44 8054075f nt!KiDispatchInterrupt+0x7f
(FPO: [Uses EBP] [0,0,3])
b342b408 8054075f 000b0001 00000173 b342b494 hal!HalEndSystemInterrupt+0x54
(FPO: [2,2,0])
b342b408 8053e2e3 000b0001 00000173 b342b494 nt!KiChainedDispatch+0x2f (FPO:
[0,2] TrapFrame @ b342b418)
b342b494 00000000 badb0d00 00000000 00000240 nt!KiTrap06+0x3bf
start end module name
804d7000 806ce400 nt ntkrnlpa.exe Wed Feb 28 09:38:52 2007 (45E53F9C)
806cf000 806ef380 hal halaacpi.dll Wed Aug 04 07:59:05 2004 (41107B29)
b0af2000 b0b1c180 kmixer kmixer.sys Wed Jun 14 10:47:45 2006 (448FCD31)
b2c7e000 b32fbf20 nv4_mini nv4_mini.sys Fri Jun 29 10:16:41 2007 (4684BFE9)
b7e3d000 b7e3fd00 vstor2 vstor2.sys Fri Mar 23 18:02:01 2007 (46040809)
b7e61000 b7e72520 PfModNT PfModNT.sys Thu Jun 03 06:09:59 2004 (40BEA497)
b7f8b000 b7fdc480 srv srv.sys Mon Aug 14 12:34:39 2006 (44E051BF)
b805d000 b8060000 EIO EIO.sys Wed Jun 14 07:44:28 2006 (448FA23C)
b806d000 b806fb80 secdrv secdrv.sys Thu Nov 14 12:52:30 2002 (3DD38E7E)
b807d000 b80a5600 atksgt atksgt.sys Sun Jan 29 11:29:17 2006 (43DC98FD)
b8146000 b81c08c0 amon amon.sys Fri May 11 08:22:58 2007 (46440BC2)
b81c1000 b82a1300 vmx86 vmx86.sys Wed Aug 22 03:15:37 2007 (46CB8E39)
b82a2000 b82ce400 mrxdav mrxdav.sys Wed Aug 04 08:00:49 2004 (41107B91)
b8415000 b8429400 wdmaud wdmaud.sys Wed Jun 14 11:00:44 2006 (448FD03C)
b856a000 b8578d80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004 (41107F1A)
b894a000 b895e400 dump_nvraid dump_nvraid.sys Tue Apr 25 02:52:34 2006
(444D72D2)
b895f000 b898b900 SaiH0461 SaiH0461.sys Tue Aug 08 19:25:06 2006 (44D8C8F2)
b898c000 b89b2000 ctsfm2k ctsfm2k.sys Thu Feb 17 16:18:09 2005 (4214B5B1)
b89b2000 b89e2000 ctoss2k ctoss2k.sys Thu Feb 17 16:18:11 2005 (4214B5B3)
b89e2000 b8b7fb80 sbusb sbusb.sys Fri Jun 10 03:39:17 2005 (42A8EF45)
b8ba8000 b8c16a00 mrxsmb mrxsmb.sys Fri May 05 11:41:42 2006 (445B1DD6)
b8c17000 b8c41a00 rdbss rdbss.sys Fri May 05 11:47:55 2006 (445B1F4B)
b8c42000 b8c63d00 afd afd.sys Wed Aug 04 08:14:13 2004 (41107EB5)
b8c64000 b8c8bc00 netbt netbt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
b8c8c000 b8cacf00 ipnat ipnat.sys Thu Sep 30 00:28:36 2004 (415B3714)
b8cad000 b8ce0000 pctfw2 pctfw2.sys Mon Sep 17 19:22:53 2007 (46EEB7ED)
b8ce0000 b8d37d80 tcpip tcpip.sys Thu Apr 20 13:51:47 2006 (444775D3)
b8d38000 b8d4a400 ipsec ipsec.sys Wed Aug 04 08:14:27 2004 (41107EC3)
b8d6b000 b8d7e780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 08:07:04 2004 (41107D08)
b8d7f000 b8ddef00 Senfilt Senfilt.sys Mon Mar 13 17:40:28 2006 (4415A07C)
b8ddf000 b8df5f00 AEAudio AEAudio.sys Mon Aug 07 15:57:27 2006 (44D746C7)
b8df6000 b8e19980 portcls portcls.sys Wed Aug 04 08:15:47 2004 (41107F13)
b8e1a000 b8e66000 ADIHdAud ADIHdAud.sys Tue Jan 16 15:09:04 2007 (45ACDC80)
b8e76000 b8e78f80 mouhid mouhid.sys Fri Aug 17 22:47:57 2001 (3B7D82FD)
b8e86000 b8e89780 VMkbd VMkbd.sys Wed Aug 22 04:24:56 2007 (46CB9E78)
b8ff3000 b8ff5f00 ws2ifsl ws2ifsl.sys Fri Aug 17 22:55:58 2001 (3B7D84DE)
b920f000 b921d100 usbhub usbhub.sys Wed Aug 04 08:08:40 2004 (41107D68)
b923f000 b9247d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 08:08:18 2004 (41107D52)
b9292000 b9294280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
b92a2000 b92a4900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
b92a6000 b92a9a00 kbdhid kbdhid.sys Wed Aug 04 07:58:33 2004 (41107B09)
b9f5e000 b9f69000 hcmon hcmon.sys Wed Aug 22 03:55:50 2007 (46CB97A6)
ba096000 ba0c9200 update update.sys Wed Aug 04 07:58:32 2004 (41107B08)
ba0ca000 ba0ec000 pctfw pctfw.sys Mon Sep 17 19:22:25 2007 (46EEB7D1)
ba0ec000 ba11c100 rdpdr rdpdr.sys Wed Aug 04 08:01:10 2004 (41107BA6)
ba11d000 ba12de00 psched psched.sys Wed Aug 04 08:04:16 2004 (41107C60)
ba14a000 ba14d600 SaiMini SaiMini.sys Mon Aug 14 12:52:44 2006 (44E055FC)
ba1b6000 ba1bf480 NDProxy NDProxy.SYS Fri Aug 17 22:55:30 2001 (3B7D84C2)
ba1f6000 ba20c680 ndiswan ndiswan.sys Wed Aug 04 08:14:30 2004 (41107EC6)
ba20d000 ba220980 parport parport.sys Wed Aug 04 07:59:04 2004 (41107B28)
ba221000 ba231280 serial serial.sys Wed Aug 04 08:15:51 2004 (41107F17)
ba232000 ba285000 NVSNPU NVSNPU.SYS Wed Mar 22 22:23:16 2006 (4421C044)
ba285000 ba389f00 NVNRM NVNRM.SYS Wed Mar 22 22:23:39 2006 (4421C05B)
ba38a000 ba3af000 HDAudBus HDAudBus.sys Thu Oct 28 00:21:32 2004 (41801F6C)
ba3af000 ba3d1680 ks ks.sys Wed Aug 04 08:15:20 2004 (41107EF8)
ba3d2000 ba3f4e80 USBPORT USBPORT.SYS Wed Aug 04 08:08:34 2004 (41107D62)
ba3f9000 ba3fb300 PdiPorts PdiPorts.sys Fri Nov 17 01:31:13 2006 (455D02D1)
ba411000 ba413580 ndistapi ndistapi.sys Fri Aug 17 22:55:29 2001 (3B7D84C1)
ba415000 ba417a00 Video3D32 Video3D32.sys Fri Sep 29 04:06:25 2006
(451C7FA1)
ba419000 ba41bb00 atkkbnt atkkbnt.sys Tue Oct 31 08:55:36 2006 (45470178)
ba41d000 ba420c80 serenum serenum.sys Wed Aug 04 07:59:06 2004 (41107B2A)
ba445000 ba447580 hidusb hidusb.sys Fri Aug 17 23:02:16 2001 (3B7D8658)
ba465000 ba467a00 VMNET VMNET.SYS Fri Mar 16 11:05:31 2007 (45FA6BEB)
ba469000 ba46b680 vmnetadapter vmnetadapter.sys Fri Mar 16 11:06:08 2007
(45FA6C10)
ba471000 ba474c80 mssmbios mssmbios.sys Wed Aug 04 08:07:47 2004 (41107D33)
ba505000 ba51f580 Mup Mup.sys Wed Aug 04 08:15:20 2004 (41107EF8)
ba520000 ba53a260 snapman snapman.sys Fri Oct 06 15:44:30 2006 (45265DBE)
ba53b000 ba599ec0 timntr timntr.sys Mon Sep 25 15:44:11 2006 (4517DD2B)
ba59a000 ba5c6a80 NDIS NDIS.sys Wed Aug 04 08:14:27 2004 (41107EC3)
ba5c7000 ba653400 Ntfs Ntfs.sys Fri Feb 09 12:10:31 2007 (45CC56A7)
ba654000 ba66a780 KSecDD KSecDD.sys Wed Aug 04 07:59:45 2004 (41107B51)
ba66b000 ba67cf00 sr sr.sys Wed Aug 04 08:06:22 2004 (41107CDE)
ba67d000 ba69c780 fltMgr fltMgr.sys Mon Aug 21 11:14:57 2006 (44E97991)
ba69d000 ba6b5980 nvatabus nvatabus.sys Tue Apr 25 02:52:25 2006 (444D72C9)
ba6b6000 ba6cd480 atapi atapi.sys Wed Aug 04 07:59:41 2004 (41107B4D)
ba6ce000 ba6e5800 SCSIPORT SCSIPORT.SYS Wed Aug 04 07:59:39 2004 (41107B4B)
ba6e6000 ba6fa400 nvraid nvraid.sys Tue Apr 25 02:52:34 2006 (444D72D2)
ba6fb000 ba720a80 dmio dmio.sys Wed Aug 04 08:07:13 2004 (41107D11)
ba721000 ba73fb80 ftdisk ftdisk.sys Fri Aug 17 22:52:41 2001 (3B7D8419)
ba740000 ba750c80 pci pci.sys Wed Aug 04 08:07:45 2004 (41107D31)
ba751000 ba77f000 ACPI ACPI.sys Wed Aug 04 08:07:35 2004 (41107D27)
ba77f000 ba7a6380 a347bus a347bus.sys Fri Apr 30 08:37:01 2004 (4091F40D)
ba8a8000 ba8b0d00 isapnp isapnp.sys Fri Aug 17 22:58:01 2001 (3B7D8559)
ba8b8000 ba8c6e80 ohci1394 ohci1394.sys Wed Aug 04 08:10:05 2004 (41107DBD)
ba8c8000 ba8d5000 1394BUS 1394BUS.SYS Wed Aug 04 08:10:03 2004 (41107DBB)
ba8d8000 ba8e2500 MountMgr MountMgr.sys Wed Aug 04 07:58:29 2004 (41107B05)
ba8e8000 ba8f4200 CLASSPNP CLASSPNP.SYS Wed Aug 04 08:14:26 2004 (41107EC2)
ba8f8000 ba905080 VolSnap VolSnap.sys Wed Aug 04 08:00:14 2004 (41107B6E)
ba908000 ba917e00 jraid jraid.sys Sat Sep 29 07:30:52 2007 (46FDE30C)
ba918000 ba920e00 disk disk.sys Wed Aug 04 07:59:53 2004 (41107B59)
ba928000 ba930b60 PxHelp20 PxHelp20.sys Wed Aug 09 19:27:31 2006 (44DA1B03)
ba978000 ba980900 Fips Fips.SYS Sat Aug 18 03:31:49 2001 (3B7DC585)
ba9b8000 ba9c7380 rspndr rspndr.sys Wed Nov 08 09:51:53 2006 (45519AA9)
ba9c8000 ba9d6b80 drmk drmk.sys Wed Aug 04 08:07:54 2004 (41107D3A)
ba9d8000 ba9e4e00 NVENETFD NVENETFD.sys Wed Mar 22 22:23:58 2006 (4421C06E)
ba9f8000 baa00700 wanarp wanarp.sys Wed Aug 04 08:04:57 2004 (41107C89)
baa08000 baa17900 Cdfs Cdfs.SYS Wed Aug 04 08:14:09 2004 (41107EB1)
baa18000 baa20700 netbios netbios.sys Wed Aug 04 08:03:19 2004 (41107C27)
baa28000 baa37000 pctmp pctmp.sys Wed Jul 25 01:27:52 2007 (46A68AF8)
baa38000 baa44200 dump_CLASSPNP dump_CLASSPNP.SYS Wed Aug 04 08:14:26 2004
(41107EC2)
baa58000 baa61a00 processr processr.sys Wed Aug 04 07:59:14 2004 (41107B32)
baa68000 baa72380 imapi imapi.sys Wed Aug 04 08:00:12 2004 (41107B6C)
baa78000 baa84180 cdrom cdrom.sys Wed Aug 04 07:59:52 2004 (41107B58)
baa88000 baa96380 redbook redbook.sys Wed Aug 04 07:59:34 2004 (41107B46)
baa98000 baaa1000 nvnetbus nvnetbus.sys Wed Mar 22 22:24:01 2006 (4421C071)
baaa8000 baab5180 i8042prt i8042prt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
baab8000 baac4880 rasl2tp rasl2tp.sys Wed Aug 04 08:14:21 2004 (41107EBD)
baac8000 baad2200 raspppoe raspppoe.sys Wed Aug 04 08:05:06 2004 (41107C92)
baad8000 baae1f00 termdd termdd.sys Wed Aug 04 07:58:52 2004 (41107B1C)
baae8000 baaf0980 SaiBus SaiBus.sys Thu Nov 03 11:52:37 2005 (4369EBF5)
bab08000 bab10900 msgpc msgpc.sys Wed Aug 04 08:04:11 2004 (41107C5B)
bab18000 bab23d00 raspptp raspptp.sys Wed Aug 04 08:14:26 2004 (41107EC2)
bab28000 bab2e200 PCIIDEX PCIIDEX.SYS Wed Aug 04 07:59:40 2004 (41107B4C)
bab30000 bab34900 PartMgr PartMgr.sys Sat Aug 18 03:32:23 2001 (3B7DC5A7)
bab38000 bab3df00 VClone VClone.sys Sat Apr 22 21:59:21 2006 (444A8B19)
bab68000 bab6e800 usbehci usbehci.sys Wed Aug 04 08:08:34 2004 (41107D62)
bab70000 bab71000 fdc fdc.sys unavailable (00000000)
bab78000 bab7dc00 mouclass mouclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
bab80000 bab84880 TDI TDI.SYS Wed Aug 04 08:07:47 2004 (41107D33)
bab88000 bab8c580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
bab90000 bab94080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
bab98000 bab9e200 kbdclass kbdclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
babb0000 babb7260 SCDEmu SCDEmu.SYS Mon Apr 09 14:27:07 2007 (461A311B)
babc0000 babc8000 pctssipc pctssipc.sys Tue Aug 14 04:44:41 2007 (46C11719)
babc8000 babcf880 Npfs Npfs.SYS Wed Aug 04 08:00:38 2004 (41107B86)
bac08000 bac0e180 HIDPARSE HIDPARSE.SYS Wed Aug 04 08:08:15 2004 (41107D4F)
bac10000 bac14780 vmnetuserif vmnetuserif.sys Wed Aug 22 03:57:47 2007
(46CB981B)
bac18000 bac1c680 lirsgt lirsgt.sys Sun Jan 29 12:06:18 2006 (43DCA1AA)
bac30000 bac35480 vmnetbridge vmnetbridge.sys Fri Mar 16 11:06:36 2007
(45FA6C2C)
bac50000 bac54500 watchdog watchdog.sys Wed Aug 04 08:07:32 2004 (41107D24)
bac58000 bac5d000 flpydisk flpydisk.sys Wed Aug 04 07:59:24 2004 (41107B3C)
bac60000 bac67b80 usbccgp usbccgp.sys Wed Aug 04 08:08:45 2004 (41107D6D)
bac68000 bac6d200 vga vga.sys Wed Aug 04 08:07:06 2004 (41107D0A)
bac70000 bac74a80 Msfs Msfs.SYS Wed Aug 04 08:00:37 2004 (41107B85)
bac88000 bac8f000 VMparport VMparport.sys Wed Aug 22 03:54:30 2007
(46CB9756)
bac90000 bac97e40 tifsfilt tifsfilt.sys Mon Sep 25 15:48:28 2006 (4517DE2C)
bacb0000 bacb4280 usbohci usbohci.sys Wed Aug 04 08:08:34 2004 (41107D62)
bacb8000 bacbb000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345)
bada8000 bada9b80 kdcom kdcom.dll Fri Aug 17 22:49:10 2001 (3B7D8346)
badaa000 badab100 WMILIB WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
badac000 badad700 dmload dmload.sys Fri Aug 17 22:58:15 2001 (3B7D8567)
badae000 badafb00 Jgogo Jgogo.sys Tue Feb 07 12:52:58 2006 (43E88A1A)
badb0000 badb1480 a347scsi a347scsi.sys Fri Apr 30 08:32:58 2004 (4091F31A)
badd4000 badd5200 ElbyDelay ElbyDelay.sys Tue Apr 12 10:41:20 2005
(425B89B0)
badd6000 badd7420 ASACPI ASACPI.sys Fri Aug 13 04:52:52 2004 (411C2D04)
badda000 baddb100 swenum swenum.sys Wed Aug 04 07:58:41 2004 (41107B11)
bae30000 bae31f80 ElbyCDIO ElbyCDIO.sys Sat Apr 22 03:44:39 2006 (44498A87)
bae36000 bae37f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
bae38000 bae39080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
bae3a000 bae3b280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682)
bae3c000 bae3d080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
bae3e000 bae3f080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
bae4a000 bae4bde0 nod32drv nod32drv.sys Fri May 11 08:23:05 2007 (46440BC9)
bae5c000 bae5db00 ParVdm ParVdm.SYS Fri Aug 17 22:49:49 2001 (3B7D836D)
bae70000 bae70d00 pciide pciide.sys Fri Aug 17 22:51:49 2001 (3B7D83E5)
baef1000 baef1c00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
baef6000 baef6d00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)
baf5e000 baf5eb80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
baf7f000 baf7fa80 PQNTDrv PQNTDrv.SYS Tue Sep 17 01:14:30 2002 (3D8665D6)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 14:47:34 2007 (45F013F6)
bf9c3000 bf9d4580 dxg dxg.sys Wed Aug 04 08:00:51 2004 (41107B93)
bff70000 bff72480 framebuf framebuf.dll Fri Aug 20 00:38:20 2004 (41252BDC)

Unloaded modules:
b3734000 b375f000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b83c7000 b83f2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
baf15000 baf16000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b907a000 b9087000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b83f2000 b8415000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba9a8000 ba9b6000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bae26000 bae28000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
baa08000 baa16000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bac60000 bac65000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
b9296000 b9299000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt
 
One Minidump is Insufficient to Determine the Root Cause ... .. if you can
Zip 5-6 Minidumps and upload them to any free web hosting and give me the
link .. i can study them and tell you the result

ricardo.l said:
Devil_Himself said:
You Haven't Resolved the Symbols ....
You now have a debuglog.txt in c:\, open it in notepad and post the content
to this thread
Click to expand...
I was amazed when I saw those commands work...I'd realized I was missing
something but didn't know how to go ahead with the analysis. It seems we are
on the right way, now the point becomes how to fix it... :)
There it goes:

* Bugcheck Analysis
*

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of
KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the
time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will
have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 870d0020, Pointer to a stuck thread object. Do .thread then kb on it
to find
the hung location.
Arg2: 89d0eed8, Pointer to a DEFERRED_WATCHDOG object.
Arg3: bacdfcb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see
notes).

Debugging Details:
------------------
FAULTING_THREAD: 870d0020
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: csrss.exe
LAST_CONTROL_TRANSFER: from 806d1ca4 to 80540c9f

STACK_TEXT:
b342b3fc 806d1ca4 0000003d 89d71c44 8054075f nt!KiDispatchInterrupt+0x7f
b342b408 8054075f 000b0001 00000173 b342b494 hal!HalEndSystemInterrupt+0x54
b342b408 8053e2e3 000b0001 00000173 b342b494 nt!KiChainedDispatch+0x2f
b342b494 00000000 badb0d00 00000000 00000240 nt!KiTrap06+0x3bf


STACK_COMMAND: .thread 0xffffffff870d0020 ; kb

FOLLOWUP_IP:
nt!KiDispatchInterrupt+7f
80540c9f 8b2c24 mov ebp,dword ptr [esp]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiDispatchInterrupt+7f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9c

FAILURE_BUCKET_ID: 0xEA_nt!KiDispatchInterrupt+7f

BUCKET_ID: 0xEA_nt!KiDispatchInterrupt+7f

Followup: MachineOwner
---------

eax=ffdff13c ebx=89d0eed8 ecx=00000000 edx=00000000 esi=bac513a4 edi=88217ac8
eip=80540c9f esp=b342b3f4 ebp=b342b418 iopl=0 vif nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00080286
nt!KiDispatchInterrupt+0x7f:
80540c9f 8b2c24 mov ebp,dword ptr [esp]
ss:0010:b342b3f4=b342b418
ChildEBP RetAddr Args to Child
b342b3fc 806d1ca4 0000003d 89d71c44 8054075f nt!KiDispatchInterrupt+0x7f
(FPO: [Uses EBP] [0,0,3])
b342b408 8054075f 000b0001 00000173 b342b494 hal!HalEndSystemInterrupt+0x54
(FPO: [2,2,0])
b342b408 8053e2e3 000b0001 00000173 b342b494 nt!KiChainedDispatch+0x2f (FPO:
[0,2] TrapFrame @ b342b418)
b342b494 00000000 badb0d00 00000000 00000240 nt!KiTrap06+0x3bf
start end module name
804d7000 806ce400 nt ntkrnlpa.exe Wed Feb 28 09:38:52 2007 (45E53F9C)
806cf000 806ef380 hal halaacpi.dll Wed Aug 04 07:59:05 2004 (41107B29)
b0af2000 b0b1c180 kmixer kmixer.sys Wed Jun 14 10:47:45 2006 (448FCD31)
b2c7e000 b32fbf20 nv4_mini nv4_mini.sys Fri Jun 29 10:16:41 2007 (4684BFE9)
b7e3d000 b7e3fd00 vstor2 vstor2.sys Fri Mar 23 18:02:01 2007 (46040809)
b7e61000 b7e72520 PfModNT PfModNT.sys Thu Jun 03 06:09:59 2004 (40BEA497)
b7f8b000 b7fdc480 srv srv.sys Mon Aug 14 12:34:39 2006 (44E051BF)
b805d000 b8060000 EIO EIO.sys Wed Jun 14 07:44:28 2006 (448FA23C)
b806d000 b806fb80 secdrv secdrv.sys Thu Nov 14 12:52:30 2002 (3DD38E7E)
b807d000 b80a5600 atksgt atksgt.sys Sun Jan 29 11:29:17 2006 (43DC98FD)
b8146000 b81c08c0 amon amon.sys Fri May 11 08:22:58 2007 (46440BC2)
b81c1000 b82a1300 vmx86 vmx86.sys Wed Aug 22 03:15:37 2007 (46CB8E39)
b82a2000 b82ce400 mrxdav mrxdav.sys Wed Aug 04 08:00:49 2004 (41107B91)
b8415000 b8429400 wdmaud wdmaud.sys Wed Jun 14 11:00:44 2006 (448FD03C)
b856a000 b8578d80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004 (41107F1A)
b894a000 b895e400 dump_nvraid dump_nvraid.sys Tue Apr 25 02:52:34 2006
(444D72D2)
b895f000 b898b900 SaiH0461 SaiH0461.sys Tue Aug 08 19:25:06 2006 (44D8C8F2)
b898c000 b89b2000 ctsfm2k ctsfm2k.sys Thu Feb 17 16:18:09 2005 (4214B5B1)
b89b2000 b89e2000 ctoss2k ctoss2k.sys Thu Feb 17 16:18:11 2005 (4214B5B3)
b89e2000 b8b7fb80 sbusb sbusb.sys Fri Jun 10 03:39:17 2005 (42A8EF45)
b8ba8000 b8c16a00 mrxsmb mrxsmb.sys Fri May 05 11:41:42 2006 (445B1DD6)
b8c17000 b8c41a00 rdbss rdbss.sys Fri May 05 11:47:55 2006 (445B1F4B)
b8c42000 b8c63d00 afd afd.sys Wed Aug 04 08:14:13 2004 (41107EB5)
b8c64000 b8c8bc00 netbt netbt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
b8c8c000 b8cacf00 ipnat ipnat.sys Thu Sep 30 00:28:36 2004 (415B3714)
b8cad000 b8ce0000 pctfw2 pctfw2.sys Mon Sep 17 19:22:53 2007 (46EEB7ED)
b8ce0000 b8d37d80 tcpip tcpip.sys Thu Apr 20 13:51:47 2006 (444775D3)
b8d38000 b8d4a400 ipsec ipsec.sys Wed Aug 04 08:14:27 2004 (41107EC3)
b8d6b000 b8d7e780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 08:07:04 2004 (41107D08)
b8d7f000 b8ddef00 Senfilt Senfilt.sys Mon Mar 13 17:40:28 2006 (4415A07C)
b8ddf000 b8df5f00 AEAudio AEAudio.sys Mon Aug 07 15:57:27 2006 (44D746C7)
b8df6000 b8e19980 portcls portcls.sys Wed Aug 04 08:15:47 2004 (41107F13)
b8e1a000 b8e66000 ADIHdAud ADIHdAud.sys Tue Jan 16 15:09:04 2007 (45ACDC80)
b8e76000 b8e78f80 mouhid mouhid.sys Fri Aug 17 22:47:57 2001 (3B7D82FD)
b8e86000 b8e89780 VMkbd VMkbd.sys Wed Aug 22 04:24:56 2007 (46CB9E78)
b8ff3000 b8ff5f00 ws2ifsl ws2ifsl.sys Fri Aug 17 22:55:58 2001 (3B7D84DE)
b920f000 b921d100 usbhub usbhub.sys Wed Aug 04 08:08:40 2004 (41107D68)
b923f000 b9247d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 08:08:18 2004 (41107D52)
b9292000 b9294280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
b92a2000 b92a4900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
b92a6000 b92a9a00 kbdhid kbdhid.sys Wed Aug 04 07:58:33 2004 (41107B09)
b9f5e000 b9f69000 hcmon hcmon.sys Wed Aug 22 03:55:50 2007 (46CB97A6)
ba096000 ba0c9200 update update.sys Wed Aug 04 07:58:32 2004 (41107B08)
ba0ca000 ba0ec000 pctfw pctfw.sys Mon Sep 17 19:22:25 2007 (46EEB7D1)
ba0ec000 ba11c100 rdpdr rdpdr.sys Wed Aug 04 08:01:10 2004 (41107BA6)
ba11d000 ba12de00 psched psched.sys Wed Aug 04 08:04:16 2004 (41107C60)
ba14a000 ba14d600 SaiMini SaiMini.sys Mon Aug 14 12:52:44 2006 (44E055FC)
ba1b6000 ba1bf480 NDProxy NDProxy.SYS Fri Aug 17 22:55:30 2001 (3B7D84C2)
ba1f6000 ba20c680 ndiswan ndiswan.sys Wed Aug 04 08:14:30 2004 (41107EC6)
ba20d000 ba220980 parport parport.sys Wed Aug 04 07:59:04 2004 (41107B28)
ba221000 ba231280 serial serial.sys Wed Aug 04 08:15:51 2004 (41107F17)
ba232000 ba285000 NVSNPU NVSNPU.SYS Wed Mar 22 22:23:16 2006 (4421C044)
ba285000 ba389f00 NVNRM NVNRM.SYS Wed Mar 22 22:23:39 2006 (4421C05B)
ba38a000 ba3af000 HDAudBus HDAudBus.sys Thu Oct 28 00:21:32 2004 (41801F6C)
ba3af000 ba3d1680 ks ks.sys Wed Aug 04 08:15:20 2004 (41107EF8)
ba3d2000 ba3f4e80 USBPORT USBPORT.SYS Wed Aug 04 08:08:34 2004 (41107D62)
ba3f9000 ba3fb300 PdiPorts PdiPorts.sys Fri Nov 17 01:31:13 2006 (455D02D1)
ba411000 ba413580 ndistapi ndistapi.sys Fri Aug 17 22:55:29 2001 (3B7D84C1)
ba415000 ba417a00 Video3D32 Video3D32.sys Fri Sep 29 04:06:25 2006
(451C7FA1)
ba419000 ba41bb00 atkkbnt atkkbnt.sys Tue Oct 31 08:55:36 2006 (45470178)
ba41d000 ba420c80 serenum serenum.sys Wed Aug 04 07:59:06 2004 (41107B2A)
ba445000 ba447580 hidusb hidusb.sys Fri Aug 17 23:02:16 2001 (3B7D8658)
ba465000 ba467a00 VMNET VMNET.SYS Fri Mar 16 11:05:31 2007 (45FA6BEB)
ba469000 ba46b680 vmnetadapter vmnetadapter.sys Fri Mar 16 11:06:08 2007
(45FA6C10)
ba471000 ba474c80 mssmbios mssmbios.sys Wed Aug 04 08:07:47 2004 (41107D33)
ba505000 ba51f580 Mup Mup.sys Wed Aug 04 08:15:20 2004 (41107EF8)
ba520000 ba53a260 snapman snapman.sys Fri Oct 06 15:44:30 2006 (45265DBE)
ba53b000 ba599ec0 timntr timntr.sys Mon Sep 25 15:44:11 2006 (4517DD2B)
ba59a000 ba5c6a80 NDIS NDIS.sys Wed Aug 04 08:14:27 2004 (41107EC3)
ba5c7000 ba653400 Ntfs Ntfs.sys Fri Feb 09 12:10:31 2007 (45CC56A7)
ba654000 ba66a780 KSecDD KSecDD.sys Wed Aug 04 07:59:45 2004 (41107B51)
ba66b000 ba67cf00 sr sr.sys Wed Aug 04 08:06:22 2004 (41107CDE)
ba67d000 ba69c780 fltMgr fltMgr.sys Mon Aug 21 11:14:57 2006 (44E97991)
ba69d000 ba6b5980 nvatabus nvatabus.sys Tue Apr 25 02:52:25 2006 (444D72C9)
ba6b6000 ba6cd480 atapi atapi.sys Wed Aug 04 07:59:41 2004 (41107B4D)
ba6ce000 ba6e5800 SCSIPORT SCSIPORT.SYS Wed Aug 04 07:59:39 2004 (41107B4B)
ba6e6000 ba6fa400 nvraid nvraid.sys Tue Apr 25 02:52:34 2006 (444D72D2)
ba6fb000 ba720a80 dmio dmio.sys Wed Aug 04 08:07:13 2004 (41107D11)
ba721000 ba73fb80 ftdisk ftdisk.sys Fri Aug 17 22:52:41 2001 (3B7D8419)
ba740000 ba750c80 pci pci.sys Wed Aug 04 08:07:45 2004 (41107D31)
ba751000 ba77f000 ACPI ACPI.sys Wed Aug 04 08:07:35 2004 (41107D27)
ba77f000 ba7a6380 a347bus a347bus.sys Fri Apr 30 08:37:01 2004 (4091F40D)
ba8a8000 ba8b0d00 isapnp isapnp.sys Fri Aug 17 22:58:01 2001 (3B7D8559)
ba8b8000 ba8c6e80 ohci1394 ohci1394.sys Wed Aug 04 08:10:05 2004 (41107DBD)
ba8c8000 ba8d5000 1394BUS 1394BUS.SYS Wed Aug 04 08:10:03 2004 (41107DBB)
ba8d8000 ba8e2500 MountMgr MountMgr.sys Wed Aug 04 07:58:29 2004 (41107B05)
ba8e8000 ba8f4200 CLASSPNP CLASSPNP.SYS Wed Aug 04 08:14:26 2004 (41107EC2)
ba8f8000 ba905080 VolSnap VolSnap.sys Wed Aug 04 08:00:14 2004 (41107B6E)
ba908000 ba917e00 jraid jraid.sys Sat Sep 29 07:30:52 2007 (46FDE30C)
ba918000 ba920e00 disk disk.sys Wed Aug 04 07:59:53 2004 (41107B59)
ba928000 ba930b60 PxHelp20 PxHelp20.sys Wed Aug 09 19:27:31 2006 (44DA1B03)
ba978000 ba980900 Fips Fips.SYS Sat Aug 18 03:31:49 2001 (3B7DC585)
ba9b8000 ba9c7380 rspndr rspndr.sys Wed Nov 08 09:51:53 2006 (45519AA9)
ba9c8000 ba9d6b80 drmk drmk.sys Wed Aug 04 08:07:54 2004 (41107D3A)
ba9d8000 ba9e4e00 NVENETFD NVENETFD.sys Wed Mar 22 22:23:58 2006 (4421C06E)
ba9f8000 baa00700 wanarp wanarp.sys Wed Aug 04 08:04:57 2004 (41107C89)
baa08000 baa17900 Cdfs Cdfs.SYS Wed Aug 04 08:14:09 2004 (41107EB1)
baa18000 baa20700 netbios netbios.sys Wed Aug 04 08:03:19 2004 (41107C27)
baa28000 baa37000 pctmp pctmp.sys Wed Jul 25 01:27:52 2007 (46A68AF8)
baa38000 baa44200 dump_CLASSPNP dump_CLASSPNP.SYS Wed Aug 04 08:14:26 2004
(41107EC2)
baa58000 baa61a00 processr processr.sys Wed Aug 04 07:59:14 2004 (41107B32)
baa68000 baa72380 imapi imapi.sys Wed Aug 04 08:00:12 2004 (41107B6C)
baa78000 baa84180 cdrom cdrom.sys Wed Aug 04 07:59:52 2004 (41107B58)
baa88000 baa96380 redbook redbook.sys Wed Aug 04 07:59:34 2004 (41107B46)
baa98000 baaa1000 nvnetbus nvnetbus.sys Wed Mar 22 22:24:01 2006 (4421C071)
baaa8000 baab5180 i8042prt i8042prt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
baab8000 baac4880 rasl2tp rasl2tp.sys Wed Aug 04 08:14:21 2004 (41107EBD)
baac8000 baad2200 raspppoe raspppoe.sys Wed Aug 04 08:05:06 2004 (41107C92)
baad8000 baae1f00 termdd termdd.sys Wed Aug 04 07:58:52 2004 (41107B1C)
baae8000 baaf0980 SaiBus SaiBus.sys Thu Nov 03 11:52:37 2005 (4369EBF5)
bab08000 bab10900 msgpc msgpc.sys Wed Aug 04 08:04:11 2004 (41107C5B)
bab18000 bab23d00 raspptp raspptp.sys Wed Aug 04 08:14:26 2004 (41107EC2)
bab28000 bab2e200 PCIIDEX PCIIDEX.SYS Wed Aug 04 07:59:40 2004 (41107B4C)
bab30000 bab34900 PartMgr PartMgr.sys Sat Aug 18 03:32:23 2001 (3B7DC5A7)
bab38000 bab3df00 VClone VClone.sys Sat Apr 22 21:59:21 2006 (444A8B19)
bab68000 bab6e800 usbehci usbehci.sys Wed Aug 04 08:08:34 2004 (41107D62)
bab70000 bab71000 fdc fdc.sys unavailable (00000000)
bab78000 bab7dc00 mouclass mouclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
bab80000 bab84880 TDI TDI.SYS Wed Aug 04 08:07:47 2004 (41107D33)
bab88000 bab8c580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
bab90000 bab94080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
bab98000 bab9e200 kbdclass kbdclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
babb0000 babb7260 SCDEmu SCDEmu.SYS Mon Apr 09 14:27:07 2007 (461A311B)
babc0000 babc8000 pctssipc pctssipc.sys Tue Aug 14 04:44:41 2007 (46C11719)
babc8000 babcf880 Npfs Npfs.SYS Wed Aug 04 08:00:38 2004 (41107B86)
bac08000 bac0e180 HIDPARSE HIDPARSE.SYS Wed Aug 04 08:08:15 2004 (41107D4F)
bac10000 bac14780 vmnetuserif vmnetuserif.sys Wed Aug 22 03:57:47 2007
(46CB981B)
bac18000 bac1c680 lirsgt lirsgt.sys Sun Jan 29 12:06:18 2006 (43DCA1AA)
bac30000 bac35480 vmnetbridge vmnetbridge.sys Fri Mar 16 11:06:36 2007
(45FA6C2C)
bac50000 bac54500 watchdog watchdog.sys Wed Aug 04 08:07:32 2004 (41107D24)
bac58000 bac5d000 flpydisk flpydisk.sys Wed Aug 04 07:59:24 2004 (41107B3C)
bac60000 bac67b80 usbccgp usbccgp.sys Wed Aug 04 08:08:45 2004 (41107D6D)
bac68000 bac6d200 vga vga.sys Wed Aug 04 08:07:06 2004 (41107D0A)
bac70000 bac74a80 Msfs Msfs.SYS Wed Aug 04 08:00:37 2004 (41107B85)
bac88000 bac8f000 VMparport VMparport.sys Wed Aug 22 03:54:30 2007
(46CB9756)
bac90000 bac97e40 tifsfilt tifsfilt.sys Mon Sep 25 15:48:28 2006 (4517DE2C)
bacb0000 bacb4280 usbohci usbohci.sys Wed Aug 04 08:08:34 2004 (41107D62)
bacb8000 bacbb000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345)
bada8000 bada9b80 kdcom kdcom.dll Fri Aug 17 22:49:10 2001 (3B7D8346)
badaa000 badab100 WMILIB WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
badac000 badad700 dmload dmload.sys Fri Aug 17 22:58:15 2001 (3B7D8567)
badae000 badafb00 Jgogo Jgogo.sys Tue Feb 07 12:52:58 2006 (43E88A1A)
badb0000 badb1480 a347scsi a347scsi.sys Fri Apr 30 08:32:58 2004 (4091F31A)
badd4000 badd5200 ElbyDelay ElbyDelay.sys Tue Apr 12 10:41:20 2005
(425B89B0)
badd6000 badd7420 ASACPI ASACPI.sys Fri Aug 13 04:52:52 2004 (411C2D04)
badda000 baddb100 swenum swenum.sys Wed Aug 04 07:58:41 2004 (41107B11)
bae30000 bae31f80 ElbyCDIO ElbyCDIO.sys Sat Apr 22 03:44:39 2006 (44498A87)
bae36000 bae37f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
bae38000 bae39080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
bae3a000 bae3b280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682)
bae3c000 bae3d080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
bae3e000 bae3f080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
bae4a000 bae4bde0 nod32drv nod32drv.sys Fri May 11 08:23:05 2007 (46440BC9)
bae5c000 bae5db00 ParVdm ParVdm.SYS Fri Aug 17 22:49:49 2001 (3B7D836D)
bae70000 bae70d00 pciide pciide.sys Fri Aug 17 22:51:49 2001 (3B7D83E5)
baef1000 baef1c00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
baef6000 baef6d00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)
baf5e000 baf5eb80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
baf7f000 baf7fa80 PQNTDrv PQNTDrv.SYS Tue Sep 17 01:14:30 2002 (3D8665D6)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 14:47:34 2007 (45F013F6)
bf9c3000 bf9d4580 dxg dxg.sys Wed Aug 04 08:00:51 2004 (41107B93)
bff70000 bff72480 framebuf framebuf.dll Fri Aug 20 00:38:20 2004 (41252BDC)

Unloaded modules:
b3734000 b375f000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b83c7000 b83f2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
baf15000 baf16000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b907a000 b9087000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b83f2000 b8415000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba9a8000 ba9b6000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bae26000 bae28000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
baa08000 baa16000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bac60000 bac65000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Click to expand...
 
Devil_Himself said:
One Minidump is Insufficient to Determine the Root Cause ... .. if you can
Zip 5-6 Minidumps and upload them to any free web hosting and give me the
link .. i can study them and tell you the result
Click to expand...

Oh thx, you're very nice. As far as I remember that was the only one,
because I never had problems before. But I'll double check and if more than
one is available I'll be glad to link them up to go ahead with this analysis.
Talk to u later, Ric
 
Devil_Himself said:
One Minidump is Insufficient to Determine the Root Cause ... .. if you can
Zip 5-6 Minidumps and upload them to any free web hosting and give me the
link .. i can study them and tell you the result
Click to expand...

Yes, that was the only one dump file.
Possibly, I can try to provide you with some pieces of registry?

Here it is what I found about asus smart doctor in HKLM/Software:


[HKEY_LOCAL_MACHINE\SOFTWARE\ASUS\SmartDoctor]
"InstalledTime"="11-19-2007"
"InstalledDir"="C:\Programmi\T3u\ASUS-SmartDoctor"
"UninstallPath"="C:\PROGRA~1\FILECO~1\INSTAL~1\Driver\9\INTEL3~1\IDriver.exe
/M{12E11FBB-7CA6-4A86-834D-5E6390D51009} /l1033 "
"Path"="C:\Programmi\T3u\ASUS-SmartDoctor\SmartDoctor.exe /start"
"Deccription"=""
"DisplayName"="ASUS SmartDoctor"
"CapabilityForAiPanel"=dword:0000004f
"ControlType"=dword:00000001
"UninstallReboot"=dword:00000000
"MultipleInstance"=dword:00000000
"TrayIconResourceid"=dword:00000000
"IconResourceid"=dword:00000000
"ClassName"="Askin1.0"
"CaptionName"="ASUS SmartDoctor"
"ReleaseTime"=""
"AiPanelVersion"=dword:00000000
"Version"=dword:00000000
"ID"="ASUS_VGA_SMART_DOCTOR"
"EIO_Init"=dword:00000002
"MinimizeWindowFor3D"=dword:00000001
"Auto Fan Control"=dword:00000001
"Fan SpeedMode"=dword:00000004
"Auto Lower Clock"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\ASUS\SmartDoctor\Setting]
"UninstallPath"=""
"Path"=""
@=""
"Monitoring Polling Time"=dword:00000005
"Auto Lower Clock"=dword:00000000
"Disable Alarm in FullScreen"=dword:00000000
"MinimizeWindowFor3D"=dword:00000001
"MinimizeWindow"=dword:00000000
"FBVDDQCheck"=dword:00000000
"VCCCheck"=dword:00000000
"NVVDDCheck"=dword:00000000
"GPUTemperatureCheck"=dword:00000000
"RAMTemperatureCheck"=dword:00000000
"FanSpeedCheck"=dword:00000000
"RAMTemperatureValue"=dword:00000000
"GPUTemperatureValue"=dword:00000000
"FanSpeedBound"=dword:00000000
"Fan DutyCycleValue"=dword:0000003c
"VoltageError"=dword:00000000
"Fan SpeedMode"=dword:00000002
"Auto Fan Control"=dword:00000001
"Fan Top TemperatureLimit"=dword:0000003c
"Fan High TemperatureLimit"=dword:00000037
"Fan Median TemperatureLimit"=dword:00000032
"Fan Low TemperatureLimit"=dword:0000002d
"EnableSmartTune"=dword:00000000
"SmartTuneMODE"=dword:00000000
"LastFrequencyLevel"=dword:00000003
"EnableManualOverClcok"=dword:00000000
"ManualOverClockRate"=dword:00000000
"EnableDynamicOverclock"=dword:00000000
"AGPVDDQCheck"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\ASUS\SmartDoctor\Setting\Timing0]
"usetweak"=dword:00000000
@=""
"ssid"=dword:00000000
"devid"=dword:00000000
"ramcfg"=dword:00000000
"mclk"=dword:00000000
"nvclk"=dword:00000000
 
Suggestion
1.Run "memtest" to stress the ram. If memtest reports the ram is faulty, ram
is bad. Sometimes some faulty ram can pass memtest .Reset the memory stick to
another slot.If You have More then one Stick of Ram Take out one memory stick
And Run "Memtest" on each separately . If windows does not crash, the removed
memory stick is faulty.

2.Check the temperature of the CPU and make sure that it is not overheat.
Make sure that the CPU fan works properly . Try Changing It

3.Clean the dust inside the computer case

4.Make sure that your PSU have adequate power For all the hardware.

5.Update Video Card Drivers. Also Reset video card. Run 3DMark to test your
video card. Check to default setting if you video card is "overclocked"

6. Run chkdsk /r at command prompt
 
Devil_Himself said:
6. Run chkdsk /r at command prompt
Click to expand...

I did this at first and during stage 4 (of 5) it returned "an unspecified
error occurred". And prompted back with cursor.
On another partition: ALL ntfs boot sectors unreadable.

The disk is about 5 months old.
I am not going to test ram or video card before solving this of course.
Previously I attempted a chkdsk but didnt use /r (but /f ), and dont know
the difference, but now I made it right apparently.
Thanks for advicing. I keep investigating this issue.
 
"chkdsk /r" does the same thing as "chkdsk /f" only it also checks for bad
sectors on the disk and recovers any readable information. Running "chkdsk
/r" implies that also "chkdsk /f" is run.

"chkdsk /f" only checks for disk errors, not bad sectors.
 
The help says chkdsk /r is only available from the recovery console prompt.

start/run, type:
HH mk:@MSITStore:%windir%\Help\bootcons.chm::/bootcons_chkdsk.htm
 
As I wrote earlier, from your list my first attempt was chkdsk.

I have tried again, and in the active partition (where it said all sector
unreadable) now it went fine: two details to report.

1) it found some free space as allocated and corrected the issue
2) more important, I believe: it found one bad sector and marked it as such
(4 KB).
It was related to a file called nv_io.pnf (maybe involved in raid
controller, which I am using)

From googling .pnf it says that if missing they are regenerated. But since
my problem seems still in place, do you think I should make it someway from
related .inf?
If so, how?
 
Mark L. Ferguson said:
The help says chkdsk /r is only available from the recovery console prompt.

start/run, type:
HH mk:@MSITStore:%windir%\Help\bootcons.chm::/bootcons_chkdsk.htm
Click to expand...

Good to know how to do it, I'll take note of it.
Maybe when I tried first time something was locked on the active
partition...who knows.
 
D_H has done a great job of putting you on some good lines of thought. I was
trying to keep you from worrying about what is probably an 'extraneous' bit
of 'errata'. From the start of the thread I was thinking you have a 'flaky'
hard drive, and it's telling you to 'save data and get a new one' loud and
clear. You are closer to the issue, and probably know what you need.
 
Mark L. Ferguson said:
D_H has done a great job of putting you on some good lines of thought. I was
trying to keep you from worrying about what is probably an 'extraneous' bit
of 'errata'. From the start of the thread I was thinking you have a 'flaky'
hard drive, and it's telling you to 'save data and get a new one' loud and
clear. You are closer to the issue, and probably know what you need.
Click to expand...

Yes, that's what I am thinking, ur perfectly right.
Chkdsk is shoving a few other unreadable file sectors.
I am gonna mirror the disk over another new one that I already have.

Even so, right after that, I want to understand what is going on as much as
I can (and u all are being of unvaluable support), because, if the disk is
almost gone, I want to claim my warranty rights. It's just 5 months old, and
I don't even keep disks working 24 hours a day, at all.
So I believe I should test it with seagate tool and see what happens.
I've appreciated your thoughts also, thank you.
Ricardo
 
Mark L. Ferguson said:
D_H has done a great job of putting you on some good lines of thought. I was
trying to keep you from worrying about what is probably an 'extraneous' bit
of 'errata'. From the start of the thread I was thinking you have a 'flaky'
hard drive, and it's telling you to 'save data and get a new one' loud and
clear. You are closer to the issue, and probably know what you need.
Click to expand...

To tell the end of the story, I ran the seagate tool to test their
hard-drive, it failed right away the self-test and adviced to go ahead with
the long test, which never went beyond 10-13% and stuck itself.
It's easy to say from a light metallic noise at that point that it was
actually a hardware failure.

Just to add more details: I made an xp install on a new drive.
When the other drive was mounted as it was, that is as a single stripe disk
(and sata enabled from bios), even the new OS couldn't boot with same problem
as the failed drive.
When I disabled raid feature, the new OS could boot and get to win logon
screen after a couple of minutes (displaying regular logo and progress bar
beneath). At this point several errors came up like that XP couldn't write
$MFT on the other drive unit (and that something like "systemRestoreVolume.."
was damaged and couldn't be mounted) .
I ran scan disk on the damaged disk and after several attempt (in which OS
froze up and I had to reset) the progress bar reached the end, but still a
message said that it couldn't complete succesfully that task.

I believe that the failure involved some mechanical part of the drive, which
led to write errors and bad blocks. But since I made an image of the drive I
am willing to test whether it actually works or not, because if the fault is
in the microelectronic controllers perhaps files are still good and with a
system files recheck I could recover my desktop setup.
By the way, I got a replacement drive from seagate, clearly.
Thank you guys for your assistence, best regards.

Rick
 
Back
Top