The nightmare of event logs...

pgi947

pgi947

pgi947

Soldato
Joined
25 Jun 2011
Posts
16,797
Location
Aberdeen
Since moving to Z97 from Z87 I've expereinced no end of BSOD's, 9 times out of 10 its just the WHEA_UNCONTROLLABLE_ERROR - but it doesn't document the error code in event viewer, but what I did find was this...

broken.jpg

Nearly all of those are drive related, some of its spouting something about not enough room for shadow play to operate, others saying disk x: requires chkdsk etc...which its had and reported back fine.

Even though the above BSOD's only seem to happen when OC'd (especially straight after splash) and only on Windows 8.1, I can't help but feel this is something chipset related thats taking a hit when I start manually entering settings.

I even went and purchased another copy of Windows 7 - which runs flawlessly, even with a big OC.

So any ideas before I do my 3rd Windows 8.1 install of the year? Honestly don't have time for this either :(

System:
4770K
Z97 XPower AC
8GB TridentX (have tried multiple memory configurations with many kits, all are faultless!)
3 x 256GB SSD (Agility 3, Vertex460 & Vector150)
1 x 1TB Samsung HDD
780 SLI
Antec HCP 1000w
 
Hang fire, in true pebkac fashion it appears Intel management engine install is corrupt, so repaired that now stressing again...

Edit: nope still happening...straight after splash with a manual oc.
 
Last edited:
Was up quite late last night reading up, from what I gather...

Whea errors are formed from reports sent by he CPU to the os, from what I can make out its stop code 0x124, which I believe to be vcore related. My overclocke was fine on z87 with the same os install. Any current oc with z97 is fine on windows 7, windows 8 gives the above bsod on login. If I use the motherboards oc genie, it auto clocks to 4.2ghz - and is stable in 8.1.

This leads me to believe one of the following things may be happening:

-oc genie is changing some setting somewhere that I've missed
-CPU is incorrectly reporting voltage to the os causing the bsod
-other fault I'm missing, bad ram/ssd or something.

I'm fairly certain my hardware is fine, 4.4ghz 1.4v (high Intentionally to rule out low vcore/droop) posts to windows 7 fine, will let me torture it as long as I like, fails to get past splash logon with win 8.1. Always at the same point, presumably when either a driver loads or when something is being reported.

Any ideas at all guys, this error is driving me nuts.
 
Cheers huddy!!

To round up, drive related errors in op appear to have cleared up with repairing the management engine, but the whae bsods persist with a manual oc only within windows 8.1. Auto oc functions fine in 8.1 and manual oc is fine in windows 7. Previous z87 motherboard held a manual oc fine, have since changed PSU and moved to z97 xpower.
 
Thanks for the replies guys!

Yer I saw those BSOD codes, already knew 0x124 was supposed to be vcore related, as I've had it in the past while OC'ing! Only this time I know the limits of my hardware and what works at what voltages.

Thanks tipes, whocrashed is a wonderful little program - far more informative then event viewer :)

I've managed to get into 8.1 at x43 with 1.38v vcore, any higher on the multi it bails as soon as I hit the login page. I KNOW this chip does 4.6ghz @ 1.28v, as thats what it was at for the 8 months prior to changing motherboard and it also still loads up win7 and stresses in that just fine.

whocrashed reports:

On Thu 12/06/2014 16:57:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061214-9656-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37203)
Bugcheck code: 0x124 (0x0, 0xFFFFE00057E03028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Click to expand...

Also a few of these, the most recent being last night:

On Wed 11/06/2014 22:44:11 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061114-11906-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
Click to expand...

I also know its not a thermal issue, chip is delidded, liquid pro and under a waterblock. Temps are fine in windows 7, and were previously in windows 8.1 with Z87.

I've disabled all non-essential programs from startup and windows 8.1 safe mode still posts up fine (though reporting programs in SM say clocks are 3.5ghz?).
 
Aye I've had it before due to sa needing a bump, bit as is my memory is running stock 1600 c11 to take it out of the equation.

I have two instances of Intel watchdog timer driver in add/remove, one gives no info (version number etc...) And says I don't have permission to remove and the other instance does nothing when I ask it to uninstall.

So any ideas on tools that can force remove these? Trying to get to an as-good-as driverless state and iirc the watchdog timer will bsod the system if it detects issues with the CPU? Could be on to something here.
 
Oh, I did have SSD's in the back of my mind, I have 3 in total, all OCZ!

Agility 3 256GB - Sandforce (Windows 8.1)
Vertex460 256GB - Indilinx Barefoot 3 (windows 7)
Vector 150 256GB - Indilinx Barefoot 3 (Empty)

Think it might be worth mirroring the 8.1 install over to the vector 150?
 
Cheers tipes I'll try that tomorrow.

Intel management engine refuses to remove too, I can repair it but it still gives an error about failing to uninstall, though the log says windows uninstall shield removed but produced error 1603 and it stays as recognised as installed on 8.1.

Its all looking a bit like z87 and z97 intel drivers have screwed up together in the process putting out false info to cause the bsod.

If this doesn't sort it then its clean install time unfortunately, I've grown to like 8.1 quite a lot.
 
We will see, I don't think a clean install would be such a bad idea anyhow, just a shame Microsoft haven't released any 8.1.1 images, only 8.0, so a long old string of updates to come.
 
Oooh good find!!! I'll have to double check what c-states are set at but iirc they should all be disabled - unless of course I have missed one, as some are direct under the oc settings and some in CPU features :)

This could also make sense of the massive vcore required to get into windows, as no doubt the low power voltage scales from the vcore...
 
Last edited:
Yeah same, everything's just to coincidental to be a bad oc...home now will check c-states shortly, will compare them to what the auto oc uses too.
 
FIXED!!!!!!!!!!!!!!!!!!

FIXED!!!!!!!!!!!!!

It was a C-State option, I've been bouncing about in the bios between an auto OC profile and a manual one, while C1E and EIST WAS disabled, something merely called 'Intel C-State' which triggers another C-State option (which was on auto). Disabled the initial C-State and now all is well.

Some more testing to come as I haven't ramped up the ram or anything yet.

TL;DR: Disabled something called Intel C-State, now all is well.
 
Not sure mate, new PSU in as well so that might have played a part.

Going to clean Install tomorrow still as I've ripped that much out of the gutts of the system I now get watchdog timeout errors :p

Edit: new bios out today too!

- Enhanced OC Call Back function. - Updated BIOS Code Base. - Updated MSI GESII Module. - Improved S4 resume function.
Click to expand...
 
Last edited:
Its definitely disabled. Same as before, Windows 7 fine, 8.1 not, so yes tipes I'll take you up on the offer of the OS image - I'll be in touch tomorrow with some hosting details - thank you :)

Its strange, I set the auto OC, runs fine, mirrored every setting I could see (scaled 4.4ghz) and I couldn't get into windows manually.

oddly enough the WHAE BSOD's are gone, the two flavours now...

On Fri 13/06/2014 21:48:30 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061314-9296-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1D18D)
Bugcheck code: 0xFC (0xFFFFD0017274D520, 0x800000013A365963, 0xFFFFD0017274D080, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 13/06/2014 21:48:30 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: eamonm.sys (eamonm+0x2B10F)
Bugcheck code: 0xFC (0xFFFFD0017274D520, 0x800000013A365963, 0xFFFFD0017274D080, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\drivers\eamonm.sys
product: ESET Smart Security
company: ESET
description: Amon monitor
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: eamonm.sys (Amon monitor, ESET).
Google query: ESET ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Click to expand...

The first referring to a file system error (back thinking SSD) and the second is referencing my anti-virus (ESET NOD32). Will swap out ram tomorrow
 
Enables verifier and then got a driver verifier violation bsod...

Edit: these bsods are continuing at stock also, good or bad sign?

Edit 2: windows 8.1 is now completely unusable.

On Sat 14/06/2014 14:26:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061414-10343-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt+0x12258)
Bugcheck code: 0xC4 (0x2001B, 0xFFFFF8012AA8BFF0, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\verifierext.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Driver Verifier Extension
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION



On Sat 14/06/2014 14:26:47 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!XdvNotifyExtensions+0x360)
Bugcheck code: 0xC4 (0x2001B, 0xFFFFF8012AA8BFF0, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\verifierext.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Driver Verifier Extension
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION



On Sat 14/06/2014 14:24:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061414-19859-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt+0x12258)
Bugcheck code: 0xC4 (0x2001B, 0xFFFFF80009C7FFF0, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\verifierext.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Driver Verifier Extension
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation DRIVER_VERIFIER_DETECTED_VIOLATION
Click to expand...
 
Last edited:
Right, swapped out ram, Installed windows 8 (not 8.1 yet) to a spare ssd, installed all the basic drivers, currently flying through prime at 4.6ghz 1.3v :)
 
You must log in or register to reply here.
Back
Top Bottom