Hello,
I have the same problem with the sensor test of real temp 3.4. BSOD or prime95 was closed by winDgb
I test realtemp 3.4 with prime95v259 and v2511. BSOD or winDgb closed
***************************************************************
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\WINDOWS\Minidump\Mini120609-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*DownstreamStore*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Dec 6 13:19:45.062 2009 (GMT+1)
System Uptime: 0 days 0:07:33.750
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, f783f68c, aa11875c, 0}
Probably caused by : watchdog.sys ( watchdog!WdExitMonitoredSection+10 )
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: f783f68c, The address that the exception occurred at
Arg3: aa11875c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
FAULTING_IP:
watchdog!WdExitMonitoredSection+10
f783f68c 80be9c00000000 cmp byte ptr [esi+9Ch],0
TRAP_FRAME: aa11875c -- (.trap 0xffffffffaa11875c)
ErrCode = 00000000
eax=000b8659 ebx=7ffdf284 ecx=89ff6cf8 edx=bbc00000 esi=31383139 edi=89ff6d24
eip=f783f68c esp=aa1187d0 ebp=aa118924 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
watchdog!WdExitMonitoredSection+0x10:
f783f68c 80be9c00000000 cmp byte ptr [esi+9Ch],0 ds:0023:313831d5=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: RealTemp.exe
LAST_CONTROL_TRANSFER: from bf80440e to f783f68c
STACK_TEXT:
aa1187d4 bf80440e 7ffdf000 bf80c3f7 8055c6d0 watchdog!WdExitMonitoredSection+0x10
aa1187dc bf80c3f7 8055c6d0 89da8828 00000003 win32k!DEVLOCKOBJ::vDestructor+0x2e
aa118924 805415fd 0000000d 0012f26c 0012f2a8 win32k!NtGdiFlushUserBatch+0x89a
aa118950 bf836a2d 00000000 aa118c38 00000000 nt!KiFastCallEntry+0xcd
aa118c48 bf813d96 00000002 aa118c8c 00000018 win32k!EngCopyBits+0x555
aa118ccc bf8035a3 bbebb7d0 0000000f 00000000 win32k!SfnDWORD+0xa8
aa118d0c bf80ec5b 773c3dcf aa118d64 0012f510 win32k!xxxDispatchMessage+0x1dc
aa118d58 8054162c 00419534 0012f548 7c91e514 win32k!NtUserDispatchMessage+0x39
aa118d58 7c91e514 00419534 0012f548 7c91e514 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f548 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
watchdog!WdExitMonitoredSection+10
f783f68c 80be9c00000000 cmp byte ptr [esi+9Ch],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: watchdog!WdExitMonitoredSection+10
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: watchdog
IMAGE_NAME: watchdog.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 480254ab
FAILURE_BUCKET_ID: 0x8E_watchdog!WdExitMonitoredSection+10
BUCKET_ID: 0x8E_watchdog!WdExitMonitoredSection+10
Followup: MachineOwner
******************************************************************
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\WINDOWS\Minidump\Mini120609-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
***************************************************************
or prime95 was closed by winDgb.
*****************************
But strange is, with realtemp v 3.00 and prime95v259 i passed the sensor test.
Maybe this helpful.
CU