View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001036SpeedFanOtherpublic2007-12-09 13:312007-12-09 13:34
Reportermdcobra Assigned Toalfredo  
PrioritynormalSeveritycrashReproducibilityrandom
Status assignedResolutionopen 
PlatformX86OSWindows XP Pro 32bitOS VersionSP2
Product Version4.33 
Summary0001036: "random" BSOD's
DescriptionToday I was investigating why my system is unstable.
So I was using WinDbg to go through my minidumps, and discovered Speedfan might be causing the problem. I think I have about 3 dumps. I will put the output from WinDbg in additional comments.
Steps To ReproduceThe BSOD's seem random, so it is difficult, but I do get them frequently.
Additional InformationCan you recommend a workaround, i.e. using 4.32?
1 crash seems to be the same as bug 0001022.
TagsNo tags attached.
Motherboard Model
Video Card Model2*7900 GT in SLI (1 Sparcle and 1 Leadtek)

Activities

2007-12-09 13:31

 

SpeedFanReport.TXT (59,001 bytes)   

mdcobra

2007-12-09 13:32

reporter   ~0003208

Probably caused by : speedfan.sys ( speedfan+d00 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf8c2396, The address that the exception occurred at
Arg3: b4716514, Trap Frame
Arg4: 00000000

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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4516880f

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
win32k+c2396
bf8c2396 668b38 mov di,word ptr [eax]

TRAP_FRAME: b4716514 -- (.trap 0xffffffffb4716514)
ErrCode = 00000000
eax=4000005a ebx=02f20040 ecx=02f20040 edx=00000008 esi=00000002 edi=4000005a
eip=bf8c2396 esp=b4716588 ebp=b4716594 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k+0xc2396:
bf8c2396 668b38 mov di,word ptr [eax] ds:0023:4000005a=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf836fdf to bf8c2396

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b4716594 bf836fdf 02f20040 4000005a 000005d8 win32k+0xc2396
b47165b8 bf836ce0 00000166 b471681c e2d35dd0 win32k+0x36fdf
b47167cc bf80a517 e2d35de0 00000000 00000000 win32k+0x36ce0
b4716860 805409ac e2d35dd0 e1a7f418 e26c1350 win32k+0xa517
b4716894 7c90eb94 badb0d00 0012f078 00000000 nt+0x699ac
b4716898 badb0d00 0012f078 00000000 00000000 0x7c90eb94
b471689c 0012f078 00000000 00000000 00000000 speedfan+0xd00
b47168a0 00000000 00000000 00000000 00000000 0x12f078


STACK_COMMAND: kb

FOLLOWUP_IP:
speedfan+d00
badb0d00 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: speedfan+d00

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: speedfan

IMAGE_NAME: speedfan.sys

BUCKET_ID: WRONG_SYMBOLS

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

mdcobra

2007-12-09 13:33

reporter   ~0003209

Probably caused by : speedfan.sys ( speedfan+d00 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: f0ff1f2c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80510d95, address which referenced memory

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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4516880f

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 f0ff1f2c

CURRENT_IRQL: 2

FAULTING_IP:
nt+39d95
80510d95 8b460c mov eax,dword ptr [esi+0Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 805aee11 to 80510d95

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b46d5c14 805aee11 776ad001 88dfada0 007ffff8 nt+0x39d95
b46d5c34 8051295d 88dfada0 88e14a5c 88dfada0 nt+0xd7e11
b46d5c68 805d114b 00dfada0 892fd890 40010004 nt+0x3b95d
b46d5cf0 805d122f 40010004 b46d5d4c 804fef8d nt+0xfa14b
b46d5cfc 804fef8d 892fd890 b46d5d48 b46d5d3c nt+0xfa22f
b46d5d4c 80540b9e 00000001 00000000 b46d5d64 nt+0x27f8d
b46d5d64 7c90eb94 badb0d00 0007f460 00000000 nt+0x69b9e
b46d5d68 badb0d00 0007f460 00000000 00000000 0x7c90eb94
b46d5d6c 0007f460 00000000 00000000 00000000 speedfan+0xd00
b46d5d70 00000000 00000000 00000000 00000000 0x7f460


STACK_COMMAND: kb

FOLLOWUP_IP:
speedfan+d00
badb0d00 ?? ???

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: speedfan+d00

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: speedfan

IMAGE_NAME: speedfan.sys

BUCKET_ID: WRONG_SYMBOLS

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

mdcobra

2007-12-09 13:34

reporter   ~0003210

Probably caused by : hardware ( speedfan+d00 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: b4f48278, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf8cfa46, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 b4f48278

FAULTING_IP:
win32k+cfa46
bf8cfa46 8b8da8298721 mov ecx,dword ptr [ebp+218729A8h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

MISALIGNED_IP:
win32k+cfa46
bf8cfa46 8b8da8298721 mov ecx,dword ptr [ebp+218729A8h]

LAST_CONTROL_TRANSFER: from 805409ac to bf8cfa46

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
936d58d0 805409ac 0004037e 0000000e 00000000 win32k+0xcfa46
936d58f4 7c90eb94 badb0d00 0012ebec 00000000 nt+0x699ac
936d58f8 badb0d00 0012ebec 00000000 00000000 0x7c90eb94
936d58fc 0012ebec 00000000 00000000 00000001 speedfan+0xd00
936d5900 00000000 00000000 00000001 00000038 0x12ebec


STACK_COMMAND: kb

FOLLOWUP_IP:
speedfan+d00
badb0d00 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: speedfan+d00

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

Issue History

Date Modified Username Field Change
2007-12-09 13:31 mdcobra New Issue
2007-12-09 13:31 mdcobra Status new => assigned
2007-12-09 13:31 mdcobra Assigned To => alfredo
2007-12-09 13:31 mdcobra File Added: SpeedFanReport.TXT
2007-12-09 13:31 mdcobra Video Card Model => 2*7900 GT in SLI (1 Sparcle and 1 Leadtek)
2007-12-09 13:32 mdcobra Note Added: 0003208
2007-12-09 13:33 mdcobra Note Added: 0003209
2007-12-09 13:34 mdcobra Note Added: 0003210