2016/11/20 04:56:24
pearhead
I'm having issues w/ my system and waiting on a reply to my support ticket. In the mean time though I thought I'd post. I'm running a Z170 FTW bios 1.07, w a 6600k. Stock speeds. I have tried 1.08-1.09 as well., 4x8gb Muskin dd4 3000. Crucial M500 240gb SSD, tests great in SSDLife Pro. I've removed all other hardware and taken it down to 1 stick of mem. I've tested all mem sticks in slot 2 and they test AOK in Windows Mem test and Memtest. I've tried 2 other PSU's currently using a Corsair CX850M(12.036-11.962 in bios and windows 10 under e-leet). System freezing randomly w/ Power-Kernel 41 in the event viewer every time. I had a bios chip go bad when the system hung on a bios flash when 1.09 first came out. Got a new chip from EVGA, and it worked great for about a day...system started freezing again. Thus the back to 1.07. It was somewhat stable. Yesterday i was watching temps and voltages in E-leet and w/ my memory in XMP 1 mode, and if I clicked restart in windows it would freeze. this is the only way i've been able to replicate a freeze. I have to hard reset to get system to reboot. With memory in automatic mode it wont freeze w/ E-leet open. I've uninstalled all evga software e-leet and precision and same results :( Tempted to try windows 7 and see if it's a windows 10 issue...Anyones input would be awesome... been fighting a long battle w/ all this flashing and testing :( I should add I also removed my video card(GTX 970) and have had the same issues w/ the onboard video as well.
 
Thanks, Pearhead
2016/11/20 08:02:24
rsabatino
i am thinking it might be your board because nobody is harder on computer than me. i have re flashed bios twice did numerous fresh installs of windows 10 on my ftw board now i am running an insiders build  and no problems.
2016/11/20 15:53:52
EVGATech_MDecker
Hello,
 
are you running any overclocks or voltage adjustments on your system currently?
 
Is your memory running at auto or did you set XMP?
2016/11/20 17:30:54
pearhead
Nope all stock voltages...no OC. With memory on auto, system will still freeze on it's own at any random time...(5 min to 1 day) but can't make it freeze by doing anything in particular. If I set it to XMP mode (where it was fine for nearly the last year) the freezes seem to happen quicker and that's when I can open E-leet, hit RESTART and it freezes every time. Weird huh?? :(  Right now it's somewhat stable under bios 1.07 w/ just one stick of memory, but will freeze eventually. If I flash to BIOS 1.08 or 1.09 I get more BSOD than just hard freezes. 
2016/11/20 19:19:17
Sajin
What are the bug check/stop codes for your blue screens?
2016/11/20 20:58:00
pearhead
the 3 bsod's i usually get are "System Service Exception, memory management errors, and IRQL NOT LESS OR EQUAL...might be some others but those are the ones i get off the top of my head. More so if I try BIOS 1.09... more freezing w/out bsod under 1.07 currently. Not really sure how to investigate them anymore than what they say on the BSOD itself when it does occur. I installed Blue Screen View, an app that showed me I also had a SYSTEM THREAD EXCEPTION NOT HANDLED...attached is the 4 BSOD it shows... 
==================================================
Dump File : 111916-12453-01.dmp
Crash Time : 11/19/2016 4:37:14 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff802`5793284c
Parameter 3 : ffffe281`f88106c8
Parameter 4 : ffffe281`f880fef0
Caused By Driver : dxgmms2.sys
Caused By Address : dxgmms2.sys+52d11
File Description : DirectX Graphics MMS
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.351 (rs1_release_inmarket.161014-1755)
Processor : x64
Crash Address : dxgmms2.sys+1284c
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111916-12453-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 562,308
Dump File Time : 11/19/2016 4:47:03 PM
==================================================
==================================================
Dump File : 111916-11468-01.dmp
Crash Time : 11/19/2016 2:21:39 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041793
Parameter 2 : fffffa00`0000baa8
Parameter 3 : 00000000`00000016
Parameter 4 : 00000000`00000015
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14a510
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.447 (rs1_release_inmarket.161102-0100)
Processor : x64
Crash Address : ntoskrnl.exe+14a510
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111916-11468-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 534,796
Dump File Time : 11/19/2016 2:23:16 PM
==================================================
==================================================
Dump File : 111916-5640-01.dmp
Crash Time : 11/19/2016 12:56:09 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff801`80bc4120
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : fffff801`80bc4120
Caused By Driver : storport.sys
Caused By Address : storport.sys+267f
File Description : Microsoft Storage Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.351 (rs1_release_inmarket.161014-1755)
Processor : x64
Crash Address : ntoskrnl.exe+14a510
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111916-5640-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 431,796
Dump File Time : 11/19/2016 12:58:19 PM
==================================================
==================================================
Dump File : 111916-7156-01.dmp
Crash Time : 11/19/2016 12:53:31 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : ffffa1a4`4f7eb741
Parameter 3 : ffff9080`78604bf0
Parameter 4 : 00000000`00000000
Caused By Driver : win32kbase.sys
Caused By Address : win32kbase.sys+5b741
File Description : Base Win32k Kernel Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.0 (rs1_release.160715-1616)
Processor : x64
Crash Address : ntoskrnl.exe+14a510
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111916-7156-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 14393
Dump File Size : 431,684
Dump File Time : 11/19/2016 12:54:05 PM
==================================================
2016/11/21 14:47:59
Sajin
Looks like a ram/cpu problem to me. When running memtest did you test each stick individually? If not, I would recommend retesting them. Run the IPDT on your cpu to make sure it's ok.
2016/11/21 18:53:34
pearhead
I did test each memory stick individually. I also tried a stick from a friend w/ an identical build. I ran the IPDT an it errors on PCH. I've made sure chipset drivers are installed. Bad cpu prob huh? 
2016/11/21 19:00:52
Sajin
pearhead
I did test each memory stick individually. I also tried a stick from a friend w/ an identical build. I ran the IPDT an it errors on PCH. I've made sure chipset drivers are installed. Bad cpu prob huh? 


Not necessarily. Do you have the intel rapid storage technology driver installed? If no, install it and retest.
2016/11/21 19:51:44
pearhead
Awesome help there!!! CPU totally passes. Hoping that driver issue has been the headache all along.  I'm thinking when I first had this board I was running Windows 7 and upgraded to windows 10, thus the driver was there from windows 7... a few months back when I started having this problem I had just done a clean install of Windows 10, and prob didn't have that Intel Rapid Storage Driver. You'd think that would be listed on the drivers download page?? Well will report back later as to how things are running!

Use My Existing Forum Account

Use My Social Media Account