Reboot on boot

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hello!

I installed a 100gb sata drive with an sata card. On every second boot, a
reboot occurs with this. Would you be abel to decifer it? Thank you!

-Bahman
---------------------------------------------
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\PROGRA~1\DEBUGG~1\Mini022806-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
Debug session time: Tue Feb 28 06:59:47.873 2006 (GMT-8)
System Uptime: not available
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Bugcheck code 00000022
Arguments 000202ef 8166a738 8166a680 81485008

ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
b9595728 00000000 000202ef 8166a738 8166a680 0xbfa55ec8

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000893
KdSecondaryVersion 00000000
DirectoryTableBase 0b434000
PfnDataBase 818cf000
PsLoadedModuleList 80481580
PsActiveProcessHead 80483008
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 00000022
BugCheckParameter1 000202ef
BugCheckParameter2 8166a738
BugCheckParameter3 8166a680
BugCheckParameter4 81485008
PaeEnabled 00000000
KdDebuggerDataBlock 8046d470
MiniDumpFields 45474150

TRIAGE_DUMP32:
ServicePackBuild 00000400
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001050
UnloadedDriversOffset 00001088
PrcbOffset 00001860
ProcessOffset 00002250
ThreadOffset 000024e0
CallStackOffset 00002728
SizeOfCallStack 000008d4
DriverListOffset 00002ffc
DriverCount 00000070
StringPoolOffset 0000513c
StringPoolSize 000020b0
BrokenDriverOffset 00000000
TriageOptions 00000045
TopOfStack b959572c


Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
Debug session time: Tue Feb 28 06:59:47.873 2006 (GMT-8)
System Uptime: not available
start end module name
80400000 8059cd80 nt Thu Oct 06 02:20:25 2005 (4344EC59)

Unloaded modules:
b9feb000 ba3b1000 nv4_disp.dll
Timestamp: unavailable (00000000)
Checksum: 00000000
ed180000 ed189000 redbook.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ed2d0000 ed2d5000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ed4fc000 ed4ff000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
No export analyze found
Finished dump check
 
0x22 FILE_SYSTEM

From what I can tell there is no fix for that one.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| hello!
|
| I installed a 100gb sata drive with an sata card. On every second boot, a
| reboot occurs with this. Would you be abel to decifer it? Thank you!
|
| -Bahman
| ---------------------------------------------
| Microsoft (R) Windows Debugger Version 6.6.0003.5
| Copyright (c) Microsoft Corporation. All rights reserved.
|
|
| Loading Dump File [C:\PROGRA~1\DEBUGG~1\Mini022806-02.dmp]
| Mini Kernel Dump File: Only registers and stack trace are available
|
| Symbol search path is: *** Invalid ***
|
****************************************************************************
| * Symbol loading may be unreliable without a symbol search path.
*
| * Use .symfix to have the debugger choose a symbol path.
*
| * After setting your symbol path, use .reload to refresh symbol locations.
*
|
****************************************************************************
| Executable search path is:
| *********************************************************************
| * Symbols can not be loaded because symbol path is not initialized. *
| * *
| * The Symbol Path can be set by: *
| * using the _NT_SYMBOL_PATH environment variable. *
| * using the -y <symbol_path> argument when starting the debugger. *
| * using .sympath and .sympath+ *
| *********************************************************************
| Unable to load image ntoskrnl.exe, Win32 error 2
| *** WARNING: Unable to verify timestamp for ntoskrnl.exe
| *** ERROR: Module load completed but symbols could not be loaded for
| ntoskrnl.exe
| Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
| Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
| Debug session time: Tue Feb 28 06:59:47.873 2006 (GMT-8)
| System Uptime: not available
| *********************************************************************
| * Symbols can not be loaded because symbol path is not initialized. *
| * *
| * The Symbol Path can be set by: *
| * using the _NT_SYMBOL_PATH environment variable. *
| * using the -y <symbol_path> argument when starting the debugger. *
| * using .sympath and .sympath+ *
| *********************************************************************
|
*******************************************************************************
| *
| *
| * Bugcheck Analysis
| *
| *
| *
|
*******************************************************************************
| Bugcheck code 00000022
| Arguments 000202ef 8166a738 8166a680 81485008
|
| ChildEBP RetAddr Args to Child
| WARNING: Frame IP not in any known module. Following frames may be wrong.
| b9595728 00000000 000202ef 8166a738 8166a680 0xbfa55ec8
|
| ----- 32 bit Kernel Mini Dump Analysis
|
| DUMP_HEADER32:
| MajorVersion 0000000f
| MinorVersion 00000893
| KdSecondaryVersion 00000000
| DirectoryTableBase 0b434000
| PfnDataBase 818cf000
| PsLoadedModuleList 80481580
| PsActiveProcessHead 80483008
| MachineImageType 0000014c
| NumberProcessors 00000001
| BugCheckCode 00000022
| BugCheckParameter1 000202ef
| BugCheckParameter2 8166a738
| BugCheckParameter3 8166a680
| BugCheckParameter4 81485008
| PaeEnabled 00000000
| KdDebuggerDataBlock 8046d470
| MiniDumpFields 45474150
|
| TRIAGE_DUMP32:
| ServicePackBuild 00000400
| SizeOfDump 00010000
| ValidOffset 0000fffc
| ContextOffset 00000320
| ExceptionOffset 000007d0
| MmOffset 00001050
| UnloadedDriversOffset 00001088
| PrcbOffset 00001860
| ProcessOffset 00002250
| ThreadOffset 000024e0
| CallStackOffset 00002728
| SizeOfCallStack 000008d4
| DriverListOffset 00002ffc
| DriverCount 00000070
| StringPoolOffset 0000513c
| StringPoolSize 000020b0
| BrokenDriverOffset 00000000
| TriageOptions 00000045
| TopOfStack b959572c
|
|
| Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
| Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
| Debug session time: Tue Feb 28 06:59:47.873 2006 (GMT-8)
| System Uptime: not available
| start end module name
| 80400000 8059cd80 nt Thu Oct 06 02:20:25 2005 (4344EC59)
|
| Unloaded modules:
| b9feb000 ba3b1000 nv4_disp.dll
| Timestamp: unavailable (00000000)
| Checksum: 00000000
| ed180000 ed189000 redbook.sys
| Timestamp: unavailable (00000000)
| Checksum: 00000000
| ed2d0000 ed2d5000 Cdaudio.SYS
| Timestamp: unavailable (00000000)
| Checksum: 00000000
| ed4fc000 ed4ff000 Sfloppy.SYS
| Timestamp: unavailable (00000000)
| Checksum: 00000000
| No export analyze found
| Finished dump check
|
 
Dave,

I rebuilt this machine twice with the same problem.

The memory and everything else were working fine until this upgrade. So, I
take it the problem is the hard drive or the card?

Also, I can see FILE SYSTEM flashing on blue screen. But I can see the drive
content if I plug it in elsewhere. Would it be the boot sector that is
damaged? Obviously rebuilding is not doing anything so it is something
deeper. Diskchck didn't help either.

-Bahman

Dave Patrick said:
0x22 FILE_SYSTEM

From what I can tell there is no fix for that one.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| hello!
|
| I installed a 100gb sata drive with an sata card. On every second boot, a
| reboot occurs with this. Would you be abel to decifer it? Thank you!
|
| -Bahman
| ---------------------------------------------
| Microsoft (R) Windows Debugger Version 6.6.0003.5
| Copyright (c) Microsoft Corporation. All rights reserved.
|
|
| Loading Dump File [C:\PROGRA~1\DEBUGG~1\Mini022806-02.dmp]
| Mini Kernel Dump File: Only registers and stack trace are available
|
| Symbol search path is: *** Invalid ***
|
****************************************************************************
| * Symbol loading may be unreliable without a symbol search path.
*
| * Use .symfix to have the debugger choose a symbol path.
*
| * After setting your symbol path, use .reload to refresh symbol locations.
*
|
****************************************************************************
| Executable search path is:
| *********************************************************************
| * Symbols can not be loaded because symbol path is not initialized. *
| * *
| * The Symbol Path can be set by: *
| * using the _NT_SYMBOL_PATH environment variable. *
| * using the -y <symbol_path> argument when starting the debugger. *
| * using .sympath and .sympath+ *
| *********************************************************************
| Unable to load image ntoskrnl.exe, Win32 error 2
| *** WARNING: Unable to verify timestamp for ntoskrnl.exe
| *** ERROR: Module load completed but symbols could not be loaded for
| ntoskrnl.exe
| Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
| Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
| Debug session time: Tue Feb 28 06:59:47.873 2006 (GMT-8)
| System Uptime: not available
| *********************************************************************
| * Symbols can not be loaded because symbol path is not initialized. *
| * *
| * The Symbol Path can be set by: *
| * using the _NT_SYMBOL_PATH environment variable. *
| * using the -y <symbol_path> argument when starting the debugger. *
| * using .sympath and .sympath+ *
| *********************************************************************
|
*******************************************************************************
| *
| *
| * Bugcheck Analysis
| *
| *
| *
|
*******************************************************************************
| Bugcheck code 00000022
| Arguments 000202ef 8166a738 8166a680 81485008
|
| ChildEBP RetAddr Args to Child
| WARNING: Frame IP not in any known module. Following frames may be wrong.
| b9595728 00000000 000202ef 8166a738 8166a680 0xbfa55ec8
|
| ----- 32 bit Kernel Mini Dump Analysis
|
| DUMP_HEADER32:
| MajorVersion 0000000f
| MinorVersion 00000893
| KdSecondaryVersion 00000000
| DirectoryTableBase 0b434000
| PfnDataBase 818cf000
| PsLoadedModuleList 80481580
| PsActiveProcessHead 80483008
| MachineImageType 0000014c
| NumberProcessors 00000001
| BugCheckCode 00000022
| BugCheckParameter1 000202ef
| BugCheckParameter2 8166a738
| BugCheckParameter3 8166a680
| BugCheckParameter4 81485008
| PaeEnabled 00000000
| KdDebuggerDataBlock 8046d470
| MiniDumpFields 45474150
|
| TRIAGE_DUMP32:
| ServicePackBuild 00000400
| SizeOfDump 00010000
| ValidOffset 0000fffc
| ContextOffset 00000320
| ExceptionOffset 000007d0
| MmOffset 00001050
| UnloadedDriversOffset 00001088
| PrcbOffset 00001860
| ProcessOffset 00002250
| ThreadOffset 000024e0
| CallStackOffset 00002728
| SizeOfCallStack 000008d4
| DriverListOffset 00002ffc
| DriverCount 00000070
| StringPoolOffset 0000513c
| StringPoolSize 000020b0
| BrokenDriverOffset 00000000
| TriageOptions 00000045
| TopOfStack b959572c
|
|
| Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
| Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
| Debug session time: Tue Feb 28 06:59:47.873 2006 (GMT-8)
| System Uptime: not available
| start end module name
| 80400000 8059cd80 nt Thu Oct 06 02:20:25 2005 (4344EC59)
|
| Unloaded modules:
| b9feb000 ba3b1000 nv4_disp.dll
| Timestamp: unavailable (00000000)
| Checksum: 00000000
| ed180000 ed189000 redbook.sys
| Timestamp: unavailable (00000000)
| Checksum: 00000000
| ed2d0000 ed2d5000 Cdaudio.SYS
| Timestamp: unavailable (00000000)
| Checksum: 00000000
| ed4fc000 ed4ff000 Sfloppy.SYS
| Timestamp: unavailable (00000000)
| Checksum: 00000000
| No export analyze found
| Finished dump check
|
Click to expand...
 
You can download and run a disk diagnostic from the drive manufacturer's web
site. I'd be more inclined to point the finger at the drive controller,
cables, or memory.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Dave,
|
| I rebuilt this machine twice with the same problem.
|
| The memory and everything else were working fine until this upgrade. So, I
| take it the problem is the hard drive or the card?
|
| Also, I can see FILE SYSTEM flashing on blue screen. But I can see the
drive
| content if I plug it in elsewhere. Would it be the boot sector that is
| damaged? Obviously rebuilding is not doing anything so it is something
| deeper. Diskchck didn't help either.
|
| -Bahman
 
Back
Top