Question
296 views

Unexpected Error: UNEXPECTED_KERNEL_MODE_TRAP (Wfd01000.sys)

TusharPandey asked on

Hello,

I am using Windows 8.1 on my Sony Vaio Fit15e svf15219sn.

From last 3 days the bsod of unexpected_kernel_mode_trap (Wdf01000.sys) is coming.

I had reset my laptop and than refresh it again but than also the error is not solved

Here is the minidump link

https://onedrive.live.com/redir?resid=5BF7DA13166608B2!5314&authkey=!AJSn4YlhG0v1-ko&ithint=file%2c.zip  

1 person had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on

Hi,

The attached DMP file is of the UNEXPECTED_KERNEL_MODE_TRAP (7f) bug check.

This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

BugCheck 7F, {8, ffffd0014a76e130, ffffd0014a774fe0, fffff800b6d4b6ca}

The 1st parameter of the bug check is 0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault.

1: kd> k
Child-SP          RetAddr           Call Site
ffffd001`4a76dfe8 fffff801`a237bae9 nt!KeBugCheckEx
ffffd001`4a76dff0 fffff801`a2379bf4 nt!KiBugCheckDispatch+0x69
ffffd001`4a76e130 fffff800`b6d4b6ca nt!KiDoubleFaultAbort+0xb4
ffffd001`4a774fe0 fffff800`b6d4f0d4 Wdf01000!FxIoQueue::GetRequest+0x62
ffffd001`4a775080 fffff800`b975ece0 Wdf01000!imp_WdfIoQueueRetrieveNextRequest+0x60
ffffd001`4a7750d0 fffff800`b975f678 USBXHCI!Bulk_RetrieveNextStage+0x368
ffffd001`4a775150 fffff800`b975db7a USBXHCI!Bulk_MapTransfers+0xd8
ffffd001`4a7751c0 fffff800`b6da9930 USBXHCI!Bulk_WdfEvtIoQueueReadyNotification+0x36
ffffd001`4a7751f0 fffff800`b6da9fff Wdf01000!FxIoQueueIoResume::Invoke+0x40
ffffd001`4a775220 fffff800`b6d38dd6 Wdf01000!FxIoQueue::ProcessReadyNotify+0x87
ffffd001`4a775280 fffff800`b6d28279 Wdf01000!FxIoQueue::DispatchEvents+0x1d016
ffffd001`4a775340 fffff800`b6d42050 Wdf01000!FxIoQueue::QueueRequest+0x8d
ffffd001`4a7753b0 fffff800`b97a2698 Wdf01000!imp_WdfDeviceWdmDispatchIrpToIoQueue+0x248
ffffd001`4a775430 fffff800`b97a1d1d ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer+0x194
ffffd001`4a7754e0 fffff800`b9797e20 ucx01000!Urb_USBPORTStyle_ProcessURB+0x331
ffffd001`4a775540 fffff800`b6d20d43 ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0x448
ffffd001`4a7755d0 fffff800`b6c247b0 Wdf01000!FxDevice::DispatchWithLock+0xb01
ffffd001`4a7756b0 fffff800`b6c26c4a ACPI!ACPIDispatchForwardIrp+0x70
ffffd001`4a7756e0 fffff800`b6c24157 ACPI!ACPIIrpDispatchDeviceControl+0xb6
ffffd001`4a775710 fffff800`ba4f0bea ACPI!ACPIDispatchIrp+0x147
ffffd001`4a775780 fffff800`b6d20d43 UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0xdd2
ffffd001`4a775890 fffff800`b6c247b0 Wdf01000!FxDevice::DispatchWithLock+0xb01
ffffd001`4a775970 fffff800`b6c26c4a ACPI!ACPIDispatchForwardIrp+0x70
ffffd001`4a7759a0 fffff800`b6c24157 ACPI!ACPIIrpDispatchDeviceControl+0xb6
ffffd001`4a7759d0 fffff800`baaa167f ACPI!ACPIDispatchIrp+0x147
ffffd001`4a775a40 fffff800`baaa14a0 usbccgp!DispatchPdoUrb+0x16f
ffffd001`4a775b40 fffff800`baaa01eb usbccgp!DispatchPdoInternalDeviceControl+0x80
ffffd001`4a775ba0 fffff800`b6d22056 usbccgp!USBC_Dispatch+0x1db
ffffd001`4a775c60 fffff800`ba6474eb Wdf01000!imp_WdfRequestSend+0x156
ffffd001`4a775cc0 ffffe000`def92fc0 VIA_USB_SER+0x24eb
ffffd001`4a775cc8 ffffe000`e5599520 0xffffe000`def92fc0
ffffd001`4a775cd0 ffffe000`de26e020 0xffffe000`e5599520
ffffd001`4a775cd8 fffff800`b6d36037 0xffffe000`de26e020
ffffd001`4a775ce0 fffff800`ba646c4f Wdf01000!imp_WdfCollectionAdd+0xdb
ffffd001`4a775d40 00001fff`20c4ce48 VIA_USB_SER+0x1c4f
ffffd001`4a775d48 00001fff`21d91fd8 0x00001fff`20c4ce48
ffffd001`4a775d50 00000000`00000000 0x00001fff`21d91fd8

It appears the VIA_USB_SER.sys driver is causing problems here. I am unsure as to what this driver is, perhaps a USB to Serial adapter, or vice-versa? I'd remove it ASAP device-wise as well as uninstall the software.

Regards,

Patrick

Debugger/Reverse Engineer.
Be the first person to mark this helpful

Abuse history


progress