Blue screen of death crashes

[Logan15]

I've always seemed to have issue's with blue screens but I just let them happen and deal with them when they arise as i have had no idea how to fix them however i learnt how to open the Memory.DMP file and I think there is useful information which will help me solve this problem only if I understood it.

Memory.Dmp File

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17415.amd64fre.winblue_r4.141028-1500
Machine Name:
Kernel base = 0xfffff802`1187a000 PsLoadedModuleList = 0xfffff802`11b53250
Debug session time: Sun Jun 14 15:13:18.966 2015 (UTC + 1:00)
System Uptime: 0 days 2:20:43.649
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols

Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8008d2bd085, 0, ffffffffffffffff}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+825 )

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

7: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8008d2bd085, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffffffffffffff

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
USBPORT!USBPORT_Core_iCompleteDoneTransfer+825
fffff800`8d2bd085 488b45b8 mov rax,qword ptr [rbp-48h]

EXCEPTION_PARAMETER2: ffffffffffffffff

BUGCHECK_STR: 0x1E_c0000005_R

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE: FFFFD001A21B8FB0

EXCEPTION_RECORD: ffffd001a2185180 -- (.exr 0xffffd001a2185180)
ExceptionAddress: 0000000000000000
ExceptionCode: 00001f80
ExceptionFlags: 00000007
NumberParameters: -1575414848
Parameter[0]: 0000000700000001
Parameter[1]: ffffd001a21b0c10
Parameter[2]: 0000000000000000
Parameter[3]: ffffd001a5dea2d3
Parameter[4]: 0000000080050031
Parameter[5]: 0000000000000030
Parameter[6]: 00000000001aa000
Parameter[7]: 00000000000406f8
Parameter[8]: 0000000000000000
Parameter[9]: 0000000000000000
Parameter[10]: 0000000000000000
Parameter[11]: 0000000000000000
Parameter[12]: 00000000ffff0ff0
Parameter[13]: 0000000000000400
Parameter[14]: 007f000000000000

TRAP_FRAME: 0000000000000002 -- (.trap 0x2)
Unable to read trap frame at 00000000`00000002

LAST_CONTROL_TRANSFER: from fffff80211a5cc4e to fffff802119ca9a0

STACK_TEXT:
ffffd001`a21af378 fffff802`11a5cc4e : 00000000`0000001e ffffffff`c0000005 fffff800`8d2bd085 00000000`00000000 : nt!KeBugCheckEx
ffffd001`a21af380 fffff802`119d1eed : ffffd001`a21afaf0 00000000`00000000 ffffd001`a21b02e8 ffffd001`a21af4f0 : nt!KiFatalExceptionHandler+0x22
ffffd001`a21af3c0 fffff802`11954125 : 00000000`00000001 fffff802`1187a000 ffffd001`a21b0200 ffffe001`00000000 : nt!RtlpExecuteHandlerForException+0xd
ffffd001`a21af3f0 fffff802`119584de : ffffd001`a21b02e8 ffffd001`a21afff0 ffffd001`a21b02e8 ffffe001`c869c01c : nt!RtlDispatchException+0x1a5
ffffd001`a21afac0 fffff802`119d65c2 : ffffd001`a2185180 00000000`00000000 00000000`00000002 fffff802`118b07da : nt!KiDispatchException+0x646
ffffd001`a21b01b0 fffff802`119d4afe : 00000000`00001000 ffffe001`cde962a0 00000000`00000000 fffff802`11811220 : nt!KiExceptionDispatch+0xc2
ffffd001`a21b0390 fffff800`8d2bd085 : ffffe001`c7a0f100 ffffe001`cacc0970 ffffd001`a21b0630 ffffe001`c7a0f1a0 : nt!KiGeneralProtectionFault+0xfe
ffffd001`a21b0520 fffff800`8d2bc76d : ffffe001`c7a0ff02 ffffe001`c869c01c ffffe001`c7a100e0 ffffe001`c7a0f1a0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x825
ffffd001`a21b06c0 fffff800`8d2bc3e3 : ffffe001`c869c154 ffffe001`c7a10178 ffffe001`c7a0f1a0 00001de9`00001e00 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x21d
ffffd001`a21b0720 fffff800`8d2bbf4e : ffffd001`a21b0900 ffffe001`c7a0f050 00000000`00000002 ffffe001`00000002 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x1e3
ffffd001`a21b0790 fffff802`11944cd0 : ffffd001`a21b0910 fffff802`1187a000 ffffd001`a21b0ad0 00000000`00000f44 : USBPORT!USBPORT_Xdpc_Worker_IocDpc+0x1fe
ffffd001`a21b0810 fffff802`11943f87 : 40fff0f0`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x1b0
ffffd001`a21b0960 fffff802`119ce4ea : ffffd001`a2185180 ffffd001`a2185180 ffffd001`a21913c0 ffffe001`c7f59080 : nt!KiRetireDpcList+0xd7
ffffd001`a21b0be0 00000000`00000000 : ffffd001`a21b1000 ffffd001`a21aa000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!USBPORT_Core_iCompleteDoneTransfer+825
fffff800`8d2bd085 488b45b8 mov rax,qword ptr [rbp-48h]

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: USBPORT!USBPORT_Core_iCompleteDoneTransfer+825

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 53897701

IMAGE_VERSION: 6.3.9600.17195

BUCKET_ID_FUNC_OFFSET: 825

FAILURE_BUCKET_ID: 0x1E_c0000005_R_USBPORT!USBPORT_Core_iCompleteDoneTransfer

BUCKET_ID: 0x1E_c0000005_R_USBPORT!USBPORT_Core_iCompleteDoneTransfer

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_usbport!usbport_core_icompletedonetransfer

FAILURE_ID_HASH: {57aa27a7-08c9-f42d-d839-0706d04cbd5e}

Followup: MachineOwner


Computer Specs:
Case: Cit Neptune
power supply: non Modular 850w
GPU: Geforce GTX 760
CPU: Fx 8350 (underclocked at 3.50ghz)
Motherboard: Asus M5A78L-M/USB3 Motherboard
Ram: 1600 mhz ddr3

hope this will help you solve the problem thanks for any help.

 

[johnbl]

if you just want to take a stab at getting this fixed,
go to the motherboard vendor's website and get drivers:
update the BIOS to get any USB microcode updates,
update the CPU chipset to get any USB 2.x updated drivers
update any 3rd party USB 3.0 chipset drivers

update any USB wireless ethernet driver.
reboot and see if you still have problems. If you have a USB drive you would also want to do a malwarebytes scan
and run cmd.exe as an admin and run
sfc.exe /scannow
and confirm all corruptions were fixed, reboot and run the command again. (malware will undo fixes on the reboot)
since you have windows 8.x you should also run
cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

(it will fix corrupted files by going to the windows update server and getting new ones if the local copy is corrupted)

-----------
something attached to your usb hub corrupted data used by one of the usb drivers.

to debug this you would need to change the memory dump type to kernel
https://www.sophos.com/en-us/support/knowledgebase/111474.aspx

turn on verifiy flags: start cmd.exe as an admin, then run
verifier.exe /standard /all
then reboot and run until you get the next bugcheck.

note: use
verifier.exe /reset
to turn of verifier function when you are done testing.

then put the kernel memory dump on a server and post a link.

if you want to look yourself here are some useful debug commands.
!pnptriage
(helpful if a usb device is stuck trying to install a USB driver)
!usb3kd.usb_tree
(if you have usb 3.0 it will show devices and you can look at the internal logs)
!for_each_module !chkimg @#ModuleName
(used to help identify 3rd party driver and microsoft drivers that are corrupted in memory)
lmiftsm
(will list the drivers in alphabetical order with the file data and time)

lots of other commands.

 

[Logan15]

thanks for the reply i will try what you said.