Hi, I'm new, so if I ask stupid questions or offend protocols, please speak up.
Having far too many 'system error, category 102, event 1003) happenings in WniXP(Home), I decided to try to have a first ever look at the minidump files.
Following the instructions in the Microsoft support document, I downloaded the Windows debugging tools, copied i386 from the CD to Windows, moved the minidump files to the suggested location, cut and pasted the batch file into the correct folder and connected to the net before running the batch file.
This is what I got:-
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\minidump\mini112506-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: c:\windows\i386
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Nov 25 12:33:22.656 2006 (GMT+0)
System Uptime: 0 days 1:36:12.218
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, e30e0000, f016b72c, 0}
ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : win32k.sys ( win32k!HmgRemoveObject+a0 )
Followup: MachineOwner
---------
It appears that, despite the net connection, the debugger was unable to connect with the symbols files. Is it possible that this is because Firefox is my default browser? Surely Microsoft is not that small minded.
Can anyone explain the significance of the 'Probably caused by : win32k.sys' comment in the penultimate line? Should I just run sfc /scannow, or is it something deeper than that?
Think carefully before offering help because, if I get to see the contents of the files, I will almost certainly be back to ask what it all means. <BG>
Having far too many 'system error, category 102, event 1003) happenings in WniXP(Home), I decided to try to have a first ever look at the minidump files.
Following the instructions in the Microsoft support document, I downloaded the Windows debugging tools, copied i386 from the CD to Windows, moved the minidump files to the suggested location, cut and pasted the batch file into the correct folder and connected to the net before running the batch file.
This is what I got:-
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\minidump\mini112506-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: c:\windows\i386
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Nov 25 12:33:22.656 2006 (GMT+0)
System Uptime: 0 days 1:36:12.218
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, e30e0000, f016b72c, 0}
ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : win32k.sys ( win32k!HmgRemoveObject+a0 )
Followup: MachineOwner
---------
It appears that, despite the net connection, the debugger was unable to connect with the symbols files. Is it possible that this is because Firefox is my default browser? Surely Microsoft is not that small minded.
Can anyone explain the significance of the 'Probably caused by : win32k.sys' comment in the penultimate line? Should I just run sfc /scannow, or is it something deeper than that?
Think carefully before offering help because, if I get to see the contents of the files, I will almost certainly be back to ask what it all means. <BG>