Rebooting Frequently

Toggle sidebar Toggle sidebar
J

J

Distinguished
Apr 2, 2004
373
0
18,780
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

Can someone tell me what could be causing my HP NX5000 Laptop to reboot for
no apparent reason?
It happens when the user is in MS Word, ver 2003, he/she will be typing and
then get a fatal eror message... when they click ok it reboots. Below is a
copy of the dump file.


Loading dump file mini102004-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 80543e58
PsLoadedModuleList 80543530
PsActiveProcessHead 80545578
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 1000008e
BugCheckParameter1 c0000005
BugCheckParameter2 805ac9e5
BugCheckParameter3 f9a23d20
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 805353e0
MiniDumpFields 000004ff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 00002268
ThreadOffset 000024c0
CallStackOffset 00002720
SizeOfCallStack 00004000
DriverListOffset 000069b0
DriverCount 0000008e
StringPoolOffset 000093d8
StringPoolSize 00002a08
BrokenDriverOffset 00000000
TriageOptions ffffffff
TopOfStack f9a23d94
DebuggerDataOffset 00006720
DebuggerDataSize 00000290


Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Wed Oct 20 12:09:56 2004
System Uptime: 0 days 0:11:30
start end module name
804d4000 806aa280 nt Checksum: 001E311B Timestamp: Thu Apr 24
10:
57:43 2003 (3EA80977)

Unloaded modules:
ef98c000 ef9b3000 kmixer.sys Timestamp: unavailable (00000000)
effe6000 f000d000 kmixer.sys Timestamp: unavailable (00000000)
f9b7d000 f9b7e000 drmkaud.sys Timestamp: unavailable (00000000)
f01ba000 f01c7000 DMusic.sys Timestamp: unavailable (00000000)
f01ca000 f01d8000 swmidi.sys Timestamp: unavailable (00000000)
f00ad000 f00d0000 aec.sys Timestamp: unavailable (00000000)
f0919000 f091b000 splitter.sys Timestamp: unavailable (00000000)
f96a8000 f96b2000 imapi.sys Timestamp: unavailable (00000000)
f9890000 f9898000 processr.sys Timestamp: unavailable (00000000)
f9870000 f9875000 Cdaudio.SYS Timestamp: unavailable (00000000)
f99d4000 f99d7000 Sfloppy.SYS Timestamp: unavailable (00000000)
f9868000 f986d000 Flpydisk.SYS Timestamp: unavailable (00000000)

Finished dump check
 
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

Also The computer is using SP1.
(I don't know how I ended up with 2 threads)

"J" wrote:

> Can someone tell me what could be causing my HP NX5000 Laptop to reboot for
> no apparent reason?
> It happens when the user is in MS Word, ver 2003, he/she will be typing and
> then get a fatal eror message... when they click ok it reboots. Below is a
> copy of the dump file.
>
>
> Loading dump file mini102004-01.dmp
> ----- 32 bit Kernel Mini Dump Analysis
>
> DUMP_HEADER32:
> MajorVersion 0000000f
> MinorVersion 00000a28
> DirectoryTableBase 00039000
> PfnDataBase 80543e58
> PsLoadedModuleList 80543530
> PsActiveProcessHead 80545578
> MachineImageType 0000014c
> NumberProcessors 00000001
> BugCheckCode 1000008e
> BugCheckParameter1 c0000005
> BugCheckParameter2 805ac9e5
> BugCheckParameter3 f9a23d20
> BugCheckParameter4 00000000
> PaeEnabled 00000000
> KdDebuggerDataBlock 805353e0
> MiniDumpFields 000004ff
>
> TRIAGE_DUMP32:
> ServicePackBuild 00000100
> SizeOfDump 00010000
> ValidOffset 0000fffc
> ContextOffset 00000320
> ExceptionOffset 000007d0
> MmOffset 00001068
> UnloadedDriversOffset 000010a0
> PrcbOffset 00001878
> ProcessOffset 00002268
> ThreadOffset 000024c0
> CallStackOffset 00002720
> SizeOfCallStack 00004000
> DriverListOffset 000069b0
> DriverCount 0000008e
> StringPoolOffset 000093d8
> StringPoolSize 00002a08
> BrokenDriverOffset 00000000
> TriageOptions ffffffff
> TopOfStack f9a23d94
> DebuggerDataOffset 00006720
> DebuggerDataSize 00000290
>
>
> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
> Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
> Debug session time: Wed Oct 20 12:09:56 2004
> System Uptime: 0 days 0:11:30
> start end module name
> 804d4000 806aa280 nt Checksum: 001E311B Timestamp: Thu Apr 24
> 10:
> 57:43 2003 (3EA80977)
>
> Unloaded modules:
> ef98c000 ef9b3000 kmixer.sys Timestamp: unavailable (00000000)
> effe6000 f000d000 kmixer.sys Timestamp: unavailable (00000000)
> f9b7d000 f9b7e000 drmkaud.sys Timestamp: unavailable (00000000)
> f01ba000 f01c7000 DMusic.sys Timestamp: unavailable (00000000)
> f01ca000 f01d8000 swmidi.sys Timestamp: unavailable (00000000)
> f00ad000 f00d0000 aec.sys Timestamp: unavailable (00000000)
> f0919000 f091b000 splitter.sys Timestamp: unavailable (00000000)
> f96a8000 f96b2000 imapi.sys Timestamp: unavailable (00000000)
> f9890000 f9898000 processr.sys Timestamp: unavailable (00000000)
> f9870000 f9875000 Cdaudio.SYS Timestamp: unavailable (00000000)
> f99d4000 f99d7000 Sfloppy.SYS Timestamp: unavailable (00000000)
> f9868000 f986d000 Flpydisk.SYS Timestamp: unavailable (00000000)
>
> Finished dump check
 
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

This won't fix your problem, but it'll keep your machine from rebooting.

Choosing recovery actions if Windows stops unexpectedly

Right click My Computer | Properties | Advanced tab |
Click the Settings button under Startup and Recovery |
Under System Failure | UNCheck: ? Automatically restart |
OK |Apply | OK

[[Specifies whether Windows will automatically reboot whenever the system
stops unexpectedly.
You must be logged on as a member of the Administrators group to set
recovery options.]]

--
Hope this helps. Let us know.
Wes

In news:5694A5C0-A04D-4FEE-83F5-A2161D619DAC@microsoft.com,
J <J@discussions.microsoft.com> hunted and pecked:
> Also The computer is using SP1.
> (I don't know how I ended up with 2 threads)
>
> "J" wrote:
>
>> Can someone tell me what could be causing my HP NX5000 Laptop to
>> reboot for no apparent reason?
>> It happens when the user is in MS Word, ver 2003, he/she will be
>> typing and then get a fatal eror message... when they click ok it
>> reboots. Below is a copy of the dump file.
>>
>>
>> Loading dump file mini102004-01.dmp
>> ----- 32 bit Kernel Mini Dump Analysis
>>
>> DUMP_HEADER32:
>> MajorVersion 0000000f
>> MinorVersion 00000a28
>> DirectoryTableBase 00039000
>> PfnDataBase 80543e58
>> PsLoadedModuleList 80543530
>> PsActiveProcessHead 80545578
>> MachineImageType 0000014c
>> NumberProcessors 00000001
>> BugCheckCode 1000008e
>> BugCheckParameter1 c0000005
>> BugCheckParameter2 805ac9e5
>> BugCheckParameter3 f9a23d20
>> BugCheckParameter4 00000000
>> PaeEnabled 00000000
>> KdDebuggerDataBlock 805353e0
>> MiniDumpFields 000004ff
>>
>> TRIAGE_DUMP32:
>> ServicePackBuild 00000100
>> SizeOfDump 00010000
>> ValidOffset 0000fffc
>> ContextOffset 00000320
>> ExceptionOffset 000007d0
>> MmOffset 00001068
>> UnloadedDriversOffset 000010a0
>> PrcbOffset 00001878
>> ProcessOffset 00002268
>> ThreadOffset 000024c0
>> CallStackOffset 00002720
>> SizeOfCallStack 00004000
>> DriverListOffset 000069b0
>> DriverCount 0000008e
>> StringPoolOffset 000093d8
>> StringPoolSize 00002a08
>> BrokenDriverOffset 00000000
>> TriageOptions ffffffff
>> TopOfStack f9a23d94
>> DebuggerDataOffset 00006720
>> DebuggerDataSize 00000290
>>
>>
>> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86
>> compatible Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
>> Debug session time: Wed Oct 20 12:09:56 2004
>> System Uptime: 0 days 0:11:30
>> start end module name
>> 804d4000 806aa280 nt Checksum: 001E311B Timestamp:
>> Thu Apr 24 10:
>> 57:43 2003 (3EA80977)
>>
>> Unloaded modules:
>> ef98c000 ef9b3000 kmixer.sys Timestamp: unavailable (00000000)
>> effe6000 f000d000 kmixer.sys Timestamp: unavailable (00000000)
>> f9b7d000 f9b7e000 drmkaud.sys Timestamp: unavailable (00000000)
>> f01ba000 f01c7000 DMusic.sys Timestamp: unavailable (00000000)
>> f01ca000 f01d8000 swmidi.sys Timestamp: unavailable (00000000)
>> f00ad000 f00d0000 aec.sys Timestamp: unavailable (00000000)
>> f0919000 f091b000 splitter.sys Timestamp: unavailable (00000000)
>> f96a8000 f96b2000 imapi.sys Timestamp: unavailable (00000000)
>> f9890000 f9898000 processr.sys Timestamp: unavailable (00000000)
>> f9870000 f9875000 Cdaudio.SYS Timestamp: unavailable (00000000)
>> f99d4000 f99d7000 Sfloppy.SYS Timestamp: unavailable (00000000)
>> f9868000 f986d000 Flpydisk.SYS Timestamp: unavailable (00000000)
>>
>> Finished dump check
 
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

I'm not wanting to keep the computer from rebooting...I'm wanting to fix it.

Anyone else have ideas?

"Wesley Vogel" wrote:

> This won't fix your problem, but it'll keep your machine from rebooting.
>
> Choosing recovery actions if Windows stops unexpectedly
>
> Right click My Computer | Properties | Advanced tab |
> Click the Settings button under Startup and Recovery |
> Under System Failure | UNCheck: Â? Automatically restart |
> OK |Apply | OK
>
> [[Specifies whether Windows will automatically reboot whenever the system
> stops unexpectedly.
> You must be logged on as a member of the Administrators group to set
> recovery options.]]
>
> --
> Hope this helps. Let us know.
> Wes
>
> In news:5694A5C0-A04D-4FEE-83F5-A2161D619DAC@microsoft.com,
> J <J@discussions.microsoft.com> hunted and pecked:
> > Also The computer is using SP1.
> > (I don't know how I ended up with 2 threads)
> >
> > "J" wrote:
> >
> >> Can someone tell me what could be causing my HP NX5000 Laptop to
> >> reboot for no apparent reason?
> >> It happens when the user is in MS Word, ver 2003, he/she will be
> >> typing and then get a fatal eror message... when they click ok it
> >> reboots. Below is a copy of the dump file.
> >>
> >>
> >> Loading dump file mini102004-01.dmp
> >> ----- 32 bit Kernel Mini Dump Analysis
> >>
> >> DUMP_HEADER32:
> >> MajorVersion 0000000f
> >> MinorVersion 00000a28
> >> DirectoryTableBase 00039000
> >> PfnDataBase 80543e58
> >> PsLoadedModuleList 80543530
> >> PsActiveProcessHead 80545578
> >> MachineImageType 0000014c
> >> NumberProcessors 00000001
> >> BugCheckCode 1000008e
> >> BugCheckParameter1 c0000005
> >> BugCheckParameter2 805ac9e5
> >> BugCheckParameter3 f9a23d20
> >> BugCheckParameter4 00000000
> >> PaeEnabled 00000000
> >> KdDebuggerDataBlock 805353e0
> >> MiniDumpFields 000004ff
> >>
> >> TRIAGE_DUMP32:
> >> ServicePackBuild 00000100
> >> SizeOfDump 00010000
> >> ValidOffset 0000fffc
> >> ContextOffset 00000320
> >> ExceptionOffset 000007d0
> >> MmOffset 00001068
> >> UnloadedDriversOffset 000010a0
> >> PrcbOffset 00001878
> >> ProcessOffset 00002268
> >> ThreadOffset 000024c0
> >> CallStackOffset 00002720
> >> SizeOfCallStack 00004000
> >> DriverListOffset 000069b0
> >> DriverCount 0000008e
> >> StringPoolOffset 000093d8
> >> StringPoolSize 00002a08
> >> BrokenDriverOffset 00000000
> >> TriageOptions ffffffff
> >> TopOfStack f9a23d94
> >> DebuggerDataOffset 00006720
> >> DebuggerDataSize 00000290
> >>
> >>
> >> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86
> >> compatible Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
> >> Debug session time: Wed Oct 20 12:09:56 2004
> >> System Uptime: 0 days 0:11:30
> >> start end module name
> >> 804d4000 806aa280 nt Checksum: 001E311B Timestamp:
> >> Thu Apr 24 10:
> >> 57:43 2003 (3EA80977)
> >>
> >> Unloaded modules:
> >> ef98c000 ef9b3000 kmixer.sys Timestamp: unavailable (00000000)
> >> effe6000 f000d000 kmixer.sys Timestamp: unavailable (00000000)
> >> f9b7d000 f9b7e000 drmkaud.sys Timestamp: unavailable (00000000)
> >> f01ba000 f01c7000 DMusic.sys Timestamp: unavailable (00000000)
> >> f01ca000 f01d8000 swmidi.sys Timestamp: unavailable (00000000)
> >> f00ad000 f00d0000 aec.sys Timestamp: unavailable (00000000)
> >> f0919000 f091b000 splitter.sys Timestamp: unavailable (00000000)
> >> f96a8000 f96b2000 imapi.sys Timestamp: unavailable (00000000)
> >> f9890000 f9898000 processr.sys Timestamp: unavailable (00000000)
> >> f9870000 f9875000 Cdaudio.SYS Timestamp: unavailable (00000000)
> >> f99d4000 f99d7000 Sfloppy.SYS Timestamp: unavailable (00000000)
> >> f9868000 f986d000 Flpydisk.SYS Timestamp: unavailable (00000000)
> >>
> >> Finished dump check
>
>
 
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

Follow my previous advice and then when you suffer from [[reboot for
no apparent reason]] you can open the Event Viewer and see if you can find
the reason.

Look in System or Application.

To open the Event Viewer...
Start | Run | Type: eventvwr | OK

Double click the event in Event Viewer | Click: the button below the second
arrow (looks like two pages) [[Copies the details of the event to the
Clipboard.]] | Paste into Notepad | Click:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Read all info | Copy and paste to Notepad | Click the [+] Related Knowledge
Base articles | Follow any links that might be useful


--
Hope this helps. Let us know.
Wes

In news:11958F30-7760-4749-882E-E8F1F4D62759@microsoft.com,
J <J@discussions.microsoft.com> hunted and pecked:
> I'm not wanting to keep the computer from rebooting...I'm wanting to
> fix it.
>
> Anyone else have ideas?
>
> "Wesley Vogel" wrote:
>
>> This won't fix your problem, but it'll keep your machine from
>> rebooting.
>>
>> Choosing recovery actions if Windows stops unexpectedly
>>
>> Right click My Computer | Properties | Advanced tab |
>> Click the Settings button under Startup and Recovery |
>> Under System Failure | UNCheck: Â? Automatically restart |
>> OK |Apply | OK
>>
>> [[Specifies whether Windows will automatically reboot whenever the
>> system stops unexpectedly.
>> You must be logged on as a member of the Administrators group to set
>> recovery options.]]
>>
>> --
>> Hope this helps. Let us know.
>> Wes
>>
>> In news:5694A5C0-A04D-4FEE-83F5-A2161D619DAC@microsoft.com,
>> J <J@discussions.microsoft.com> hunted and pecked:
>>> Also The computer is using SP1.
>>> (I don't know how I ended up with 2 threads)
>>>
>>> "J" wrote:
>>>
>>>> Can someone tell me what could be causing my HP NX5000 Laptop to
>>>> reboot for no apparent reason?
>>>> It happens when the user is in MS Word, ver 2003, he/she will be
>>>> typing and then get a fatal eror message... when they click ok it
>>>> reboots. Below is a copy of the dump file.
>>>>
>>>>
>>>> Loading dump file mini102004-01.dmp
>>>> ----- 32 bit Kernel Mini Dump Analysis
>>>>
>>>> DUMP_HEADER32:
>>>> MajorVersion 0000000f
>>>> MinorVersion 00000a28
>>>> DirectoryTableBase 00039000
>>>> PfnDataBase 80543e58
>>>> PsLoadedModuleList 80543530
>>>> PsActiveProcessHead 80545578
>>>> MachineImageType 0000014c
>>>> NumberProcessors 00000001
>>>> BugCheckCode 1000008e
>>>> BugCheckParameter1 c0000005
>>>> BugCheckParameter2 805ac9e5
>>>> BugCheckParameter3 f9a23d20
>>>> BugCheckParameter4 00000000
>>>> PaeEnabled 00000000
>>>> KdDebuggerDataBlock 805353e0
>>>> MiniDumpFields 000004ff
>>>>
>>>> TRIAGE_DUMP32:
>>>> ServicePackBuild 00000100
>>>> SizeOfDump 00010000
>>>> ValidOffset 0000fffc
>>>> ContextOffset 00000320
>>>> ExceptionOffset 000007d0
>>>> MmOffset 00001068
>>>> UnloadedDriversOffset 000010a0
>>>> PrcbOffset 00001878
>>>> ProcessOffset 00002268
>>>> ThreadOffset 000024c0
>>>> CallStackOffset 00002720
>>>> SizeOfCallStack 00004000
>>>> DriverListOffset 000069b0
>>>> DriverCount 0000008e
>>>> StringPoolOffset 000093d8
>>>> StringPoolSize 00002a08
>>>> BrokenDriverOffset 00000000
>>>> TriageOptions ffffffff
>>>> TopOfStack f9a23d94
>>>> DebuggerDataOffset 00006720
>>>> DebuggerDataSize 00000290
>>>>
>>>>
>>>> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86
>>>> compatible Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
>>>> Debug session time: Wed Oct 20 12:09:56 2004
>>>> System Uptime: 0 days 0:11:30
>>>> start end module name
>>>> 804d4000 806aa280 nt Checksum: 001E311B Timestamp:
>>>> Thu Apr 24 10:
>>>> 57:43 2003 (3EA80977)
>>>>
>>>> Unloaded modules:
>>>> ef98c000 ef9b3000 kmixer.sys Timestamp: unavailable (00000000)
>>>> effe6000 f000d000 kmixer.sys Timestamp: unavailable (00000000)
>>>> f9b7d000 f9b7e000 drmkaud.sys Timestamp: unavailable
>>>> (00000000) f01ba000 f01c7000 DMusic.sys Timestamp:
>>>> unavailable (00000000) f01ca000 f01d8000 swmidi.sys
>>>> Timestamp: unavailable (00000000) f00ad000 f00d0000 aec.sys
>>>> Timestamp: unavailable (00000000) f0919000 f091b000 splitter.sys
>>>> Timestamp: unavailable (00000000) f96a8000 f96b2000 imapi.sys
>>>> Timestamp: unavailable (00000000) f9890000 f9898000 processr.sys
>>>> Timestamp: unavailable (00000000) f9870000 f9875000 Cdaudio.SYS
>>>> Timestamp: unavailable (00000000) f99d4000 f99d7000 Sfloppy.SYS
>>>> Timestamp: unavailable (00000000) f9868000 f986d000 Flpydisk.SYS
>>>> Timestamp: unavailable (00000000)
>>>>
>>>> Finished dump check
 
Archived from groups: microsoft.public.windowsxp.configuration_manage (More info?)

Also, you'll be able to read the BSOD if it appears. ;-)

--
Hope this helps. Let us know.
Wes

In news:Of$wCJ4tEHA.2468@TK2MSFTNGP09.phx.gbl,
Wesley Vogel <123WVogel955@comcast.net> hunted and pecked:
> Follow my previous advice and then when you suffer from [[reboot for
> no apparent reason]] you can open the Event Viewer and see if you can
> find the reason.
>
> Look in System or Application.
>
> To open the Event Viewer...
> Start | Run | Type: eventvwr | OK
>
> Double click the event in Event Viewer | Click: the button below the
> second arrow (looks like two pages) [[Copies the details of the event
> to the Clipboard.]] | Paste into Notepad | Click:
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Read all info | Copy and paste to Notepad | Click the [+] Related
> Knowledge Base articles | Follow any links that might be useful
>
>
>
> In news:11958F30-7760-4749-882E-E8F1F4D62759@microsoft.com,
> J <J@discussions.microsoft.com> hunted and pecked:
>> I'm not wanting to keep the computer from rebooting...I'm wanting to
>> fix it.
>>
>> Anyone else have ideas?
>>
>> "Wesley Vogel" wrote:
>>
>>> This won't fix your problem, but it'll keep your machine from
>>> rebooting.
>>>
>>> Choosing recovery actions if Windows stops unexpectedly
>>>
>>> Right click My Computer | Properties | Advanced tab |
>>> Click the Settings button under Startup and Recovery |
>>> Under System Failure | UNCheck: Â? Automatically restart |
>>> OK |Apply | OK
>>>
>>> [[Specifies whether Windows will automatically reboot whenever the
>>> system stops unexpectedly.
>>> You must be logged on as a member of the Administrators group to set
>>> recovery options.]]
>>>
>>> --
>>> Hope this helps. Let us know.
>>> Wes
>>>
>>> In news:5694A5C0-A04D-4FEE-83F5-A2161D619DAC@microsoft.com,
>>> J <J@discussions.microsoft.com> hunted and pecked:
>>>> Also The computer is using SP1.
>>>> (I don't know how I ended up with 2 threads)
>>>>
>>>> "J" wrote:
>>>>
>>>>> Can someone tell me what could be causing my HP NX5000 Laptop to
>>>>> reboot for no apparent reason?
>>>>> It happens when the user is in MS Word, ver 2003, he/she will be
>>>>> typing and then get a fatal eror message... when they click ok it
>>>>> reboots. Below is a copy of the dump file.
>>>>>
>>>>>
>>>>> Loading dump file mini102004-01.dmp
>>>>> ----- 32 bit Kernel Mini Dump Analysis
>>>>>
>>>>> DUMP_HEADER32:
>>>>> MajorVersion 0000000f
>>>>> MinorVersion 00000a28
>>>>> DirectoryTableBase 00039000
>>>>> PfnDataBase 80543e58
>>>>> PsLoadedModuleList 80543530
>>>>> PsActiveProcessHead 80545578
>>>>> MachineImageType 0000014c
>>>>> NumberProcessors 00000001
>>>>> BugCheckCode 1000008e
>>>>> BugCheckParameter1 c0000005
>>>>> BugCheckParameter2 805ac9e5
>>>>> BugCheckParameter3 f9a23d20
>>>>> BugCheckParameter4 00000000
>>>>> PaeEnabled 00000000
>>>>> KdDebuggerDataBlock 805353e0
>>>>> MiniDumpFields 000004ff
>>>>>
>>>>> TRIAGE_DUMP32:
>>>>> ServicePackBuild 00000100
>>>>> SizeOfDump 00010000
>>>>> ValidOffset 0000fffc
>>>>> ContextOffset 00000320
>>>>> ExceptionOffset 000007d0
>>>>> MmOffset 00001068
>>>>> UnloadedDriversOffset 000010a0
>>>>> PrcbOffset 00001878
>>>>> ProcessOffset 00002268
>>>>> ThreadOffset 000024c0
>>>>> CallStackOffset 00002720
>>>>> SizeOfCallStack 00004000
>>>>> DriverListOffset 000069b0
>>>>> DriverCount 0000008e
>>>>> StringPoolOffset 000093d8
>>>>> StringPoolSize 00002a08
>>>>> BrokenDriverOffset 00000000
>>>>> TriageOptions ffffffff
>>>>> TopOfStack f9a23d94
>>>>> DebuggerDataOffset 00006720
>>>>> DebuggerDataSize 00000290
>>>>>
>>>>>
>>>>> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86
>>>>> compatible Kernel base = 0x804d4000 PsLoadedModuleList =
>>>>> 0x80543530 Debug session time: Wed Oct 20 12:09:56 2004
>>>>> System Uptime: 0 days 0:11:30
>>>>> start end module name
>>>>> 804d4000 806aa280 nt Checksum: 001E311B Timestamp:
>>>>> Thu Apr 24 10:
>>>>> 57:43 2003 (3EA80977)
>>>>>
>>>>> Unloaded modules:
>>>>> ef98c000 ef9b3000 kmixer.sys Timestamp: unavailable
>>>>> (00000000) effe6000 f000d000 kmixer.sys Timestamp:
>>>>> unavailable (00000000) f9b7d000 f9b7e000 drmkaud.sys
>>>>> Timestamp: unavailable (00000000) f01ba000 f01c7000 DMusic.sys
>>>>> Timestamp: unavailable (00000000) f01ca000 f01d8000 swmidi.sys
>>>>> Timestamp: unavailable (00000000) f00ad000 f00d0000 aec.sys
>>>>> Timestamp: unavailable (00000000) f0919000 f091b000 splitter.sys
>>>>> Timestamp: unavailable (00000000) f96a8000 f96b2000 imapi.sys
>>>>> Timestamp: unavailable (00000000) f9890000 f9898000 processr.sys
>>>>> Timestamp: unavailable (00000000) f9870000 f9875000 Cdaudio.SYS
>>>>> Timestamp: unavailable (00000000) f99d4000 f99d7000 Sfloppy.SYS
>>>>> Timestamp: unavailable (00000000) f9868000 f986d000 Flpydisk.SYS
>>>>> Timestamp: unavailable (00000000)
>>>>>
>>>>> Finished dump check
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom