• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Sensor Test Crash

Joined
Nov 24, 2009
Messages
5 (0.00/day)
Likes
0
#26
FWIW, I tried the sensor test with my system overclocked to 3.2 GHz. The results were the same. I also tried playing a CD while running the sensor test and when the system locked up (as before), the music stopped. Just thought you would like to know.
 
Joined
Nov 24, 2009
Messages
5 (0.00/day)
Likes
0
#27
Another piece of information for you ...

I went to the settings tab and played around with the clock modulation. All settings worked OK except for 12.5%. As soon as I clicked Apply with the 12.5% setting, the computer locked up as before.
 

unclewebb

RealTemp Author
Joined
Jun 1, 2008
Messages
1,147 (0.32/day)
Likes
689
#28
All I can say is that if you are having problems with the sensor test locking up then you shouldn't use it. I've been unable to recreate this problem on any of the computers I've tried it on so at the moment, I'm not able to come up with a solution.

Your testing and w1ldm4n's testing has helped me understand exactly what's causing the problem but I haven't been able to figure out why this is a problem on some computers but not others and why this problem magically disappeared for w1ldm4n.

Sometime in the future I will look into this issue further and try to find a different way of doing things that might be more compatible.

Edit: Thanks for that last test. The Intel documentation says that you should be able to set a Clock Modulation value of 12.5%. I can set that value on all of my computers without any lock ups. I might have to add an option to that test to prevent it using that setting if a user is having problems. This seems more like a problem with your CPU. What stepping is your E8400? I have an E8400 C0 that works fine.
 

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#30
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.:rockout:
CU
 

unclewebb

RealTemp Author
Joined
Jun 1, 2008
Messages
1,147 (0.32/day)
Likes
689
#31
ERLOESER: Thanks for posting that. This is a very strange bug that I don't have a solution for. OceanBreeze made it seem like a bug within the CPU. You could try your CPU too by going into the RealTemp Settings window and try to force different Clock Modulation values. It's the last 12.5% setting that was causing him troubles. Can you enable and disable that one without your computer crashing?

I haven't made any changes to how this test operates for a long time which is why I can't understand why old versions of RealTemp work for you but the newer one chokes on this test. If I could repeat this bug it would be easy to fix but the test and all of the Clock Modulation settings work fine on my computer.

Here is the latest version of RealTemp.
http://www.sendspace.com/file/u79b5p

I haven't changed anything since 3.40 so it's very likely the bug is still there. :(
 

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#32
Well
with realtemp 3.4 and prime95 v259 and setting in realtemp Clock Modulation 12.5 % i passed the sensor test in xp sp 3 32 bit Movement sensor core #0=1 core#1=3
CPU load. 100%, 88,4%,77,2%,65,7%,54,7%,46%, 39,1%, 30,2%,11,8%, 11,6%
Setting in realtemp 3 and prime95 v259 are with no Clock Modulation
also passed the sensor test. in xp sp3 32 bit

To realtemp 3.4 with prime 95 v259 with disable Clock Modulation
prime95 v259 was closed by winDgb in Test 6 xp sp3 bit 32.

Vista 64 bit not testet.

To my system

E7200 (Revision M0 Stepping6) @ 370 a Multi 9,5 3515 MHZ. RAM G.Skill F2- 8000 CL5 @ 493 MHZ (2x2GB). ratio 3:4. CPL 10.
BIOS settings MB bios version. 1501 Asus p5q-pro vCore 1,23125. CPU PLL 1,5, DRAMv 2,02. vNB 1,18. VTT 1,22. rest standart settings in bios.
CPU Margin Enhancement optimize (was default)

VID CPU-Z load 1,1625 also realtemp. LLC disable. CPU-Z idle vCore 1,2. CPU-Z load intelburntest 1,174V. prime95 load 1,184V

Other problem in xs benchmark i get only 170 point in xp sp3 realtemp v3.4 in vista ultimate 64bit.169 points. In realtemp v3 i have in xp sp3 over 1000 points???
System is prime95 inplace custom stable, Linx, intelburn on Vita 64 bit. Goldmemory no errors.

Im testing CPU Margin Enhancement compatible at the moment,
I think the temps looks better (CPU and MB in idle, Core temps are the same) i will run a full custom test prime95 in place.

BTW anyone knows what vin1 and vin3 means on a MB P5Q-PRO in the CPUID HWmonitor
Vin1 is 1,66. Vin has a min. of 1,11V and a max. of 1,15V Value on prime95 1,14 V
Maybe CPU Margin Enhancement is the problem.
But i cant find a good explain of ASUS CPU Margin Enhancement!
 
Last edited:

unclewebb

RealTemp Author
Joined
Jun 1, 2008
Messages
1,147 (0.32/day)
Likes
689
#33
If you manually enable Clock Modulation, this will slow your computer to a crawl and will reduce your benchmark scores. I just downloaded 3.40 from the TPU site and in Vista 32 bit it is working OK.



I will try this test in a few more OS versions when I get the chance.

The Cool Down Test does not crash on any of the CPUs I've tested it on. For some reason, on some CPUs, it crashes when the Clock Modulation gets turned off. I've followed the Intel documentation but I'll see if I can change anything in my code to get this working properly on your computer.

Did you try RealTemp 3.50 from the link I posted above?
 

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#34
Thanks unclewebb

I will test realtemp 3.5 tomorrow first with xp and modulation off, i hope i get no BSOD and windgb will not closed. When i passed it (no BSOD), i will test it in vista 64bit. I hate BSOD :cry:. At the moment i cant test realtemp 3.5 prime95 is running im testing CPU Margin enhancement at compatible. with optimize system is stable. 4 hours to go

BTW do you know something about CPU Margin enhancement from ASUS?
I know only optimize is for dual cores. performence for quad cores and compatible for some 45nm to raise the FSB. But i dont know what is the best setting for my E7200 compatible or optimize. At the moment i see no difference. only that i have a better idle temp MB only max 32°C in compatible in optimize i ve 34 °C. and in load all the time 31 or 32 °C.
 
Last edited:
Joined
Dec 6, 2005
Messages
10,108 (2.27/day)
Likes
3,992
Location
Manchester, NH
System Name Working on it ;)
Processor I7-4790K
Motherboard MSI Z97 U3 Plus
Cooling Be Quiet Pure Rock Air
Memory 16GB 4x4 G.Skill CAS9 2133 Sniper
Video Card(s) GIGABYTE AORUS 1070 Ti 2040/2400 (GPU/MEM OC)
Storage Samsung EVO 500GB / 8 Different WDs / QNAP TS-253 8GB NAS with 2x2Tb WD Black
Display(s) 34" LG 34CB88-P 21:9 Curved UltraWide QHD (3440*1440)
Case Rosewill Challenger
Audio Device(s) Onboard + HD HDMI
Power Supply Corsair HX750 (love it)
Mouse Logitech G5
Keyboard Corsair Strafe RGB & G610 Orion Red
Software Win 10 upgraded from Win 7 Pro
#35
I am running Windows 7 Professional (64 bit) and my computer crashes when I try to run the sensor test.
Details:
E8400 (not overclocked)
My Idle temps are supposedly around 45-50c

When I click sensor test it opens the box, I select Prime95 and let the test run. Everything seems to be going fine until the idle test when it says 'stopping Prime95'. At this point, my entire computer freezes, nothing on the display changes at all. Numbers stop changing, even the second hand on the windows clock gadget on the desktop stop, no a single pixel on my display will change. I have to use the hardware reset button on my computer and then everything boots normally.

Why is this happening, and what can I do to fix it.
I tried the 32 and 64 bit versions of Prime95, is there a 64 bit realtemp?

P.S. I've heard around the internet that Tjmax for an E8400 is 100c, is this correct?
Latest version here and I get a windows must close application error every time I push that button...

X38 Maximus Formula, E8700, running at stock.
 

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#37
I testet realtemp 3.5 with prime95v2511 on Vista 64bit. prime95 Application was closed at test 5 same result in xp 32bit.
XS bench score realtemp 3.5 1174
 

unclewebb

RealTemp Author
Joined
Jun 1, 2008
Messages
1,147 (0.32/day)
Likes
689
#38
To me it doesn't sound like your computer is 100% stable. Have you tried running a LinX test? It's a little more severe than running Prime95 and might show you how stable your CPU really is. Set it so it tests as much of your memory as possible.

You can download it and read about it here:

http://www.xtremesystems.org/forums/showthread.php?t=201670

If that passes try running Prime95 in blend mode and see how that goes.
 

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#39
@unclewebb, if u mean me with linx.
I told u that my system is linx 0.6.4.Problem size 20325, MIB 3168, run 100 and intelburntest (20 runs)stable with full memory (Physical Usage 90,6 % Process Explorer) at vista 64bit.
But why to test prime95 blend (it is more or less only a ram test btw i passed prime blend 24h) i passed goldmemory 2 passes no errors and memtest 86 4 passes no errors.
PLZ look again in realtemp 3 and realtemp 3.4. because realtemp works for me with no clock modulation. It must be a different inside the script.

THX
Intel(R) LINPACK 64-bit data - LinX 0.6.4

Current date/time: Tue Dec 22 09:40:39 2009

CPU frequency: 3.515 GHz
Number of CPUs: 2
Number of threads: 2

Parameters are set to:

Number of tests : 1
Number of equations to solve (problem size) : 20325
Leading dimension of array : 20328
Number of trials to run : 100
Data alignment value (in Kbytes) : 4

Maximum memory requested that can be used = 3305743456, at the size = 20325

============= Timing linear equation system solver =================

Size LDA Align. Time(s) GFlops Residual Residual(norm)
20325 20328 4 247.181 22.6490 3.746651e-010 3.216981e-002
20325 20328 4 246.205 22.7388 3.746651e-010 3.216981e-002
20325 20328 4 245.729 22.7829 3.746651e-010 3.216981e-002
20325 20328 4 245.567 22.7979 3.746651e-010 3.216981e-002
20325 20328 4 246.679 22.6952 3.746651e-010 3.216981e-002
20325 20328 4 245.776 22.7785 3.746651e-010 3.216981e-002
20325 20328 4 245.671 22.7882 3.746651e-010 3.216981e-002
20325 20328 4 245.363 22.8168 3.746651e-010 3.216981e-002
20325 20328 4 245.988 22.7588 3.746651e-010 3.216981e-002
20325 20328 4 248.219 22.5543 3.746651e-010 3.216981e-002
20325 20328 4 245.515 22.8027 3.746651e-010 3.216981e-002
20325 20328 4 246.143 22.7445 3.746651e-010 3.216981e-002
20325 20328 4 245.715 22.7841 3.746651e-010 3.216981e-002
20325 20328 4 246.474 22.7140 3.746651e-010 3.216981e-002
20325 20328 4 246.157 22.7432 3.746651e-010 3.216981e-002
20325 20328 4 245.568 22.7978 3.746651e-010 3.216981e-002
20325 20328 4 245.360 22.8171 3.746651e-010 3.216981e-002
20325 20328 4 246.030 22.7549 3.746651e-010 3.216981e-002
20325 20328 4 252.555 22.1671 3.746651e-010 3.216981e-002
20325 20328 4 249.199 22.4656 3.746651e-010 3.216981e-002
20325 20328 4 246.192 22.7400 3.746651e-010 3.216981e-002
20325 20328 4 246.192 22.7400 3.746651e-010 3.216981e-002
20325 20328 4 245.736 22.7822 3.746651e-010 3.216981e-002
20325 20328 4 248.279 22.5489 3.746651e-010 3.216981e-002
20325 20328 4 251.589 22.2522 3.746651e-010 3.216981e-002
20325 20328 4 245.770 22.7790 3.746651e-010 3.216981e-002
20325 20328 4 246.274 22.7324 3.746651e-010 3.216981e-002
20325 20328 4 246.192 22.7400 3.746651e-010 3.216981e-002
20325 20328 4 245.847 22.7719 3.746651e-010 3.216981e-002
20325 20328 4 246.257 22.7340 3.746651e-010 3.216981e-002
20325 20328 4 246.566 22.7055 3.746651e-010 3.216981e-002
20325 20328 4 246.217 22.7377 3.746651e-010 3.216981e-002
20325 20328 4 246.349 22.7256 3.746651e-010 3.216981e-002
20325 20328 4 246.619 22.7007 3.746651e-010 3.216981e-002
20325 20328 4 246.360 22.7245 3.746651e-010 3.216981e-002
20325 20328 4 246.332 22.7271 3.746651e-010 3.216981e-002
20325 20328 4 247.224 22.6451 3.746651e-010 3.216981e-002
20325 20328 4 247.004 22.6653 3.746651e-010 3.216981e-002
20325 20328 4 248.041 22.5705 3.746651e-010 3.216981e-002
20325 20328 4 248.260 22.5506 3.746651e-010 3.216981e-002
20325 20328 4 247.102 22.6562 3.746651e-010 3.216981e-002
20325 20328 4 247.111 22.6554 3.746651e-010 3.216981e-002
20325 20328 4 247.207 22.6466 3.746651e-010 3.216981e-002
20325 20328 4 248.280 22.5487 3.746651e-010 3.216981e-002
20325 20328 4 253.530 22.0818 3.746651e-010 3.216981e-002
20325 20328 4 246.945 22.6707 3.746651e-010 3.216981e-002
20325 20328 4 246.608 22.7017 3.746651e-010 3.216981e-002
20325 20328 4 247.522 22.6179 3.746651e-010 3.216981e-002
20325 20328 4 247.493 22.6205 3.746651e-010 3.216981e-002
20325 20328 4 246.654 22.6974 3.746651e-010 3.216981e-002
20325 20328 4 247.061 22.6600 3.746651e-010 3.216981e-002
20325 20328 4 247.087 22.6577 3.746651e-010 3.216981e-002
20325 20328 4 246.547 22.7072 3.746651e-010 3.216981e-002
20325 20328 4 247.537 22.6165 3.746651e-010 3.216981e-002
20325 20328 4 247.122 22.6545 3.746651e-010 3.216981e-002
20325 20328 4 246.839 22.6804 3.746651e-010 3.216981e-002
20325 20328 4 247.479 22.6217 3.746651e-010 3.216981e-002
20325 20328 4 246.997 22.6659 3.746651e-010 3.216981e-002
20325 20328 4 246.518 22.7100 3.746651e-010 3.216981e-002
20325 20328 4 246.815 22.6826 3.746651e-010 3.216981e-002
20325 20328 4 246.792 22.6847 3.746651e-010 3.216981e-002
20325 20328 4 246.953 22.6700 3.746651e-010 3.216981e-002
20325 20328 4 247.000 22.6656 3.746651e-010 3.216981e-002
20325 20328 4 247.123 22.6544 3.746651e-010 3.216981e-002
20325 20328 4 246.645 22.6982 3.746651e-010 3.216981e-002
20325 20328 4 247.366 22.6321 3.746651e-010 3.216981e-002
20325 20328 4 247.405 22.6285 3.746651e-010 3.216981e-002
20325 20328 4 247.183 22.6489 3.746651e-010 3.216981e-002
20325 20328 4 247.402 22.6288 3.746651e-010 3.216981e-002
20325 20328 4 246.977 22.6677 3.746651e-010 3.216981e-002
20325 20328 4 246.382 22.7224 3.746651e-010 3.216981e-002
20325 20328 4 246.927 22.6724 3.746651e-010 3.216981e-002
20325 20328 4 246.733 22.6901 3.746651e-010 3.216981e-002
20325 20328 4 246.352 22.7252 3.746651e-010 3.216981e-002
20325 20328 4 246.627 22.6999 3.746651e-010 3.216981e-002
20325 20328 4 247.012 22.6645 3.746651e-010 3.216981e-002
20325 20328 4 246.567 22.7054 3.746651e-010 3.216981e-002
20325 20328 4 247.392 22.6297 3.746651e-010 3.216981e-002
20325 20328 4 247.085 22.6578 3.746651e-010 3.216981e-002
20325 20328 4 246.626 22.7000 3.746651e-010 3.216981e-002
20325 20328 4 246.929 22.6721 3.746651e-010 3.216981e-002
20325 20328 4 246.618 22.7007 3.746651e-010 3.216981e-002
20325 20328 4 246.399 22.7209 3.746651e-010 3.216981e-002
20325 20328 4 246.728 22.6906 3.746651e-010 3.216981e-002
20325 20328 4 247.307 22.6375 3.746651e-010 3.216981e-002
20325 20328 4 246.681 22.6950 3.746651e-010 3.216981e-002
20325 20328 4 247.044 22.6616 3.746651e-010 3.216981e-002
20325 20328 4 246.733 22.6902 3.746651e-010 3.216981e-002
20325 20328 4 246.573 22.7049 3.746651e-010 3.216981e-002
20325 20328 4 246.657 22.6971 3.746651e-010 3.216981e-002
20325 20328 4 247.008 22.6649 3.746651e-010 3.216981e-002
20325 20328 4 246.349 22.7255 3.746651e-010 3.216981e-002
20325 20328 4 246.589 22.7034 3.746651e-010 3.216981e-002
20325 20328 4 246.617 22.7009 3.746651e-010 3.216981e-002
20325 20328 4 246.427 22.7183 3.746651e-010 3.216981e-002
20325 20328 4 247.040 22.6620 3.746651e-010 3.216981e-002
20325 20328 4 247.084 22.6579 3.746651e-010 3.216981e-002
20325 20328 4 246.638 22.6988 3.746651e-010 3.216981e-002
20325 20328 4 247.252 22.6425 3.746651e-010 3.216981e-002
20325 20328 4 247.216 22.6458 3.746651e-010 3.216981e-002

Performance Summary (GFlops)

Size LDA Align. Average Maximal
20325 20328 4 22.6741 22.8171

End of tests
 
Last edited:

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#40
I testet realtemp 3.5 with prime95v2511 on Vista 64bit. prime95 Application was closed at test 5 .
Problemsignatur
Problemereignisame: APPCRASH
Anwendungsname: prime95.exe
Anwendungsversion: 25.11.1.0
Anwendungszeitstempel: 4a5af88b
Fehlermodulname: prime95.exe
Fehlermodulversion: 25.11.1.0
Fehlermodulzeitstempel: 4a5af88b
Ausnahmecode: c0000005
Ausnahmeoffset: 00000000001809ff
Betriebsystemversion: 6.0.6002.2.2.0.256.1
Gebietsschema-ID: 1031
Zusatzinformation 1: 2926
Zusatzinformation 2: 47c4a882266fd209c30ce38155194792
Zusatzinformation 3: 4181
Zusatzinformation 4: f1b4b2a622c4dc463af4d774f81de98c
 

unclewebb

RealTemp Author
Joined
Jun 1, 2008
Messages
1,147 (0.32/day)
Likes
689
#41
The RealTemp cool down test automatically adjusts clock modulation during the test from 100% to 12.5% in steps of 12.5%. When it doesn't need the Prime95 load any more, it shuts that process down. RealTemp was used to start Prime95 so I've never had a problem with letting RealTemp close down Prime95. Test 5 should correspond to a clock modulation setting of 50%.

It looks like Prime95 is not stable on your CPU when the Clock Modulation feature of the CPU is being used. At test 5, RealTemp is not doing anything out of the ordinary. It's monitoring temperatures as Prime is allowed to run. It's no different than tests 2, 3, 4 or tests 6 or 7. It's just using different modulation settings for each test.

I can't remember off hand any significant changes I've made to this section of code. I will definitely have a closer look at it. I'm as interested as you as finding out what's going on but I can' think of anything off hand and not once have I had this problem on my E8400 in any operating system.

I wrote a new tool called ThrottleStop that lets you play with or monitor the clock modulation setting. While running Prime95 Small FFTs like RealTemp does, you can use this tool to easily change the Clock Modulation setting. RealTemp 3.50 should be able to monitor for any clock modulation changes and will display that info in the Thermal Status area. You could also run two instances of ThrottleStop; one to adjust clock modulation and the other to monitor clock modulation. You can leave its other features since they are mostly designed to prevent Dell laptops from throttling and slowing down.

Can you start up Prime95 Small FFTs like RealTemp does and then try to run your computer at various clock modulation settings? You can also use RM Clock to adjust clock modulation on the fly. It is called ODCM which stands for on demand clock modulation. I appreciate your help with this.
 
Last edited:

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#42
Thx unclewebb,:respect:

i tested again realtemp 3 with prime95 2511 in xp sp3 32bit with default settings in realtemp.
prime95 was closed normal by realtemp after Test 8. I passed the test
movement sensor Core0 9, Core1 14
CPU load
98,9 %, 87,3%, 75,7 %, 63,5%, 54,7%, 44,5%, 36,9% 27,5%, 2,1% idle
but realtemp 3,4 works only with clock modulation 12,5 % for me ( I tested only 12,5).

You say there is no difference inside script of realtemp 3 and 3.4. I say a difference must be inside maybe a space more. When realtemp 3 works for me also realtemp 3,4 must work for me.:banghead:
The difference what i saw in realtemp 3 to realtemp 3,4. realtemp 3 show 5 °C lower temps. but this temps are wrong. realtemp 3,4 show me the correct temps.


PLZ give me some more info's about clock modulation maybe i will find a solution.
 
Joined
Sep 7, 2008
Messages
329 (0.10/day)
Likes
88
Location
Canberra Australia
Processor i5 750 4.2ghz 1.4V
Motherboard Gigabyte P55-UD4P
Cooling Corsair H70
Memory 2X2G Gskill @2140 8-11-8-28-1T
Video Card(s) 2xGainward Phantom3 570@860/4200
Storage 2xWD 500G AAKS Raid0 + 2XWD 1T Green in Raid0
Display(s) 24" HP w2408h+23" HP w2338h
Case SilverStone Raven2E-B
Audio Device(s) onboard for now
Power Supply Antec 1000W Truepower quattro
Software Win7 Ultimate 64bit
#43
Haven't read through all the posts in this thread but the sensor tests do crash while changing CPU clock's even with a 100% stable CPU, i run my i5 with 1.35v@ 4gig and it was stable with every single stress tests I can find, but running it with the same voltage @ just 3.2g, sensor test will still sometimes crash while changing the clocks, yes, it only crash while setting a lower multiplier.
 

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#44
Problem solved :toast:

the problem was the vcore.

Okay how i found a solution.
With vCore 1,23125 i passed the sensor test in realtemp 3 xp sp2 32bit.
system was prime95 custom inplace,super pi and linx 100 runs full memory in Vista 64 bit stable.

Okay i tested realtemp 3 again in Vista 64 bit again. Core1 hardware failture in Test 5 oh thats means Vcore.
Good that i have 2 OS. Vista 64bit is top for overclocking needs so much Vcore.:laugh:

I changed the Vcore in my Bios to 1,24372 (new idle CPU-Z 1,216 load prime95 CPU-Z 1,92 or 1,84V) LLC disable
to xp sp3 32 bit passed Cool and down in Version 3 and 3,4
I also passed Realtemp 3 and 3,4 with prime95 2511 64 bit in Vista 64 bit. prime95 was closed normal after Test 8.
!!!Vcore was the problem!!!! realtemp setting in xp vista default

Thx alot unclewebb u have create the ultimate final stable test. :rockout: LoL Cool and Down is harder as linx and prime95 custom inplace:respect:

last questions. Sensor Movement Core0 9 Core1 13 normal ??? idle Vocre 1,216 too high?

Merry Xmas to all :nutkick::respect:
 
Last edited:

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#45
Haven't read through all the posts in this thread but the sensor tests do crash while changing CPU clock's even with a 100% stable CPU, i run my i5 with 1.35v@ 4gig and it was stable with every single stress tests I can find, but running it with the same voltage @ just 3.2g, sensor test will still sometimes crash while changing the clocks, yes, it only crash while setting a lower multiplier.
Forget Linx and prime95 -->Cool and Down ist the new Vcore killer
BTW 448k inplace is vcore killer in prime95. You need more Vcore
 
Last edited:

unclewebb

RealTemp Author
Joined
Jun 1, 2008
Messages
1,147 (0.32/day)
Likes
689
#46
You had me worried. That would be funny if the RealTemp Cool Down Test became the ultimate stability test. :D

All RealTemp does is it changes the Clock Modulation settings to all of the supported values from 100% down to 12.5% which any Pentium 4 or later CPU should be able to handle without crashing.

I used to think that maybe a 10 minute test was too long but it's better than 24 hours of Prime or 100 rounds of LinX testing and a lot less stressful too.

Thanks you ERLOESER for finally figuring this out. You're not the first user that thought this test had bugs. Most of them just gave up without ever trying to find out why. Next time I hear about a user with this problem I will point him to all of the testing you have done. Your hard work will be useful for other users with the same problem.

I've been running my E8400 for the last year or two at 1.40 volts so 1.216 volts is definitely not too high. I'd probably give it some more voltage and see what it can really do.

These temperature sensors have a lot of issues. Sensor movement of 9 and 13 is normal. 9 and 9 or 13 and 13 would be nice but that rarely happens. Enjoy your computer and don't worry too much about the sensors or what temperature your CPU is running at. As long as you're stable then it's good. Now you are 101% stable. :toast:
 

ERLOESER

New Member
Joined
Dec 19, 2009
Messages
10 (0.00/day)
Likes
0
#47
Thx unclewebb merry xmas to you
My coretemps in prime95 max. 58°C in intelburn 68°C.
I know it is top
Sorry. i need low temps because im a Silent overclocker noisy part in my system is my Samsung HD. I love Silent fans:nutkick:
 
Joined
Sep 8, 2005
Messages
803 (0.18/day)
Likes
463
Location
Romania
Processor i5-2500K
Motherboard ASRock P67 Extreme4
Cooling Ninja 3 fanless
Memory Corsair 4GB DDR3 1600MHz CL9 XMS3 rev. A
Video Card(s) MSI GeForce GTX 1060 GAMING X 6GB
Storage Intel 535 Series 120GB + WD 6400AAKS
Display(s) Benq EW2420
Case Antec P182
Audio Device(s) Xonar D1
Power Supply Antec Signature 650
Software Win 10
#48
Joined
Mar 12, 2010
Messages
5 (0.00/day)
Likes
0
#49
Unclewebb -

First, thanks for making such a great program! Second, sorry for resurrecting a dead thread :(

I am experiencing the same issues, but was able to pass (AKA windows not freeze) after disabling any power-saving/throttling tools in the bios (C1E state, CPU EIST, etc...)my ram is stable, i've run prime into the ground but if I have those bios options enabled it hangs immediately upon shutting down the prime95 test.

I have a gigabyte ep45-ud3p, 8 gigs of G.Skill 1066 Ram & Intel Q9650 running Windows 7 X64.

I just wanted to bring these findings up since I didn't see them mentioned in the threads before or when I search on google.

Any feedback would be greatly appreciated!
 
Last edited:

unclewebb

RealTemp Author
Joined
Jun 1, 2008
Messages
1,147 (0.32/day)
Likes
689
#50
ERLOESER found out that he needed a slight boost in vcore to pass the RealTemp sensor test even though he was Prime stable for 101 hours with less voltage.

The sensor test is using a feature in your CPU called clock modulation. Adjusting clock modulation provides 8 different performance levels to the CPU. A 100% stable CPU should be able to run at no load or full load or anywhere in between while adjusting clock modulation up and down whether C1E or EIST are enabled or not.

Are you overclocked? Have you tried adjusting vcore or tried running the test with a single stick of memory at a time. There has to be a reason why it is failing. When this test fails, it always fails at the same spot but I've never had this test lock up when I've used it. Not once.

ERLOESER was going crazy too trying to pass this stupid test but after he got everything adjusted, no more lock ups. Keep trying different settings.

I don't think it will make any difference to your problem since I haven't made any changes to the cool down test in a long time but you can try downloading the latest version here.

RealTemp 3.58
http://www.sendspace.com/file/1nscjd

I added a new option for recent ATI cards. Just add GPU=2 to the RealTemp.ini file to give it a try.