Re: XP crashes, dmp files added.
- From: "rina" <peterholm@xxxxxxxxx>
- Date: Mon, 30 Jan 2006 00:22:38 +0200
Hi,
I don't use online error messaging.
I haven't got ever any relevant replies from MS.
Also, as the computer(s) are not mine, MS considers me an OEM who doesn't
get free support.
"David Candy" <.> wrote in message
news:OhBmDZRJGHA.2320@xxxxxxxxxxxxxxxxxxxxxxx
Did you use online error reporting. If so what did it say about the problem.
I just wrote this to Intel
------------------------------------------------------------------------------------------------
http://www.intel.com/support/chipsets/imst/sb/CS-020826.htm
This page refers to an error message but doesn't say what the error message
is. It gives a pointless link to the home page at http://oca.microsoft.com
saying this is where you can read the error message. It is of course not
true - it's the home page. The site is not browsable - one needs a link to
the exact page. Google found this but again there is not the error message.
Does this page refer to the special intel only BCC 8086 (as in Stop
8086(0,0,0,0) which WinDbg and Symbols have not heard of).
-----------------------------------------------------------------------------------------------
--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/harry_version_2/2005/12/thank_you_and_g.html#comments
=================================================
"rina" <peterholm@xxxxxxxxx> wrote in message
news:ed33qsPJGHA.964@xxxxxxxxxxxxxxxxxxxxxxx
> My MB is Intel 925XEBC2 with integrated RAID.
> I suspect myself too Intel Raid draivers, neccessary for my single SATA
> drive to support NCQ.
> Both times crashes happened I was accessing DVD (RW) drive.
> 1st time when I instereted as CD and typed F5
> 2nd time when I installed Plextools and was looking drive settings,
> without
> changind anything.
>
> Well, can anyone suggest a newsgroup for Intel Mobo's? (with Intel Raid
> :-))
>
>
> "David Candy" <.> wrote in message
> news:OiaYNyOJGHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
> You always get some error #2 in analysis. Don't worry about those.
>
> This is what your first one said
> Probably caused by : iaStor.sys ( iaStor+11973 )
>
> This is an Intel file.
> --
> --------------------------------------------------------------------------------------------------
> Goodbye Web Diary
> http://margokingston.typepad.com/harry_version_2/2005/12/thank_you_and_g.html#comments
> =================================================
> "rina" <peterholm@xxxxxxxxx> wrote in message
> news:OjFClnOJGHA.140@xxxxxxxxxxxxxxxxxxxxxxx
>> My PC suffers from occasional crashes.
>> Hello can anyone read a dump file?
>> I add below 2 dump files, these are rather short as crash has been very
>> quick.
>> Is there something, which gives any directions, what the problem might
>> be?
>>
>> Thanks
>>
>>>>>>>>>>>>>>>>>>>>>>>
>>
>> Microsoft (R) Windows Debugger Version 6.6.0003.5
>> Copyright (c) Microsoft Corporation. All rights reserved.
>>
>>
>> Loading Dump File [E:\Mini012906-01.dmp]
>> Mini Kernel Dump File: Only registers and stack trace are available
>>
>> Symbol search path is: C:\WINDOWS\Symbols
>> Executable search path is:
>> Unable to load image ntoskrnl.exe, Win32 error 2
>> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
>> Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
>> compatible
>> Product: WinNt, suite: TerminalServer SingleUserTS
>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
>> Debug session time: Sun Jan 29 12:18:17.812 2006 (GMT+2)
>> System Uptime: 0 days 0:03:22.980
>> Unable to load image ntoskrnl.exe, Win32 error 2
>> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
>> Loading Kernel Symbols
>> ....................................................................................................................
>>
>> .........................
>> Loading User Symbols
>> Loading unloaded module list
>> ........
>> *******************************************************************************
>> *
>> *
>> * Bugcheck Analysis
>> *
>> *
>> *
>> *******************************************************************************
>>
>> Use !analyze -v to get detailed debugging information.
>>
>> BugCheck 8086, {0, 0, 0, 0}
>>
>> Unable to load image iaStor.sys, Win32 error 2
>> *** WARNING: Unable to verify timestamp for iaStor.sys
>> *** ERROR: Module load completed but symbols could not be loaded for
>> iaStor.sys
>> Probably caused by : iaStor.sys ( iaStor+11973 )
>>
>> Followup: MachineOwner
>> ---------
>>
>> 0: kd> !analyze -v
>> *******************************************************************************
>> *
>> *
>> * Bugcheck Analysis
>> *
>> *
>> *
>> *******************************************************************************
>>
>> Unknown bugcheck code (8086)
>> Unknown bugcheck description
>> Arguments:
>> Arg1: 00000000
>> Arg2: 00000000
>> Arg3: 00000000
>> Arg4: 00000000
>>
>> Debugging Details:
>> ------------------
>>
>>
>> CUSTOMER_CRASH_COUNT: 1
>> Microsoft (R) Windows Debugger Version 6.6.0003.5
>> Copyright (c) Microsoft Corporation. All rights reserved.
>>
>>
>> Loading Dump File [E:\Mini011406-01.dmp]
>> Mini Kernel Dump File: Only registers and stack trace are available
>>
>> Symbol search path is: C:\WINDOWS\Symbols
>> Executable search path is:
>> Unable to load image ntoskrnl.exe, Win32 error 2
>> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
>> Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
>> compatible
>> Product: WinNt, suite: TerminalServer SingleUserTS
>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
>> Debug session time: Sat Jan 14 17:35:00.738 2006 (GMT+2)
>> System Uptime: 3 days 22:27:07.574
>> Unable to load image ntoskrnl.exe, Win32 error 2
>> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
>> Loading Kernel Symbols
>> ....................................................................................................................
>>
>> ...........................
>> Loading User Symbols
>> Loading unloaded module list
>> ..................................................
>> *******************************************************************************
>> *
>> *
>> * Bugcheck Analysis
>> *
>> *
>> *
>> *******************************************************************************
>>
>> Use !analyze -v to get detailed debugging information.
>>
>> BugCheck C2, {7, cd4, 20c0001, 8558a0c8}
>>
>> Probably caused by : ntoskrnl.exe ( nt!PspReaper+25 )
>>
>> Followup: MachineOwner
>> ---------
>>
>> 0: kd> !analyze -v
>> *******************************************************************************
>> *
>> *
>> * Bugcheck Analysis
>> *
>> *
>> *
>> *******************************************************************************
>>
>> BAD_POOL_CALLER (c2)
>> The current thread is making a bad pool request. Typically this is at a
>> bad
>> IRQL level or double freeing the same
>>
>> allocation, etc.
>> Arguments:
>> Arg1: 00000007, Attempt to free pool which was already freed
>> Arg2: 00000cd4, (reserved)
>> Arg3: 020c0001, Memory contents of the pool block
>> Arg4: 8558a0c8, Address of the block of pool being deallocated
>>
>> Debugging Details:
>> ------------------
>>
>>
>> POOL_ADDRESS: 8558a0c8
>>
>> FREED_POOL_TAG: Fatv
>>
>> BUGCHECK_STR: 0xc2_7_Fatv
>>
>> CUSTOMER_CRASH_COUNT: 1
>>
>> DEFAULT_BUCKET_ID: DRIVER_FAULT
>>
>> LAST_CONTROL_TRANSFER: from 00000000 to 804f9c37
>>
>> STACK_TEXT:
>> af112418 00000000 020c0001 8558a0c8 00000000 nt!PspReaper+0x25
>>
>>
>> STACK_COMMAND: kb
>>
>> FOLLOWUP_IP:
>> nt!PspReaper+25
>> 804f9c37 5d pop ebp
>>
>> FAULTING_SOURCE_CODE:
>>
>>
>> SYMBOL_STACK_INDEX: 0
>>
>> FOLLOWUP_NAME: MachineOwner
>>
>> SYMBOL_NAME: nt!PspReaper+25
>>
>> MODULE_NAME: nt
>>
>> IMAGE_NAME: ntoskrnl.exe
>>
>> DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1e
>>
>> FAILURE_BUCKET_ID: 0xc2_7_Fatv_nt!PspReaper+25
>>
>> BUCKET_ID: 0xc2_7_Fatv_nt!PspReaper+25
>>
>> Followup: MachineOwner
>> ---------
>>
>>
>> 2nd___dump____2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2n
>>
>> d___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___du
>>
>> mp2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd_
>>
>> __dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump
>>
>> 2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump2nd___dump
>>
>>
>> Microsoft (R) Windows Debugger Version 6.6.0003.5
>> Copyright (c) Microsoft Corporation. All rights reserved.
>>
>>
>> Loading Dump File [E:\Mini012906-01.dmp]
>> Mini Kernel Dump File: Only registers and stack trace are available
>>
>> Symbol search path is: C:\WINDOWS\Symbols
>> Executable search path is:
>> Unable to load image ntoskrnl.exe, Win32 error 2
>> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
>> Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
>> compatible
>> Product: WinNt, suite: TerminalServer SingleUserTS
>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
>> Debug session time: Sun Jan 29 12:18:17.812 2006 (GMT+2)
>> System Uptime: 0 days 0:03:22.980
>> Unable to load image ntoskrnl.exe, Win32 error 2
>> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
>> Loading Kernel Symbols
>> ....................................................................................................................
>>
>> .........................
>> Loading User Symbols
>> Loading unloaded module list
>> ........
>> *******************************************************************************
>> *
>> *
>> * Bugcheck Analysis
>> *
>> *
>> *
>> *******************************************************************************
>>
>> Use !analyze -v to get detailed debugging information.
>>
>> BugCheck 8086, {0, 0, 0, 0}
>>
>> Unable to load image iaStor.sys, Win32 error 2
>> *** WARNING: Unable to verify timestamp for iaStor.sys
>> *** ERROR: Module load completed but symbols could not be loaded for
>> iaStor.sys
>> Probably caused by : iaStor.sys ( iaStor+11973 )
>>
>> Followup: MachineOwner
>> ---------
>>
>> 0: kd> !analyze -v
>> *******************************************************************************
>> *
>> *
>> * Bugcheck Analysis
>> *
>> *
>> *
>> *******************************************************************************
>>
>> Unknown bugcheck code (8086)
>> Unknown bugcheck description
>> Arguments:
>> Arg1: 00000000
>> Arg2: 00000000
>> Arg3: 00000000
>> Arg4: 00000000
>>
>> Debugging Details:
>> ------------------
>>
>>
>> CUSTOMER_CRASH_COUNT: 1
>>
>> DEFAULT_BUCKET_ID: DRIVER_FAULT
>>
>> BUGCHECK_STR: 0x8086
>>
>> LAST_CONTROL_TRANSFER: from 00000000 to 804f9c12
>>
>> SYMBOL_ON_RAW_STACK: 1
>>
>> STACK_TEXT:
>> f7ad8c5c 00000000 00000000 00000000 00000000 nt!PspReaper
>>
>>
>> STACK_COMMAND: dds @$csp ; kb
>>
>> FOLLOWUP_IP:
>> iaStor+11973
>> f7446973 ?? ???
>>
>> FAULTING_SOURCE_CODE:
>>
>>
>> FOLLOWUP_NAME: MachineOwner
>>
>> SYMBOL_NAME: iaStor+11973
>>
>> MODULE_NAME: iaStor
>>
>> IMAGE_NAME: iaStor.sys
>>
>> DEBUG_FLR_IMAGE_TIMESTAMP: 40608c73
>>
>> FAILURE_BUCKET_ID: 0x8086_iaStor+11973
>>
>> BUCKET_ID: 0x8086_iaStor+11973
>>
>> Followup: MachineOwner
>> ---------
>>
>>
>>
>
>
.
- References:
- XP crashes, dmp files added.
- From: rina
- Re: XP crashes, dmp files added.
- From: rina
- XP crashes, dmp files added.
- Prev by Date: Re: Services - start failure
- Next by Date: Re: how to make one more drive on my PC
- Previous by thread: Re: XP crashes, dmp files added.
- Next by thread: Re: Winsoftware creating havoc. please help!
- Index(es):
Relevant Pages
|
