The nightmare of event logs...

I get this issue, would be interesting if you get to the bottom of it.

It always happens with me due to a 'bad overclock' but the CPU isn't getting hot, memory at XMP settings, etc.

My 4770k needs stupid voltage at 4.5GHz to be considered stable, otherwise I get these WHEA errors.

I've tried numerous windows 8 installs. Might try Windows 7 but tbh I really don't want to go back to 7, I much prefer 8.
 
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:
When I get home i'm going to reset everything, memory to 1333 and see what my max overclock will be.

Everything points to an unstable overclock but a quick search of google shows people getting the same error with stock CPUs

I never had this issue with my AMD setup and Windows 8
 
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.
 
Hopefully youve got it sorted mate. Iirc, when haswell was first released was there not a lot of concern about the new c states it introduced and possible issues with certain psu's?
 
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:
Pretty quick with the bios updates, (always a good sign). Take it youll be going back onto win 8.1 then? Ill probably do a fresh os install when i stick the 4790k in, just unsure wether to stick on 7 or go to 8.1.
 
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
 
pgi947 said:
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...



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
Click to expand...

Paul,

Don't know why but I still suspect bad driver/service - try running verifier - google it, it is great at showing where drivers or services are causing problems. It is slightly complicated to set up on the options - that is why I suggest you google it for the guide to do it.

Hope this helps
Ps have replied to your pm this morning.

Mark
 
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 :)
 
pgi947 said:
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 :)
Click to expand...

Good news Paul - seems previous install of windows got badly corrupted - not surprising with all the bsod's. Have replied to your mail - add me to d box etc

Mark
 
You must log in or register to reply here.
Back
Top Bottom