mike406
SSC Member
- Total Posts : 904
- Reward points : 0
- Joined: 2015/02/21 18:17:33
- Status: offline
- Ribbons : 13
Hello, I've been trying to solve a recurring random bluescreen issue that has cropped up since about 3 weeks ago. It happens once every few days seemingly randomly when my PC is sitting idle. I ran the Windows debugging tool and have pasted the output below. The only meaningful info I see is WIN8_DRIVER_FAULT and the Process Name being MSIAfterburner.exe. I have updated my graphics drivers and the issue persisted. So then I tried lowering the OC settings to something very mild, still no dice. So now I moved onto the next logical step of disabling MSI Afterburner for now and we'll see what happens next. Just wondering if anyone has experienced something similar to this. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000008, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------
DUMP_CLASS: 1 DUMP_QUALIFIER: 402 BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804 SYSTEM_MANUFACTURER: EVGA INTERNATIONAL CO.,LTD SYSTEM_PRODUCT_NAME: Default string SYSTEM_SKU: Default string SYSTEM_VERSION: Default string BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: 2.05 BIOS_DATE: 03/22/2018 BASEBOARD_MANUFACTURER: EVGA INTERNATIONAL CO.,LTD BASEBOARD_PRODUCT: 142-SS-E178 BASEBOARD_VERSION: 1.0 DUMP_TYPE: 0 BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: 0 BUGCHECK_P3: 8 BUGCHECK_P4: 0 CPU_COUNT: 8 CPU_MHZ: fa8 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 5e CPU_STEPPING: 3 CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C2'00000000 (cache) C2'00000000 (init) DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: MSIAfterburner.exe CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: GAMING-PC ANALYSIS_SESSION_TIME: 07-16-2018 00:35:23.0626 ANALYSIS_VERSION: 10.0.15063.468 amd64fre EXCEPTION_RECORD: 000000000010a1c0 -- (.exr 0x10a1c0) Cannot read Exception record @ 000000000010a1c0 TRAP_FRAME: fffffb0f73c3e3a8 -- (.trap 0xfffffb0f73c3e3a8) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffffb0f73c3e4d0 rsp=0000000004029000 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=00000000c0000005 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di ng zr na pe nc 0001:e4d0 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff803bace62bd to fffff803bae25430 STACK_TEXT: fffffb0f`73c3dc18 fffff803`bace62bd : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx fffffb0f`73c3dc20 fffff803`bae36042 : 00000000`0010a1c0 00000000`00000000 fffffb0f`73c3e3a8 fffff805`8761a568 : nt!KiDispatchException+0x58d fffffb0f`73c3e2d0 fffff803`bae32bbf : ffffc701`cc5a3a00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffffb0f`73c3e4b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x3ff
STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 2e9ab7e93b3f60731b8608f9c5cc37cdb42d594f THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c271607aaddf50fb1dd43e22f19afc93e33dcb02 THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791 FOLLOWUP_IP: nt!KiDispatchException+58d fffff803`bace62bd 90 nop FAULT_INSTR_CODE: cccccc90 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiDispatchException+58d FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5b3f12f4 BUCKET_ID_FUNC_OFFSET: 58d FAILURE_BUCKET_ID: 0x1E_nt!KiDispatchException BUCKET_ID: 0x1E_nt!KiDispatchException PRIMARY_PROBLEM_CLASS: 0x1E_nt!KiDispatchException TARGET_TIME: 2018-07-16T04:17:05.000Z OSBUILD: 17134 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2018-07-06 02:57:56 BUILDDATESTAMP_STR: 180410-1804 BUILDLAB_STR: rs4_release BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804 ANALYSIS_SESSION_ELAPSED_TIME: 49a0 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x1e_nt!kidispatchexception FAILURE_ID_HASH: {4c003660-11e1-3fb7-2474-3522eb7ee67b} Followup: MachineOwner ---------
|
jfw06013
SSC Member
- Total Posts : 586
- Reward points : 0
- Joined: 2017/02/14 10:26:10
- Status: offline
- Ribbons : 4
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/15 22:43:57
(permalink)
did you try DDU to uninstall your graphics driver and then re-install them? I also use Revolt Uninstaller which is awesome (not free). Works very well.
|
mike406
SSC Member
- Total Posts : 904
- Reward points : 0
- Joined: 2015/02/21 18:17:33
- Status: offline
- Ribbons : 13
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/15 23:15:35
(permalink)
jfw06013 did you try DDU to uninstall your graphics driver and then re-install them? I also use Revolt Uninstaller which is awesome (not free). Works very well.
I went ahead and used DDU and reinstalled the latest drivers. We'll see if it helps. Thanks!
|
jfw06013
SSC Member
- Total Posts : 586
- Reward points : 0
- Joined: 2017/02/14 10:26:10
- Status: offline
- Ribbons : 4
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/16 00:02:13
(permalink)
did you do it in safe mode? if not do it in safe mode.
|
mike406
SSC Member
- Total Posts : 904
- Reward points : 0
- Joined: 2015/02/21 18:17:33
- Status: offline
- Ribbons : 13
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/16 00:48:54
(permalink)
jfw06013 did you do it in safe mode? if not do it in safe mode.
I did.
|
jfw06013
SSC Member
- Total Posts : 586
- Reward points : 0
- Joined: 2017/02/14 10:26:10
- Status: offline
- Ribbons : 4
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/16 01:11:32
(permalink)
|
Sajin
EVGA Forum Moderator
- Total Posts : 49165
- Reward points : 0
- Joined: 2010/06/07 21:11:51
- Location: Texas, USA.
- Status: offline
- Ribbons : 199
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/16 12:11:30
(permalink)
If it keeps happening with msi afterburner uninstalled install graphics driver 391.35.
|
mike406
SSC Member
- Total Posts : 904
- Reward points : 0
- Joined: 2015/02/21 18:17:33
- Status: offline
- Ribbons : 13
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/16 14:39:04
(permalink)
Sajin If it keeps happening with msi afterburner uninstalled install graphics driver 391.35.
Thank you for the suggestion. I will give this a try if it happens again after a few days of testing.
|
mike406
SSC Member
- Total Posts : 904
- Reward points : 0
- Joined: 2015/02/21 18:17:33
- Status: offline
- Ribbons : 13
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/23 20:06:15
(permalink)
Well it's been about a week, and I have not had another BSOD. I'm going to try and re-enable MSI Afterburner to see what happens next.
|
mike406
SSC Member
- Total Posts : 904
- Reward points : 0
- Joined: 2015/02/21 18:17:33
- Status: offline
- Ribbons : 13
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/28 16:05:29
(permalink)
Got another system crash. I couldn't get a DMP file because my drive space was too low, but I can only assume the issue has returned. I will try your suggested driver version Sajin.
|
Sajin
EVGA Forum Moderator
- Total Posts : 49165
- Reward points : 0
- Joined: 2010/06/07 21:11:51
- Location: Texas, USA.
- Status: offline
- Ribbons : 199
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/28 16:07:49
(permalink)
mike406 I will try your suggested driver version Sajin.
|
XrayMan
Insert Custom Title Here
- Total Posts : 73000
- Reward points : 0
- Joined: 2006/12/14 22:10:06
- Location: Santa Clarita, Ca.
- Status: offline
- Ribbons : 115
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/07/28 23:33:11
(permalink)
If all else fails, use your Windows media, and choose repair.
My Affiliate Code: 8WEQVXMCJL Associate Code: VHKH33QN4W77V6A  
|
mike406
SSC Member
- Total Posts : 904
- Reward points : 0
- Joined: 2015/02/21 18:17:33
- Status: offline
- Ribbons : 13
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/08/04 23:36:42
(permalink)
Appreciate the advice XrayMan, I will keep this in mind as the next step to try if the issue returns. The good news is, since downgrading to driver version 391.35 - things seem stable even with MSI Afterburner running. Hopefully that did the trick
|
squall-leonhart
CLASSIFIED Member
- Total Posts : 2904
- Reward points : 0
- Joined: 2009/07/27 19:57:03
- Location: Australia
- Status: offline
- Ribbons : 24
Re: Getting KMODE_EXCEPTION_NOT_HANDLED every few days - might be caused by MSIAfterburner
2018/08/19 22:58:23
(permalink)
Repair won't fix this, the issue is a bug in the 397 driver family beyond 397.64. 397.55 and earlier did not have it, but they had other issues that could error state the driver, Nvidia has an open task for it with HeavyHemi, myself and a number of other users with a variety of system configs spread across Windows 7-10 affected. I've brought it on with Aida64 and GPUShark personally.
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600 Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition Monitor:BenQ G2400WD, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX300 1000 HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1 Cooler: ThermalRight Silver Arrow IB-E Extreme
|