Computer Keeps Crashing

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

tldpolak

Reputable
Aug 30, 2018
46
0
4,530
So My computer stopped BSOD and now it just frames drops after gaming for a few hours, but only on league of legends no other games crash. But it just freezes my PC and I have to shut it off and turn it back on I have updated drivers, looked into my event viewer to fix issues in there. I thought it was my Logitech headset crashing it, so I used a different headset and it still crashed. I am honestly emotionally exhausted with my PC constantly crashing. I have no idea how to fix it when I cant even see crash logs other than the event viewer. If anyone could help that would be great I only just built this custom PC almost a year ago, so it shouldn't be all messed up and it only started crashing recently but it did BSOD for about a month after I reinstalled windows to install my optane memory. It doesn't BSOD anymore it just freezes and I cant move anything, but only with league of legends. I've played hours on other games and its perfectly fine.
 
verifier should crash the system and name the bad driver and what it is doing wrong.
the info will be in the minidump file or kernel dump file depending on your crash dump settings.



 
if you change out the gpu card be sure to go into bios and reset the bios to defaults or change any setting and change it back so the bios will scan your hardware and reassign hardware resources. it will pass a database of settings to windows so windows will know what settings have been used and what is free to be assigned.

google "how to put windows into safe mode" there are various methods and different versions of windows.


audio driver tend to be screwy since they tend to be output devices with no feedback. you can have several audio drivers using the same direct memory access buffers and overwriting each others data. you never know unless you happen to have a speaker connected to the device at the time of crash. Then you just hear a sound come out of the speaker before the system crashes or locks up.


 
windows will recognize the device the problem is without the reset of the bios you will not know if windows thinks you have two gpus. the new one that is working because it was detected and the old one that the bios said was there but is not working. when this happens the primary resources are blocked from use and the card is setup using secondary hardware setting. These secondary settings can get pretty screwy, I have seen systems with GPU drivers waiting to use shared hardware settings with really stupid devices like a USB port. in that case, when the person used his mouse the GPU would generate a timeout and crash the system. (I thought it was pretty funny, for a GPU to be waiting for a mouse button to be released)

toggling a bios setting can force the rescan and you don't have to reset everything to defaults



 

Okay ran the verifier and now it bsods every time I log in to my user on windows?
 
Okay I rebooted back in safe mode to look at the mini dump file. But I'm not sure how I can send it to you if I don't have internet on the PC and if its not in safe mode it will bsod.
 


Okay so I just had to delete the verifier from running, but I probably still have the ladfgss.sys bsod error. the two dump files I got are here


SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80332aa58d1, The address that the exception occurred at
Arg3: ffffc28ed48a6b28, Exception Record Address
Arg4: ffffc28ed48a6370, Context Record Address

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17134.285 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1302

BIOS_DATE: 03/15/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: PRIME Z270-A

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80332aa58d1

BUGCHECK_P3: ffffc28ed48a6b28

BUGCHECK_P4: ffffc28ed48a6370

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

FAULTING_IP:
nt!IovpValidateDeviceObject+5
fffff803`32aa58d1 66833903 cmp word ptr [rcx],3

EXCEPTION_RECORD: ffffc28ed48a6b28 -- (.exr 0xffffc28ed48a6b28)
ExceptionAddress: fffff80332aa58d1 (nt!IovpValidateDeviceObject+0x0000000000000005)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000046dc232
Attempt to read from address 00000000046dc232

CONTEXT: ffffc28ed48a6370 -- (.cxr 0xffffc28ed48a6370)
rax=ffffd38189eecd80 rbx=ffffd38189eecd80 rcx=00000000046dc232
rdx=0000000000000000 rsi=00000000046dc232 rdi=ffff9006d3829b30
rip=fffff80332aa58d1 rsp=ffffc28ed48a6d68 rbp=fffff80332ac2ab8
r8=0000000000000000 r9=0000000000000000 r10=fffff80332ad57c0
r11=0000000000000000 r12=fffff808a20ba140 r13=fffff808a20ba140
r14=0000000000000000 r15=0000000000400000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!IovpValidateDeviceObject+0x5:
fffff803`32aa58d1 66833903 cmp word ptr [rcx],3 ds:002b:00000000`046dc232=????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

FOLLOWUP_IP:
HIDCLASS!HidpCallDriver+a2
fffff808`a20a76a2 488bcb mov rcx,rbx

BUGCHECK_STR: AV

READ_ADDRESS: fffff803326df388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
00000000046dc232

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000046dc232

ANALYSIS_SESSION_HOST: TANNER-POLAK

ANALYSIS_SESSION_TIME: 09-24-2018 02:55:12.0650

ANALYSIS_VERSION: 10.0.17134.12 x86fre

LOCK_ADDRESS: fffff8033265a4e0 -- (!locks fffff8033265a4e0)
Cannot get _ERESOURCE type

Resource @ nt!PiEngineLock (0xfffff8033265a4e0) Available
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff8033265a4e0
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff80332aa4c1e to fffff80332aa58d1

STACK_TEXT:
ffffc28e`d48a6d68 fffff803`32aa4c1e : ffffd381`89eecd80 00000000`00000000 ffff9006`d37d9010 ffff9006`d317e810 : nt!IovpValidateDeviceObject+0x5
ffffc28e`d48a6d70 fffff803`324a7263 : 00000000`00000017 00000000`00000000 ffff9006`d317e810 ffff9006`d3829b30 : nt!IovCallDriver+0x16a
ffffc28e`d48a6db0 fffff808`9aac53b3 : ffff9006`d365c2b8 fffff803`32abe613 fffff803`32ac328b ffff9006`d365c010 : nt!IofCallDriverSpecifyReturn+0xae2b3
ffffc28e`d48a6de0 fffff803`32ab25f1 : ffff9006`d3844010 fffff808`a1ff0408 00000000`00000010 00000000`00000246 : VerifierExt!IofCallDriver_internal_wrapper+0x13
ffffc28e`d48a6e10 fffff803`32ac2ab8 : ffffc28e`00000001 ffffc28e`d48a6e68 ffffd381`89eecee0 ffff9006`d365c150 : nt!VerifierIofCallDriver+0x21
ffffc28e`d48a6e50 fffff803`32ac2f76 : 00000000`00000000 fffff808`a20ba140 fffff808`a20ba140 ffff9006`d3844010 : nt!ViGenericDispatchHandler+0x54
ffffc28e`d48a6e90 fffff803`323f902a : 00000000`00000000 fffff803`32ab07c0 ffffd381`00000000 ffffd381`00000000 : nt!ViGenericSystemControl+0x16
ffffc28e`d48a6ec0 fffff803`32aa4d29 : ffffd381`89eecd80 ffff9006`d317e810 ffff9006`d34c0f40 fffff803`32aaf77e : nt!IopfCallDriver+0x56
ffffc28e`d48a6f00 fffff803`32466123 : ffffd381`89eecd80 00000000`00000000 ffff9006`d388d2f0 ffff9006`d3844010 : nt!IovCallDriver+0x275
ffffc28e`d48a6f40 fffff803`32ac328b : ffffd381`89eecd80 00000000`00000000 ffff9006`d388d2f0 fffff808`a20ba140 : nt!IofCallDriver+0x199283
ffffc28e`d48a6f80 fffff803`323f902a : ffff9006`d388d440 ffffd381`89eecd80 ffffd381`00000000 ffffd381`00000000 : nt!ViFilterDispatchGeneric+0xbb
ffffc28e`d48a6fc0 fffff803`32aa4d29 : ffffd381`89eecd80 ffff9006`d388d2f0 00000000`00000000 ffff9006`d377a000 : nt!IopfCallDriver+0x56
ffffc28e`d48a7000 fffff803`324a7263 : ffff9006`d38971b0 00000000`00000017 ffff9006`d3897060 ffff9006`d34c0f40 : nt!IovCallDriver+0x275
ffffc28e`d48a7040 fffff808`9aac53b3 : 00000000`00000000 fffff803`32aa7b1b 00000000`c00000bb 00000000`00000000 : nt!IofCallDriverSpecifyReturn+0xae2b3
ffffc28e`d48a7070 fffff803`32ab25f1 : 632e312d`41434449 34a036a0`38306c72 2f3a7074`74683286 69642e34`6c72632f : VerifierExt!IofCallDriver_internal_wrapper+0x13
ffffc28e`d48a70a0 fffff808`a20a76a2 : fffff808`9ad86010 00000000`00000000 fffffb80`00000000 fffff803`324f7691 : nt!VerifierIofCallDriver+0x21
ffffc28e`d48a70e0 fffff808`a20a7872 : ffffd381`89eecd80 ffffd381`89eecd80 00000000`00000000 ffffd381`89eecd80 : HIDCLASS!HidpCallDriver+0xa2
ffffc28e`d48a7150 fffff808`a20c5237 : ffff9006`d38971b0 ffff9006`d365c010 ffffd381`89eecf28 fffff803`32ac328b : HIDCLASS!HidpIrpMajorDefault+0x102
ffffc28e`d48a71b0 fffff808`a20a456d : ffff9006`00000002 ffff9006`d38971d0 00000000`00000004 ffff9006`d38971b0 : HIDCLASS!HidpIrpMajorSystemControl+0x5b
ffffc28e`d48a71e0 fffff803`32ac2ab8 : 00000000`00000017 00000000`00000000 ffff9006`d3829c00 ffff9006`d365c240 : HIDCLASS!HidpMajorHandler+0x290d
ffffc28e`d48a7270 fffff803`32ac2f76 : 00000000`00000000 00000000`00000000 00000000`00000001 ffff9006`d3829c00 : nt!ViGenericDispatchHandler+0x54
ffffc28e`d48a72b0 fffff803`323f902a : 00000000`00000000 fffff803`32ab07c0 ffffd381`00000000 ffffd381`00000000 : nt!ViGenericSystemControl+0x16
ffffc28e`d48a72e0 fffff803`32aa4d29 : ffffd381`89eecd80 ffff9006`d3897060 ffff9006`d2bf32d0 fffff803`32aaf77e : nt!IopfCallDriver+0x56
ffffc28e`d48a7320 fffff803`32466123 : ffffd381`89eecd80 00000000`00000000 ffff9006`d3898040 ffff9006`d3829c00 : nt!IovCallDriver+0x275
ffffc28e`d48a7360 fffff803`32ac328b : ffffd381`89eecd80 00000000`00000000 ffff9006`d3898040 00000000`00000000 : nt!IofCallDriver+0x199283
ffffc28e`d48a73a0 fffff803`323f902a : ffff9006`d3898190 ffffd381`89eecd80 ffffd381`00000001 ffffd381`00000001 : nt!ViFilterDispatchGeneric+0xbb
ffffc28e`d48a73e0 fffff803`32aa4d29 : ffffd381`89eecd80 ffff9006`d3898040 00000000`00000001 fffff803`32ab0cb9 : nt!IopfCallDriver+0x56
ffffc28e`d48a7420 fffff803`32466123 : ffffd381`89eecd80 ffff9006`d3898040 00000000`00000000 ffff9006`d2bf32d0 : nt!IovCallDriver+0x275
ffffc28e`d48a7460 fffff803`32ab0c15 : ffff9006`d317e810 ffffc28e`d48a7689 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x199283
ffffc28e`d48a74a0 fffff803`32ac112a : ffff9006`d317e810 ffffc28e`d48a7689 00000000`00000001 ffff9006`d317e810 : nt!VfIrpSendSynchronousIrp+0x109
ffffc28e`d48a7510 fffff803`32ab5e8c : 00000000`00000000 ffffc28e`d48a7689 00000000`00000001 ffff9006`d317e810 : nt!VfWmiTestStartedPdoStack+0x5a
ffffc28e`d48a75b0 fffff803`323d7c4f : 00000000`00000000 ffffc28e`d48a7689 00000000`00000001 00000000`00000000 : nt!VfMajorTestStartedPdoStack+0x58
ffffc28e`d48a75e0 fffff803`3285eb12 : 00000000`00000000 ffffc28e`d48a7689 00000000`00000001 ffffc28e`d48a7689 : nt!PpvUtilTestStartedPdoStack+0x17
ffffc28e`d48a7610 fffff803`32862258 : ffff9006`d33b4690 ffffc28e`00000001 00000000`00000000 00000000`00000000 : nt!PipProcessStartPhase3+0xc2
ffffc28e`d48a76f0 fffff803`32869b8a : ffff9006`d3775b90 ffffc28e`d48a7a19 00000000`00000010 fffff803`32869b08 : nt!PipProcessDevNodeTree+0x3d0
ffffc28e`d48a7970 fffff803`323dbf1b : ffff9001`00000003 ffff9006`c343a810 ffff9006`d3775b90 00000000`00000000 : nt!PiProcessReenumeration+0x82
ffffc28e`d48a79c0 fffff803`322e8e35 : ffff9006`c3562700 ffff9006`c34b0010 fffff803`32658da0 ffff9006`c34b0010 : nt!PnpDeviceActionWorker+0x1eb
ffffc28e`d48a7a80 fffff803`323054f7 : ffff9006`c3562700 00000000`00000080 ffff9006`c34b8040 ffff9006`c3562700 : nt!ExpWorkerThread+0xf5
ffffc28e`d48a7b10 fffff803`324427f6 : ffffc380`5ffbf180 ffff9006`c3562700 fffff803`323054b0 312e302e`30317e7e : nt!PspSystemThreadStartup+0x47
ffffc28e`d48a7b60 00000000`00000000 : ffffc28e`d48a8000 ffffc28e`d48a1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: de01f4235fdbc9755248d940d6cb139534085dcc

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 4588b07b25c520c6c35b2c120c4cdb977a3f2062

THREAD_SHA1_HASH_MOD: d4805119c5fae2f7bd376c36487c7fbf7dbdaf7c

FAULT_INSTR_CODE: 8bcb8b48

SYMBOL_STACK_INDEX: 10

SYMBOL_NAME: HIDCLASS!HidpCallDriver+a2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME: HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17134.1

STACK_COMMAND: .cxr 0xffffc28ed48a6370 ; kb

BUCKET_ID_FUNC_OFFSET: a2

FAILURE_BUCKET_ID: AV_HIDCLASS!HidpCallDriver

BUCKET_ID: AV_HIDCLASS!HidpCallDriver

PRIMARY_PROBLEM_CLASS: AV_HIDCLASS!HidpCallDriver

TARGET_TIME: 2018-09-24T03:42:05.000Z

OSBUILD: 17134

OSSERVICEPACK: 285

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-08-30 22:15:01

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17134.285

ANALYSIS_SESSION_ELAPSED_TIME: b81

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_hidclass!hidpcalldriver

FAILURE_ID_HASH: {09223f76-66f9-c8bc-7ce8-d669ecd11026}

Followup: MachineOwner


and this one


SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff802200b68d1, The address that the exception occurred at
Arg3: fffffe0407fa6b28, Exception Record Address
Arg4: fffffe0407fa6370, Context Record Address

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17134.285 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1302

BIOS_DATE: 03/15/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: PRIME Z270-A

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff802200b68d1

BUGCHECK_P3: fffffe0407fa6b28

BUGCHECK_P4: fffffe0407fa6370

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

FAULTING_IP:
nt!IovpValidateDeviceObject+5
fffff802`200b68d1 66833903 cmp word ptr [rcx],3

EXCEPTION_RECORD: fffffe0407fa6b28 -- (.exr 0xfffffe0407fa6b28)
ExceptionAddress: fffff802200b68d1 (nt!IovpValidateDeviceObject+0x0000000000000005)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000046dc232
Attempt to read from address 00000000046dc232

CONTEXT: fffffe0407fa6370 -- (.cxr 0xfffffe0407fa6370)
rax=ffff8f010ea9cd80 rbx=ffff8f010ea9cd80 rcx=00000000046dc232
rdx=0000000000000000 rsi=00000000046dc232 rdi=ffffb88e8e280e00
rip=fffff802200b68d1 rsp=fffffe0407fa6d68 rbp=fffff802200d3ab8
r8=0000000000000000 r9=0000000000000000 r10=fffff802200e67c0
r11=0000000000000000 r12=fffff80ac3bea140 r13=fffff80ac3bea140
r14=0000000000000000 r15=0000000000400000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!IovpValidateDeviceObject+0x5:
fffff802`200b68d1 66833903 cmp word ptr [rcx],3 ds:002b:00000000`046dc232=????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

FOLLOWUP_IP:
HIDCLASS!HidpCallDriver+a2
fffff80a`c3bd76a2 488bcb mov rcx,rbx

BUGCHECK_STR: AV

READ_ADDRESS: fffff8021fcf0388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
00000000046dc232

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000046dc232

ANALYSIS_SESSION_HOST: TANNER-POLAK

ANALYSIS_SESSION_TIME: 09-24-2018 02:57:24.0159

ANALYSIS_VERSION: 10.0.17134.12 x86fre

LOCK_ADDRESS: fffff8021fc6b4e0 -- (!locks fffff8021fc6b4e0)
Cannot get _ERESOURCE type

Resource @ nt!PiEngineLock (0xfffff8021fc6b4e0) Available
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff8021fc6b4e0
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff802200b5c1e to fffff802200b68d1

STACK_TEXT:
fffffe04`07fa6d68 fffff802`200b5c1e : ffff8f01`0ea9cd80 0a000004`72d28863 ffffb88e`8e7ebf00 ffffb88e`8f1f1af0 : nt!IovpValidateDeviceObject+0x5
fffffe04`07fa6d70 fffff802`1fab8263 : 00000000`00000017 00000000`00000000 ffffb88e`8f1f1af0 ffffb88e`8e280e00 : nt!IovCallDriver+0x16a
fffffe04`07fa6db0 fffff80a`bbc453b3 : ffffb88e`8e8642b8 fffff802`200cf613 fffff802`200d428b ffffb88e`8e864010 : nt!IofCallDriverSpecifyReturn+0xae2b3
fffffe04`07fa6de0 fffff802`200c35f1 : ffffb88e`8f0186a0 fffff802`200c077e ffff8f01`0ea9cee0 ffff8f01`0ea9cee0 : VerifierExt!IofCallDriver_internal_wrapper+0x13
fffffe04`07fa6e10 fffff802`200d3ab8 : fffffe04`00000001 fffffe04`07fa6e68 ffff8f01`0ea9cee0 ffffb88e`8e864150 : nt!VerifierIofCallDriver+0x21
fffffe04`07fa6e50 fffff802`200d3f76 : 00000000`00000000 fffff80a`c3bea140 fffff80a`c3bea140 ffffb88e`8f0186a0 : nt!ViGenericDispatchHandler+0x54
fffffe04`07fa6e90 fffff802`1fa0a02a : 00000000`00000000 fffff802`200c17c0 ffff8f01`00000000 ffff8f01`00000000 : nt!ViGenericSystemControl+0x16
fffffe04`07fa6ec0 fffff802`200b5d29 : ffff8f01`0ea9cd80 ffffb88e`8f1f1af0 ffffb88e`8daee1c0 fffff802`200c077e : nt!IopfCallDriver+0x56
fffffe04`07fa6f00 fffff802`1fa77123 : ffff8f01`0ea9cd80 00000000`00000000 ffffb88e`8e5df440 ffffb88e`8f0186a0 : nt!IovCallDriver+0x275
fffffe04`07fa6f40 fffff802`200d428b : ffff8f01`0ea9cd80 00000000`00000000 ffffb88e`8e5df440 fffff80a`c3bea140 : nt!IofCallDriver+0x199283
fffffe04`07fa6f80 fffff802`1fa0a02a : ffffb88e`8e5df590 ffff8f01`0ea9cd80 ffff8f01`00000000 ffff8f01`00000000 : nt!ViFilterDispatchGeneric+0xbb
fffffe04`07fa6fc0 fffff802`200b5d29 : ffff8f01`0ea9cd80 ffffb88e`8e5df440 00000000`00000000 ffffb88e`8f0b4000 : nt!IopfCallDriver+0x56
fffffe04`07fa7000 fffff802`1fab8263 : ffffb88e`8f1b41b0 00000000`00000017 ffffb88e`8f1b4060 ffffb88e`8daee1c0 : nt!IovCallDriver+0x275
fffffe04`07fa7040 fffff80a`bbc453b3 : 00000000`00000000 fffff802`200b8b1b 00000000`c00000bb 00000000`00000000 : nt!IofCallDriverSpecifyReturn+0xae2b3
fffffe04`07fa7070 fffff802`200c35f1 : 632e312d`41434449 34a036a0`38306c72 2f3a7074`74683286 69642e34`6c72632f : VerifierExt!IofCallDriver_internal_wrapper+0x13
fffffe04`07fa70a0 fffff80a`c3bd76a2 : fffff80a`bbf06010 00000000`00000000 ffffb400`00000000 fffff802`1fb08691 : nt!VerifierIofCallDriver+0x21
fffffe04`07fa70e0 fffff80a`c3bd7872 : ffff8f01`0ea9cd80 ffff8f01`0ea9cd80 00000000`00000000 ffff8f01`0ea9cd80 : HIDCLASS!HidpCallDriver+0xa2
fffffe04`07fa7150 fffff80a`c3bf5237 : ffffb88e`8f1b41b0 ffffb88e`8e864010 ffff8f01`0ea9cf28 fffff802`200d428b : HIDCLASS!HidpIrpMajorDefault+0x102
fffffe04`07fa71b0 fffff80a`c3bd456d : ffffb88e`00000002 ffffb88e`8f1b41d0 00000000`00000004 ffffb88e`8f1b41b0 : HIDCLASS!HidpIrpMajorSystemControl+0x5b
fffffe04`07fa71e0 fffff802`200d3ab8 : 00000000`00000017 00000000`00000000 ffffb88e`8f0b1da0 ffffb88e`8e864240 : HIDCLASS!HidpMajorHandler+0x290d
fffffe04`07fa7270 fffff802`200d3f76 : 00000000`00000000 00000000`00000000 00000000`00000001 ffffb88e`8f0b1da0 : nt!ViGenericDispatchHandler+0x54
fffffe04`07fa72b0 fffff802`1fa0a02a : 00000000`00000000 fffff802`200c17c0 ffff8f01`00000000 ffff8f01`00000000 : nt!ViGenericSystemControl+0x16
fffffe04`07fa72e0 fffff802`200b5d29 : ffff8f01`0ea9cd80 ffffb88e`8f1b4060 ffffb88e`8dc8d350 fffff802`200c077e : nt!IopfCallDriver+0x56
fffffe04`07fa7320 fffff802`1fa77123 : ffff8f01`0ea9cd80 00000000`00000000 ffffb88e`8eac1040 ffffb88e`8f0b1da0 : nt!IovCallDriver+0x275
fffffe04`07fa7360 fffff802`200d428b : ffff8f01`0ea9cd80 00000000`00000000 ffffb88e`8eac1040 00000000`00000000 : nt!IofCallDriver+0x199283
fffffe04`07fa73a0 fffff802`1fa0a02a : ffffb88e`8eac1190 ffff8f01`0ea9cd80 ffff8f01`00000001 ffff8f01`00000001 : nt!ViFilterDispatchGeneric+0xbb
fffffe04`07fa73e0 fffff802`200b5d29 : ffff8f01`0ea9cd80 ffffb88e`8eac1040 00000000`00000001 fffff802`200c1cb9 : nt!IopfCallDriver+0x56
fffffe04`07fa7420 fffff802`1fa77123 : ffff8f01`0ea9cd80 ffffb88e`8eac1040 00000000`00000000 ffffb88e`8dc8d350 : nt!IovCallDriver+0x275
fffffe04`07fa7460 fffff802`200c1c15 : ffffb88e`8f1f1af0 fffffe04`07fa7689 00000000`00000000 fffffe04`00000000 : nt!IofCallDriver+0x199283
fffffe04`07fa74a0 fffff802`200d212a : ffffb88e`8f1f1af0 fffffe04`07fa7689 00000000`00000001 ffffb88e`8f1f1af0 : nt!VfIrpSendSynchronousIrp+0x109
fffffe04`07fa7510 fffff802`200c6e8c : 00000000`00000000 fffffe04`07fa7689 00000000`00000001 ffffb88e`8f1f1af0 : nt!VfWmiTestStartedPdoStack+0x5a
fffffe04`07fa75b0 fffff802`1f9e8c4f : 00000000`00000000 fffffe04`07fa7689 00000000`00000001 00000000`00000000 : nt!VfMajorTestStartedPdoStack+0x58
fffffe04`07fa75e0 fffff802`1fe6fb12 : 00000000`00000000 fffffe04`07fa7689 00000000`00000001 fffffe04`07fa7689 : nt!PpvUtilTestStartedPdoStack+0x17
fffffe04`07fa7610 fffff802`1fe73258 : ffffb88e`8e555d20 fffffe04`00000001 00000000`00000000 00000000`00000000 : nt!PipProcessStartPhase3+0xc2
fffffe04`07fa76f0 fffff802`1fe7ab8a : ffffb88e`8f0348b0 fffffe04`07fa7a19 00000000`00000010 fffff802`1fe7ab08 : nt!PipProcessDevNodeTree+0x3d0
fffffe04`07fa7970 fffff802`1f9ecf1b : ffffb801`00000003 ffffb88e`7e83ad20 ffffb88e`8f0348b0 00000000`00000000 : nt!PiProcessReenumeration+0x82
fffffe04`07fa79c0 fffff802`1f8f9e35 : ffffb88e`8d911040 ffffb88e`7e8c8010 fffff802`1fc69da0 ffffb88e`00002000 : nt!PnpDeviceActionWorker+0x1eb
fffffe04`07fa7a80 fffff802`1f9164f7 : ffffb88e`8d911040 00000000`00000080 ffffb88e`7e8b8040 ffffb88e`8d911040 : nt!ExpWorkerThread+0xf5
fffffe04`07fa7b10 fffff802`1fa537f6 : ffffde80`a1886180 ffffb88e`8d911040 fffff802`1f9164b0 0cca0cba`0caa0c7a : nt!PspSystemThreadStartup+0x47
fffffe04`07fa7b60 00000000`00000000 : fffffe04`07fa8000 fffffe04`07fa1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: de01f4235fdbc9755248d940d6cb139534085dcc

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 4588b07b25c520c6c35b2c120c4cdb977a3f2062

THREAD_SHA1_HASH_MOD: d4805119c5fae2f7bd376c36487c7fbf7dbdaf7c

FAULT_INSTR_CODE: 8bcb8b48

SYMBOL_STACK_INDEX: 10

SYMBOL_NAME: HIDCLASS!HidpCallDriver+a2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME: HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17134.1

STACK_COMMAND: .cxr 0xfffffe0407fa6370 ; kb

BUCKET_ID_FUNC_OFFSET: a2

FAILURE_BUCKET_ID: AV_HIDCLASS!HidpCallDriver

BUCKET_ID: AV_HIDCLASS!HidpCallDriver

PRIMARY_PROBLEM_CLASS: AV_HIDCLASS!HidpCallDriver

TARGET_TIME: 2018-09-24T03:38:59.000Z

OSBUILD: 17134

OSSERVICEPACK: 285

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-08-30 22:15:01

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17134.285

ANALYSIS_SESSION_ELAPSED_TIME: cdc

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_hidclass!hidpcalldriver

FAILURE_ID_HASH: {09223f76-66f9-c8bc-7ce8-d669ecd11026}

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

I hope this helps.
 
both were access violations coming out of a human interface driver subsystem.
in one case the address looked like a valid kernel address but was not, in the other case the address looked like a user mode address and was invalid.

it is hard to determine the cause without looking at a kernel dump with the windows debugger.

you might put your device on a usb 2.x port to see if it has any effect. (if you have them on a usb 3 port, I can not tell without looking at the kernel dump)

looks like the windows plug and play detected a device and started to add it to the device list but verifier found a problem in the call and called a bugcheck.



 


Well those are the dump files but I found a program who crashed and that sort of tells me what happened. I did move my headset to a USB 2.0 because I played pubg an started framing a little and got a crackle noise but moving it fixed it. I still feel like if I play league after 3 hours it will bsod if not today then tomorrow.
 
you can google "how to force a memory dump using a keyboard" then make the registry change, set the system to produce a kernel memory dump. then force a memory dump. Then copy the kernel memory dump from c:\windows\memory.dmp to a cloud server, share the file for public access and post a link.

I can look at internal logs with the windows debugger. often the problems will show up hours before the system actually crashes.




 
file is going to be big. you might want to zip the file to reduce the size.
kernel dump will be 600Mb to 1.2 Gb. a complete dump will also dump your user mode files in memory.
windows pre loads a lot of programs into standby memory so the complete dump may be very large.
you might consider downloading rammap64.exe and clearing your standby lists (select the empty menu items, to clear the preloaded file list) https://docs.microsoft.com/en-us/sysinternals/downloads/rammap




 
the manual crash will still have the internal error logs if you want me to take a look at it. just make sure it runs for at least 5 to 20 minutes before you force the bugcheck.



 


Yeah if you can that would be great.
 


So it didn't crash for awhile, then it crashed again with league of legends only. But it didn't bsod it just froze my screen and I had to manually shut it off. I did just update my driver with geforce updater but idk I played for like 3 days straight with no issue. The only issue I had with freezing was it froze as I stopped my stream when I hit the button. Not during league, but it instantly reset, but no bsod there either.
 
I'm not sure how to get that to you because now when it bsods it won't restart so when I turn it off it corrupts the dump file. Even when I ran driver verifier it wouldn't restart after bsod. This recent ladfgss.sys bsod wasn't through league though it was just random while I was working on HTML homework.
 
you might go here and get autoruns64.exe
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
run it and go to the menu and hide the microsoft entries
then look at the remaining entries. you can disable 3rd party entries by unchecking the checkbox by the driver.
then you can reboot and that driver will not be loaded.
you can then check it again and reboot to get the driver to load again.

or you can delete the driver entry to remove it from loading permanently.
it is very useful for finding drivers that you did not know were loaded.

if you do get a valid memory dump you would have to copy it to a server like Microsoft onedrive, share the file for public access and post a link. problems that involve devices that are on the usb bus or are plug and play related often will require a kernel memory dump since the minimemory dump does not include the internal error log or the proper debug info to debug the more complex problems.