Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › [SOLVED] Windows 8.1 Fresh install - "KMODE_EXCEPTION_NOT_HANDLED"
New Posts  All Forums:Forum Nav:

[SOLVED] Windows 8.1 Fresh install - "KMODE_EXCEPTION_NOT_HANDLED"

post #1 of 2
Thread Starter 
I just got a bluescreen while gaming Battlefield 4.
I was running this:
Windows 8.1 Pro Preview - Build 9431
Fresh install yesterday, went from Windows 7 Ultimate
Temperatures were OK at that time.

This is the first time I get this bluescreen, but I don't want it to come back later.

Straight from WinDbg: Warning: Spoiler! (Click to show)
Code:
Loading Dump File [C:\Windows\Minidump\100913-7671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Symbols2*http://msdl.microsoft.com/download/symbols;C:\Symbols
Executable search path is: 
Windows 8 Kernel Version 9431 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9431.0.amd64fre.winmain_bluemp.130615-1214
Machine Name:
Kernel base = 0xfffff802`71c19000 PsLoadedModuleList = 0xfffff802`71ee3990
Debug session time: Wed Oct  9 23:32:25.508 2013 (UTC + 2:00)
System Uptime: 0 days 6:05:34.207
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff80002d6254a, ffffe000058bc8c0, 8}

Probably caused by : HIDPARSE.SYS ( HIDPARSE!HidP_UsageListDifference+d6 )

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

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002d6254a, The address that the exception occurred at
Arg3: ffffe000058bc8c0, Parameter 0 of the exception
Arg4: 0000000000000008, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
HIDPARSE!HidP_UsageListDifference+d6
fffff800`02d6254a 498d3c44        lea     rdi,[r12+rax*2]

EXCEPTION_PARAMETER1:  ffffe000058bc8c0

EXCEPTION_PARAMETER2:  0000000000000008

BUGCHECK_STR:  0x1E_c000001d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  bf4.exe

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFD000209EAFB0

EXCEPTION_RECORD:  ffffe00002102010 -- (.exr 0xffffe00002102010)
Cannot read Exception record @ ffffe00002102010

TRAP_FRAME:  ffffe0000509c7a0 -- (.trap 0xffffe0000509c7a0)
Unable to read trap frame at ffffe000`0509c7a0

LAST_CONTROL_TRANSFER:  from fffff80271df37aa to fffff80271d69da0

FAILED_INSTRUCTION_ADDRESS: 
HIDPARSE!HidP_UsageListDifference+d6
fffff800`02d6254a 498d3c44        lea     rdi,[r12+rax*2]

STACK_TEXT:  
ffffd000`209e9388 fffff802`71df37aa : 00000000`0000001e ffffffff`c000001d fffff800`02d6254a ffffe000`058bc8c0 : nt!KeBugCheckEx
ffffd000`209e9390 fffff802`71d712ed : fffff802`71f22000 fffff802`71c19000 0003ee44`00791000 ffffe000`00e821b0 : nt!KiFatalExceptionHandler+0x22
ffffd000`209e93d0 fffff802`71c4ccc7 : 00000000`00000000 ffffd000`209e9500 ffffd000`209ea328 ffffd000`209e9500 : nt!RtlpExecuteHandlerForException+0xd
ffffd000`209e9400 fffff802`71c4e98b : ffffd000`209ea328 ffffd000`209ea030 ffffd000`209ea328 00000000`00000000 : nt!RtlDispatchException+0x3f7
ffffd000`209e9b00 fffff802`71d75ac2 : ffffe000`02102010 00000000`00000000 ffffe000`0509c7a0 ffffe000`02c27010 : nt!KiDispatchException+0x61f
ffffd000`209ea1f0 fffff802`71d73847 : ffffe000`0509c7a0 00000000`00000103 ffffe000`02c26a38 ffffe000`02c26a38 : nt!KiExceptionDispatch+0xc2
ffffd000`209ea3d0 fffff800`02d6254a : ffffe000`02c5b88c 00000000`00000001 00000000`00000000 ffffe000`02c5b890 : nt!KiInvalidOpcodeFault+0x107
ffffd000`209ea568 fffff800`02d69596 : 00000000`00000000 ffffd000`209ea5e0 ffffe000`02ab2150 ffffe000`02c5b720 : HIDPARSE!HidP_UsageListDifference+0xd6
ffffd000`209ea590 fffff802`71c819b4 : ffffe000`02c25850 ffffe000`0179c601 ffffd000`00000007 00000000`00000000 : mouhid!MouHid_ReadComplete+0x176
ffffd000`209ea620 fffff800`02d4423f : ffffe000`03149fa0 ffffe000`00000006 ffffd000`209ea760 00000000`00000009 : nt!IopfCompleteRequest+0x4c4
ffffd000`209ea700 fffff800`02d43a0e : ffffe000`00000000 ffffe000`01e6f1d0 00000000`00000008 ffffe000`01e6f000 : HIDCLASS!HidpDistributeInterruptReport+0x12f
ffffd000`209ea7a0 fffff802`71c819b4 : ffffe000`010c6010 ffffe000`010c6010 ffffd000`209ea801 ffffe000`02c75a00 : HIDCLASS!HidpInterruptReadComplete+0x2ae
ffffd000`209ea830 fffff800`01a0de79 : ffffe000`087c74cc ffffe000`022df000 ffffe000`02c75a10 fffff800`01b047aa : nt!IopfCompleteRequest+0x4c4
ffffd000`209ea910 fffff800`01a09684 : ffffe000`087c74cc ffffe000`087c74cc ffffe000`022e00e0 00000000`ffffffff : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x419
ffffd000`209eaaa0 fffff800`01a09d20 : ffffe000`022e0002 ffffe000`087c74cc ffffd000`209eabc0 ffffe000`022e00e0 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x1d4
ffffd000`209eab00 fffff800`01a09b5a : ffffe000`022e00e0 ffffe000`022e00e0 ffffd000`209eabc0 ffffd000`209b9102 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x180
ffffd000`209eab60 fffff802`71cbe0c8 : ffffd000`209bbf00 00000000`00000f44 ffffd000`209b9180 ffffd000`20d845b0 : USBPORT!USBPORT_Xdpc_Worker_IocDpc+0x172
ffffd000`209eabe0 fffff802`71cbd361 : ffffd000`209b9180 ffffd000`209eae30 ffffe000`00d038c0 ffffd000`209b9180 : nt!KiExecuteAllDpcs+0x1b8
ffffd000`209ead30 fffff802`71d6ced5 : 48c48b48`c35e5f5c ffffd000`209b9180 ffffd000`20d84640 00000000`583d6060 : nt!KiRetireDpcList+0xe1
ffffd000`209eafb0 fffff802`71d6ccd9 : 00000000`00000000 00000000`00000018 ffffe000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffd000`269b2c00 fffff802`71d6ef45 : 00000000`00000000 fffff802`71d6abd3 ffffe000`058bc8c0 00000000`ffffffff : nt!KiDispatchInterruptContinue
ffffd000`269b2c30 fffff802`71d6abd3 : ffffe000`058bc8c0 00000000`ffffffff 00000000`00000000 ffffe000`080a7730 : nt!KiDpcInterruptBypass+0x25
ffffd000`269b2c40 00007ffb`9e0a14d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0x173
00000000`5b1ffad8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`9e0a14d3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
HIDPARSE!HidP_UsageListDifference+d6
fffff800`02d6254a 498d3c44        lea     rdi,[r12+rax*2]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  HIDPARSE!HidP_UsageListDifference+d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDPARSE

IMAGE_NAME:  HIDPARSE.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  51bd088b

BUCKET_ID_FUNC_OFFSET:  d6

FAILURE_BUCKET_ID:  0x1E_c000001d_BAD_IP_HIDPARSE!HidP_UsageListDifference

BUCKET_ID:  0x1E_c000001d_BAD_IP_HIDPARSE!HidP_UsageListDifference

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

Tell me if you want any more info etc.
(400th post:D)

-MiiX
Edited by MiiX - 10/9/13 at 5:17pm
post #2 of 2
Thread Starter 
Sh** turned out to be a failed overclock. Not sure why it did not work in Windows 8, but perfect in Windows 7. Ohwell, Stock speeds on the CPU fixed it.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › [SOLVED] Windows 8.1 Fresh install - "KMODE_EXCEPTION_NOT_HANDLED"