is it einstein or my hardware?

paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35,825,044
RAC: 0
Topic 197349

before i go through the hoops known as dell tech support, i wanted to post here first. i personally think its the CPU but was asked if einstein could be the cause as its mentioned in the debugs.

back story, "new" xps 8700 well, new a few months ago. has been crashing about once a week since i got it with 0x124, the lovely "general" hardware failure (event log and windbg output to follow), at first they replaced the GPU. then when i posted a full windows debug of a full memory dump, they caught einstein mentioned and of course there blaming that. i dont buy it. but figured id post the info here since frankly, i have no idea what im reading and would like some input from you folks.

EDIT: i forgot to mention, to rule out my software i did a full system recovery (wipe out and install from factory image), the only things i have reinstalled are basic items for daily web surfing, i.e. firefox, avast!, and of course einstein and the windows debugger.

event viewer log

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 1/21/2014 6:09:50 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: POWERDRAGON
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe0000509d028, 0x00000000be000000, 0x000000000100110a). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 012114-28296-01.
Event Xml:



1001
0
2
0
0
0x80000000000000

2996


System
POWERDRAGON



0x00000124 (0x0000000000000000, 0xffffe0000509d028, 0x00000000be000000, 0x000000000100110a)
C:\WINDOWS\MEMORY.DMP
012114-28296-01

***********
text output of windows debug

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\paul\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is: srv*
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff803`dec1d000 PsLoadedModuleList = 0xfffff803`deee1990
Debug session time: Tue Jan 21 18:03:20.615 2014 (UTC - 5:00)
System Uptime: 2 days 22:31:09.307
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
.....
Loading unloaded module list
................................
Loading Wow64 Symbols
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe0000509d028, be000000, 100110a}

*** ERROR: Module load completed but symbols could not be loaded for einstein_S6CasA_1.05_windows_intelx86__SSE2.exe

"KERNEL32.DLL" was not found in the image list.
Debugger will attempt to load "KERNEL32.DLL" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload =,.
Unable to add module at 00000000`00000000
Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe0000509d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

"KERNEL32.DLL" was not found in the image list.
Debugger will attempt to load "KERNEL32.DLL" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload =,.
Unable to add module at 00000000`00000000

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: einstein_S6Cas

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:
ffffd000`20889d78 fffff803`df3d3cdf : 00000000`00000124 00000000`00000000 ffffe000`0509d028 00000000`be000000 : nt!KeBugCheckEx
ffffd000`20889d80 fffff803`dedd4d41 : 00000000`00000001 ffffe000`003762f0 ffffe000`003762f0 ffffe000`0509d028 : hal!HalBugCheckSystem+0xcf
ffffd000`20889dc0 fffff803`df3d416c : 00000000`00000728 00000000`00000002 ffffd000`2088a1b0 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`20889e20 fffff803`df3d44d9 : ffffe000`00000010 ffffe000`003762f0 ffffd000`20889fc8 ffffe000`003762f0 : hal!HalpMcaReportError+0x50
ffffd000`20889f70 fffff803`df3d43c4 : ffffe000`00375c80 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`20889fc0 fffff803`df3d460e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`2088a000 fffff803`df3d478f : ffffe000`00375c80 ffffd000`2088a230 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`2088a030 fffff803`ded757bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`2088a060 fffff803`ded75571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`2088a1a0 00000000`0040b294 : 0095c0c0`0028fae4 000006da`008d106c be6c5e87`008d1602 3c605445`101a8fb2 : nt!KiMcheckAbort+0x171
00000000`0028f330 0095c0c0`0028fae4 : 000006da`008d106c be6c5e87`008d1602 3c605445`101a8fb2 3cba2e8c`0028f698 : einstein_S6CasA_1_05_windows_intelx86__SSE2+0xb294
00000000`0028f338 000006da`008d106c : be6c5e87`008d1602 3c605445`101a8fb2 3cba2e8c`0028f698 3fa99999`01de94f0 : 0x0095c0c0`0028fae4
00000000`0028f340 be6c5e87`008d1602 : 3c605445`101a8fb2 3cba2e8c`0028f698 3fa99999`01de94f0 0000002c`0000002c : 0x000006da`008d106c
00000000`0028f348 3c605445`101a8fb2 : 3cba2e8c`0028f698 3fa99999`01de94f0 0000002c`0000002c 00000002`000000ac : 0xbe6c5e87`008d1602
00000000`0028f350 3cba2e8c`0028f698 : 3fa99999`01de94f0 0000002c`0000002c 00000002`000000ac 00001600`770cbe6f : 0x3c605445`101a8fb2
00000000`0028f358 3fa99999`01de94f0 : 0000002c`0000002c 00000002`000000ac 00001600`770cbe6f 0028fa10`00001600 : 0x3cba2e8c`0028f698
00000000`0028f360 0000002c`0000002c : 00000002`000000ac 00001600`770cbe6f 0028fa10`00001600 0000002c`3940b30e : 0x3fa99999`01de94f0
00000000`0028f368 00000002`000000ac : 00001600`770cbe6f 0028fa10`00001600 0000002c`3940b30e 00409454`00000002 : 0x0000002c`0000002c
00000000`0028f370 00001600`770cbe6f : 0028fa10`00001600 0000002c`3940b30e 00409454`00000002 706c6120`71657266 : 0x00000002`000000ac
00000000`0028f378 0028fa10`00001600 : 0000002c`3940b30e 00409454`00000002 706c6120`71657266 61746c65`64206168 : 0x00001600`770cbe6f
00000000`0028f380 0000002c`3940b30e : 00409454`00000002 706c6120`71657266 61746c65`64206168 6620746f`64316620 : 0x0028fa10`00001600
00000000`0028f388 00409454`00000002 : 706c6120`71657266 61746c65`64206168 6620746f`64316620 20636e20`746f6432 : 0x0000002c`3940b30e
00000000`0028f390 706c6120`71657266 : 61746c65`64206168 6620746f`64316620 20636e20`746f6432 20564c20`3e46323c : 0x00409454`00000002
00000000`0028f398 61746c65`64206168 : 6620746f`64316620 20636e20`746f6432 20564c20`3e46323c 203e3148`5f46323c : 0x706c6120`71657266
00000000`0028f3a0 6620746f`64316620 : 20636e20`746f6432 20564c20`3e46323c 203e3148`5f46323c 203e314c`5f46323c : 0x61746c65`64206168
00000000`0028f3a8 20636e20`746f6432 : 20564c20`3e46323c 203e3148`5f46323c 203e314c`5f46323c 323c203e`7246323c : 0x6620746f`64316620
00000000`0028f3b0 20564c20`3e46323c : 203e3148`5f46323c 203e314c`5f46323c 323c203e`7246323c 3c203e31`485f7246 : 0x20636e20`746f6432
00000000`0028f3b8 203e3148`5f46323c : 203e314c`5f46323c 323c203e`7246323c 3c203e31`485f7246 003e314c`5f724632 : 0x20564c20`3e46323c
00000000`0028f3c0 203e314c`5f46323c : 323c203e`7246323c 3c203e31`485f7246 003e314c`5f724632 0028f6dc`00000064 : 0x203e3148`5f46323c
00000000`0028f3c8 323c203e`7246323c : 3c203e31`485f7246 003e314c`5f724632 0028f6dc`00000064 013c14b1`01e053ee : 0x203e314c`5f46323c
00000000`0028f3d0 3c203e31`485f7246 : 003e314c`5f724632 0028f6dc`00000064 013c14b1`01e053ee 0028f9eb`ffffff5a : 0x323c203e`7246323c
00000000`0028f3d8 003e314c`5f724632 : 0028f6dc`00000064 013c14b1`01e053ee 0028f9eb`ffffff5a 403e0000`00000000 : 0x3c203e31`485f7246
00000000`0028f3e0 0028f6dc`00000064 : 013c14b1`01e053ee 0028f9eb`ffffff5a 403e0000`00000000 c0542484`6792b18b : 0x003e314c`5f724632
00000000`0028f3e8 013c14b1`01e053ee : 0028f9eb`ffffff5a 403e0000`00000000 c0542484`6792b18b 00000001`0028f430 : 0x0028f6dc`00000064
00000000`0028f3f0 0028f9eb`ffffff5a : 403e0000`00000000 c0542484`6792b18b 00000001`0028f430 c0673ba0`19cf1eed : 0x013c14b1`01e053ee
00000000`0028f3f8 403e0000`00000000 : c0542484`6792b18b 00000001`0028f430 c0673ba0`19cf1eed 01e03978`0c00000c : 0x0028f9eb`ffffff5a
00000000`0028f400 c0542484`6792b18b : 00000001`0028f430 c0673ba0`19cf1eed 01e03978`0c00000c bf15efa1`92350626 : 0x403e0000`00000000
00000000`0028f408 00000001`0028f430 : c0673ba0`19cf1eed 01e03978`0c00000c bf15efa1`92350626 00000000`01e0ba00 : 0xc0542484`6792b18b
00000000`0028f410 c0673ba0`19cf1eed : 01e03978`0c00000c bf15efa1`92350626 00000000`01e0ba00 0028f458`02080064 : 0x00000001`0028f430
00000000`0028f418 01e03978`0c00000c : bf15efa1`92350626 00000000`01e0ba00 0028f458`02080064 0028f710`0028f458 : 0xc0673ba0`19cf1eed
00000000`0028f420 bf15efa1`92350626 : 00000000`01e0ba00 0028f458`02080064 0028f710`0028f458 bf0304f2`a45c3a5c : 0x01e03978`0c00000c
00000000`0028f428 00000000`01e0ba00 : 0028f458`02080064 0028f710`0028f458 bf0304f2`a45c3a5c 00000000`bd0000bd : 0xbf15efa1`92350626
00000000`0028f430 0028f458`02080064 : 0028f710`0028f458 bf0304f2`a45c3a5c 00000000`bd0000bd 00000008`1fd74788 : 0x1e0ba00
00000000`0028f438 0028f710`0028f458 : bf0304f2`a45c3a5c 00000000`bd0000bd 00000008`1fd74788 0b7ac240`01fb7a20 : 0x0028f458`02080064
00000000`0028f440 bf0304f2`a45c3a5c : 00000000`bd0000bd 00000008`1fd74788 0b7ac240`01fb7a20 409c2000`00000000 : 0x0028f710`0028f458
00000000`0028f448 00000000`bd0000bd : 00000008`1fd74788 0b7ac240`01fb7a20 409c2000`00000000 3ea1f53f`4192513b : 0xbf0304f2`a45c3a5c
00000000`0028f450 00000008`1fd74788 : 0b7ac240`01fb7a20 409c2000`00000000 3ea1f53f`4192513b 3cba2e8c`000007ff : 0xbd0000bd
00000000`0028f458 0b7ac240`01fb7a20 : 409c2000`00000000 3ea1f53f`4192513b 3cba2e8c`000007ff 0bdc5020`00000000 : 0x00000008`1fd74788
00000000`0028f460 409c2000`00000000 : 3ea1f53f`4192513b 3cba2e8c`000007ff 0bdc5020`00000000 413c82d7`5456e61b : 0x0b7ac240`01fb7a20
00000000`0028f468 3ea1f53f`4192513b : 3cba2e8c`000007ff 0bdc5020`00000000 413c82d7`5456e61b 3feb6002`04d0576b : 0x409c2000`00000000
00000000`0028f470 3cba2e8c`000007ff : 0bdc5020`00000000 413c82d7`5456e61b 3feb6002`04d0576b 00000000`00000000 : 0x3ea1f53f`4192513b
00000000`0028f478 0bdc5020`00000000 : 413c82d7`5456e61b 3feb6002`04d0576b 00000000`00000000 00000001`00370030 : 0x3cba2e8c`000007ff
00000000`0028f480 413c82d7`5456e61b : 3feb6002`04d0576b 00000000`00000000 00000001`00370030 1fd75638`00000004 : 0x0bdc5020`00000000
00000000`0028f488 3feb6002`04d0576b : 00000000`00000000 00000001`00370030 1fd75638`00000004 3d39735a`4615a929 : 0x413c82d7`5456e61b
00000000`0028f490 00000000`00000000 : 00000001`00370030 1fd75638`00000004 3d39735a`4615a929 3be2b423`94732f2f : 0x3feb6002`04d0576b

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

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

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

David S
David S
Joined: 6 Dec 05
Posts: 2,473
Credit: 22,936,222
RAC: 0

is it einstein or my hardware?

Quote:

before i go through the hoops known as dell tech support, i wanted to post here first. i personally think its the CPU but was asked if einstein could be the cause as its mentioned in the debugs.

back story, "new" xps 8700 well, new a few months ago. has been crashing about once a week since i got it with 0x124, the lovely "general" hardware failure (event log and windbg output to follow), at first they replaced the GPU. then when i posted a full windows debug of a full memory dump, they caught einstein mentioned and of course there blaming that. i dont buy it. but figured id post the info here since frankly, i have no idea what im reading and would like some input from you folks.

EDIT: i forgot to mention, to rule out my software i did a full system recovery (wipe out and install from factory image), the only things i have reinstalled are basic items for daily web surfing, i.e. firefox, avast!, and of course einstein and the windows debugger.


I think the first thing I would do is stop Einstein for a week or two and see if the problem keeps happening. If it does, you can tell Dell it did and Einstein can't be the problem.

Einstein shouldn't be the problem, but the easiest way to convince the "experts" is to eliminate it.

David

Miserable old git
Patiently waiting for the asteroid with my name on it.

paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35,825,044
RAC: 0

i actually did do that, made

i actually did do that, made it 2 weeks before i needed to do a reboot, except, that doesnt really prove it was einstein, just that the system is stable under idle conditions. with out einstein running it uses about 3GB's ram and barely any cpu at all. so if this is a hardware issue that simply proves its fine under no load conditions. where as when einstein is running it uses 100% of all 8 threads (intel i7-4770) and 6GB's + of the 12GB's available.

it turns in to a bunch of "coulds" it "could" be the memory, once something hits a high value it trips (i reseated and even switched around the dimms so i doubt it), it "could" be the heatsink, it "could" be the cpu its self, it "could" be the motherboard... thats what i mean about hoops.

thats why i wanted to post here, to see if any one with the debugging skills can give me insight, i mean this "could" be an actual einstein issue. seriously doubt it though.

and i know if i use some other software to stress the system theyd just blame that. though that would prove its not "just" einstein, any "free" software out there any one knows of that can stress the cpu like einstein does?

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

DF1DX
DF1DX
Joined: 14 Aug 10
Posts: 72
Credit: 1,993,054,755
RAC: 1,900,225

Hi Paul, boot from a

Hi Paul,

boot from a Linux-Live-CD (e.g. Ubuntu) and run memcheck for 24 hours.

If ok then run prime95 (http://www.mersenne.org/freesoft/) and start the torture test (Options->Torture Test...) for 1 or 2 days.

Good luck!

Jürgen

ExtraTerrestrial Apes
ExtraTerrestria...
Joined: 10 Nov 04
Posts: 769
Credit: 294,548,711
RAC: 415,863

Jürgens suggestions are

Jürgens suggestions are good. I suppose it's rather a memory fault than the CPU (they hardly ever fail). Win also has a memory test included since about Win 8. It seems to be pretty much the same thing (which would make a lot of sense), but I don't know for sure. In any case both should run for a long time and if either of them shows an error you've probably got the problem grabbed by the balls. there's no way DELL could blame this on software loading your system.

MrS

Scanning for our furry friends since Jan 2002

MAGIC Quantum Mechanic
MAGIC Quantum M...
Joined: 18 Jan 05
Posts: 1,367
Credit: 452,230,252
RAC: 123,813

Maybe give this a try

Maybe give this a try Paul

http://windows.microsoft.com/en-us/windows7/diagnosing-memory-problems-on-your-computer

I only have one Win8.1 and never had to do this myself.

Snow Crash
Snow Crash
Joined: 24 Dec 09
Posts: 65
Credit: 100,880,785
RAC: 0

While based on issues caused

While based on issues caused by OC I think the codes/ causes are likely still relevant:
0×124 = add/remove vcore or VTT voltage (usually Vcore, once it was QPI/VTT)
0×101 = add more vcore
0×50 = RAM timings/Frequency add DDR3 voltage or add VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add VTT voltage
0x9C = VTT most likely, but increasing vcore has helped in some instances
0X109 = add DDR3 voltage
0x0A = add VTT voltage
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your RAM voltage. Can also mean more juice for the south bridge ICH volts
0×19: memory voltage

--------------------------
- Crunch, Crunch, Crunch -
--------------------------

paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35,825,044
RAC: 0

well, my warranty goes out in

well, my warranty goes out in a month. and dell still insists its einstein. all because they see the binary mentioned in the error. system just crashed again and ill post the latest dump. i personally call b.s. but with out hard proof im SOL, as i was actually considering suing them. thing is, if i dont run einstein it still crashes it just picks another binary to mention. but it takes a significantly longer amount of time to do so.

oh, and we can rule out memory. they replaced every single part on here "except" the cpu. i dont suppose i could send it in to INTEL on my own some how? (or some windebug commands i can use to drill this down further since dell wont even let me send them the memory dumps?)

latest debug

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\paul\Desktop\memmory dumps\MEMORY_05242014.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is: srv*
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff801`8967f000 PsLoadedModuleList = 0xfffff801`899492d0
Debug session time: Sat May 24 04:31:22.355 2014 (UTC - 4:00)
System Uptime: 4 days 22:01:03.051
Loading Kernel Symbols
...............................................................
................................................................
.......................................Page 283998 not present in the dump file. Type ".hh dbgerr004" for details
...
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7ffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe00090d3a028, be000000, 100110a}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00090d3a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: einstein_S6Cas

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

STACK_TEXT:
ffffd001`6aac9df8 fffff801`89646203 : 00000000`00000124 00000000`00000000 ffffe000`90d3a028 00000000`be000000 : nt!KeBugCheckEx
ffffd001`6aac9e00 fffff801`8983f825 : 00000000`00000001 ffffe000`8caaf460 ffffe000`8caaf460 ffffe000`90d3a028 : hal!HalBugCheckSystem+0xcf
ffffd001`6aac9e40 fffff801`8964668c : 00000000`00000728 00000000`00000003 ffffd001`6aaca230 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd001`6aac9ea0 fffff801`89646a11 : ffffe000`00000010 ffffe000`8caaf460 ffffd001`6aaca048 ffffe000`8caaf460 : hal!HalpMcaReportError+0x50
ffffd001`6aac9ff0 fffff801`896468f4 : ffffe000`8caaed30 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd001`6aaca040 fffff801`89646b4e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd001`6aaca080 fffff801`89646cd7 : ffffe000`8caaed30 ffffd001`6aaca2b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd001`6aaca0b0 fffff801`897ddabb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd001`6aaca0e0 fffff801`897dd871 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd001`6aaca220 00000000`0040b138 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
00000000`0028f330 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x40b138

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

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

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

mikey
mikey
Joined: 22 Jan 05
Posts: 7,516
Credit: 616,378,497
RAC: 33,863

RE: well, my warranty goes

Quote:

well, my warranty goes out in a month. and dell still insists its einstein. all because they see the binary mentioned in the error. system just crashed again and ill post the latest dump. i personally call b.s. but with out hard proof im SOL, as i was actually considering suing them. thing is, if i dont run einstein it still crashes it just picks another binary to mention. but it takes a significantly longer amount of time to do so.

oh, and we can rule out memory. they replaced every single part on here "except" the cpu. i dont suppose i could send it in to INTEL on my own some how? (or some windebug commands i can use to drill this down further since dell wont even let me send them the memory dumps?)---------

I'm guessing you did run the Prime95 test then?

These two lines also bother me:
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
and
FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache.

You may have to search for some cpu test programs such as those here:
http://www.hiren.info/pages/bootcd Down near the bottom of the page is Testing Tools, if you download the whole cd you will get all of the tools, but you can also download them one at a time and test things. I clicked on test cpu/video... and got this screen: http://www.geocities.ws/sluvoni/

It seems to show that it tests your cpu cache. You might want to also test your video memory using these two tools too:
Video Memory Stress Test 1.7.116 A tool to thoroughly test your video RAM for errors and faults.
and
Video Memory Stress Test CE 1.21 Tests all video RAM accessible by 32-bit CPU address space from a clean environment.

As you said you ONLY have 30 days left, I would get testing soon to figure out what the problem is, or may have to live with it.

ExtraTerrestrial Apes
ExtraTerrestria...
Joined: 10 Nov 04
Posts: 769
Credit: 294,548,711
RAC: 415,863

As Mikey said, you should

As Mikey said, you should really do some of the tests suggested here. Some easier options:

- Run any other BOINC project. I suspect the CPU load will also trigger the error quicker than regular operation. Then they can't point to Einstein any more. If they still decline you could run a 3rd project.. and ask them which program is allowed to fully load their machine. If the answer is "none" it might be time to sue. Otherwise - try it and it wil probably also generate the error.

- Run some stress tests in Win (instead of BOINC). "Intel Burn Test" (easy to google) is a good one, as it comes from a Intel themselves.

MrS

Scanning for our furry friends since Jan 2002

Dennis
Dennis
Joined: 8 Nov 09
Posts: 5
Credit: 9,608,099
RAC: 70

If you are ok with linux,

If you are ok with linux, Stresslinux is good for these hard to find problems.

http://www.stresslinux.org/sl/

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.