PC hangs while gaming, with loud noise to boot.

[TooMuchStarbucks]

Hello guys. For the sake of brevity, my PC has begun to infinitely hang while I'm on a game that puts a decent load on the system, say WoW with sumpersampling. I have to hold the power button for it to stop, and when I try turning it back on my PC goes into a sort of infinite loop of turning on for a second, then turning off, and so on. In order to stop this I have to actually turn off my PSU, and then for whatever reason, disconnect a device such as a video cable or USB device. After doing that it'll boot up until of course the next crash.

Something to note was that my computer was actually blue screening about a month ago, which of course, it isn't now. It would do so under similar circumstances. I unfortunately forgot the actual error codes they displayed, if they would even since sometimes they didn't and my system would just shut down. I remember using the Windows driver verifier manager, but all that did is make my PC CONSTANTLY BSOD, even when I removed the driver it was referencing. Like if the log listed a driver from my antivirus as the problem, and I removed that, it would just BSOD again and the log would reference some other driver.

After that I just decided to nuke the thing and reinstall Windows 10 altogether. Here we are now. Since I haven't found out how to put my system specs up on here, here they are.

Motherboard: MSI Z97 Gaming 5
CPU: Intel i7 4790K
GPU: EVGA GTX 980SC
RAM: G.Skill Sniper Series 16GB (2x 8GB)
PSU: Corsair CX750M
SSD: Samsung 840
HDD: 1 WD 280GB Velociraptor and 1 WD 300GB Blue drive
CPU Cooling: CoolerMaster Hyper 212 Evo

I really appreciate any help given!

 

[logainofhades]

That is not a very good PSU, and could be causing your problems. The CX line in general isn't very good, but the CX750 is the worst of the bunch. I do recommend getting a better unit, tier 1 or 2, regardless of outcome. http://www.tomshardware.com/forum/id-2547993/psu-tier-list.html


With that said, I would check the health of those drives, using this. http://crystalmark.info/download/index-e.html

Use this to check your ram.
http://www.memtest86.com/download.htm

Considering you did a fresh install, those three things would be my primes suspects for continued BSOD.

 

[TooMuchStarbucks]

That is not a very good PSU, and could be causing your problems. The CX line in general isn't very good, but the CX750 is the worst of the bunch. I do recommend getting a better unit, tier 1 or 2, regardless of outcome. http://www.tomshardware.com/forum/id-2547993/psu-tier-list.html


With that said, I would check the health of those drives, using this. http://crystalmark.info/download/index-e.html

Use this to check your ram.
http://www.memtest86.com/download.htm

Considering you did a fresh install, those three things would be my primes suspects for continued BSOD.

Heya! Thanks for the reply!

The PSU does seem like a reason. I've looked up other scenarios where others have had similar problems and a faulty PSU pops up as the cause frequently.

Which one of the Crystalmark applications should I install for checking my storage drives?

Finally, while at work I tested one of my 8GB sticks for 8 hours with Memtest, with no errors showing up. Throughout the night I'll do the same for my other stick.

 

[logainofhades]

I just use the latest standard edition.

 

[TooMuchStarbucks]

I just use the latest standard edition.

Alrighty then. I went ahead and purchased a 850w Hydro G from FSP after both looking at the list and seeing reviews.

I've also tested the other stick of RAM with no errors, and CrystalDiskInfo shows all of my drives as being in a good health status.

For now I'm just waiting for the PSU to arrive.

 

[TooMuchStarbucks]

Unfortunately, I'm back to say that the power supply wasn't the issue. PC is still showing the same problems. However, before it shut down and started the 'pattern' again there was an actual blue screen. It only appeared for like 2 seconds and unfortunately there's no DMP file to help.

https://4st.me/NqHW6.png is currently the debugging settings I use.

 

[logainofhades]

See if you can do a system restore, back to the time before this started happening.

 

[TooMuchStarbucks]

See if you can do a system restore, back to the time before this started happening.

These problems preceded even my last Windows reinstallation altogether, and this problem in particular has been happening pretty much since I reinstalled Windows, so even the earlier restore points wouldn't really help sadly.

 

[logainofhades]

Remove the GPU, and try using your system, with just the integrated graphics.

 

[TooMuchStarbucks]

Got my PC to blue screen while gaming.

WhoCrashed report: https://www.dropbox.com/s/4s43xcsbvz094v1/WhoCrashedOutput.htm?dl=0

WinDbg:

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


Loading Dump File [C:\Windows\Minidump\040516-5937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
Machine Name:
Kernel base = 0xfffff801`29a1d000 PsLoadedModuleList = 0xfffff801`29cfbcd0
Debug session time: Tue Apr 5 20:48:03.772 2016 (UTC - 4:00)
System Uptime: 1 days 11:13:53.445
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff80061e6b887, fffff80129db0740, ffffe0012657eeb0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : USBXHCI.SYS ( USBXHCI!Isoch_RetrieveNextStage+187 )

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

0: 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: fffff80061e6b887, The address that the exception occurred at
Arg3: fffff80129db0740, Parameter 0 of the exception
Arg4: ffffe0012657eeb0, Parameter 1 of the exception

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7917

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: V1.13

BIOS_DATE: 02/16/2016

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z97 GAMING 5 (MS-7917)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff80061e6b887

BUGCHECK_P3: fffff80129db0740

BUGCHECK_P4: ffffe0012657eeb0

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

FAULTING_IP:
Wdf01000!FxIoQueue::GetRequest+1c7 [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 1129]
fffff800`61e6b887 0fb64718 movzx eax,byte ptr [rdi+18h]

EXCEPTION_PARAMETER1: fffff80129db0740

EXCEPTION_PARAMETER2: ffffe0012657eeb0

BUGCHECK_STR: 0x1E_c000001d

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-VTT6VQ7

ANALYSIS_SESSION_TIME: 04-05-2016 21:10:21.0358

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

EXCEPTION_RECORD: 000000000000000d -- (.exr 0xd)
Cannot read Exception record @ 000000000000000d

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

LAST_CONTROL_TRANSFER: from fffff80129bdcafe to fffff80129b5f760

FAILED_INSTRUCTION_ADDRESS:
Wdf01000!FxIoQueue::GetRequest+1c7 [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 1129]
fffff800`61e6b887 0fb64718 movzx eax,byte ptr [rdi+18h]

STACK_TEXT:
fffff801`2bde12e8 fffff801`29bdcafe : 00000000`0000001e ffffffff`c000001d fffff800`61e6b887 fffff801`29db0740 : nt!KeBugCheckEx
fffff801`2bde12f0 fffff801`29b6580d : fffff801`29d4e000 fffff801`29a1d000 0004c758`007cc000 ffffe001`26750000 : nt!KiFatalExceptionHandler+0x22
fffff801`2bde1330 fffff801`29a22139 : 00000000`00000000 00000000`000000e9 fffff801`2bde1930 fffff800`66a6993d : nt!RtlpExecuteHandlerForException+0xd
fffff801`2bde1360 fffff801`29a205a8 : fffff801`2bde2278 fffff801`2bde1f90 fffff801`2bde2278 fffff800`00000001 : nt!RtlDispatchException+0x429
fffff801`2bde1a60 fffff801`29b6a3c2 : 00000000`0000000d ffffe001`2916d980 00000000`00000002 00000000`00000001 : nt!KiDispatchException+0x144
fffff801`2bde2140 fffff801`29b680c6 : 00000000`00000000 fffff801`29af7e8b 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff801`2bde2320 fffff800`61e6b887 : ffffe001`232ba9c0 fffff801`2bde2558 ffffe001`232baa80 fffff801`2bde2560 : nt!KiInvalidOpcodeFault+0x106
fffff801`2bde24b0 fffff800`61e95654 : fffff801`2bde2502 fffff801`2bde25e0 fffff800`6603c260 fffff801`2bde2848 : Wdf01000!FxIoQueue::GetRequest+0x1c7 [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 1129]
fffff801`2bde2530 fffff800`6600cc97 : ffffe001`232ba9c0 ffffe001`232bada0 00000000`00000000 fffff801`2a20a94f : Wdf01000!imp_WdfIoQueueRetrieveNextRequest+0x44 [d:\th\minkernel\wdf\framework\shared\irphandlers\io\fxioqueueapi.cpp @ 663]
fffff801`2bde2560 fffff800`66002f69 : 00000000`00000000 ffffe001`29a7d640 ffffe001`232bada0 fffff800`6603c260 : USBXHCI!Isoch_RetrieveNextStage+0x187
fffff801`2bde25e0 fffff800`66002e6d : ffffe001`232bada0 00000000`00000003 00000000`00000000 fffff801`2bde2848 : USBXHCI!Isoch_MappingLoop+0x79
fffff801`2bde2630 fffff800`6600c3be : ffffe001`232b25b0 ffffe001`232b25b0 00000000`00000000 ffffe001`232bada0 : USBXHCI!Isoch_MapTransfers+0x75
fffff801`2bde2680 fffff800`6600fbd9 : ffffe001`21d40101 fffff800`00000004 ffffe001`232b6600 fffff800`63556818 : USBXHCI!Isoch_ProcessTransferEventWithED1+0x2da
fffff801`2bde2710 fffff800`66003ed7 : 00000000`00000004 fffff801`2bde2818 fffff801`2bde2848 00000000`00000000 : USBXHCI!Endpoint_TransferEventHandler+0x49
fffff801`2bde2770 fffff800`6600aba8 : 00000000`000004c0 ffffe001`265afff8 00000000`00000009 fffff801`29a8bb96 : USBXHCI!UsbDevice_TransferEventHandler+0x87
fffff801`2bde27d0 fffff801`29a8b6a0 : fffff801`29d3cf00 ffffe001`2688f2f0 fffff801`2bde29c0 ffffe001`21d40f44 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0x748
fffff801`2bde28c0 fffff801`29a8adb9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x270
fffff801`2bde2a10 fffff801`29b6251a : 00000000`00000000 fffff801`29d3a180 fffff801`29db0740 ffffe001`22011840 : nt!KiRetireDpcList+0xe9
fffff801`2bde2c60 00000000`00000000 : fffff801`2bde3000 fffff801`2bddd000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: f1b8eeda62a71b45acf74dfc1408b5e169b840fa

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3b96d853fc2f579a1aae71f857cc4bf7e8de42d5

THREAD_SHA1_HASH_MOD: 3771d95f6b64126be289640dd9510a26dca46480

FOLLOWUP_IP:
USBXHCI!Isoch_RetrieveNextStage+187
fffff800`6600cc97 8be8 mov ebp,eax

FAULT_INSTR_CODE: c085e88b

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: USBXHCI!Isoch_RetrieveNextStage+187

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBXHCI

IMAGE_NAME: USBXHCI.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d6a0

IMAGE_VERSION: 10.0.10586.0

BUCKET_ID_FUNC_OFFSET: 187

FAILURE_BUCKET_ID: 0x1E_c000001d_BAD_IP_USBXHCI!Isoch_RetrieveNextStage

BUCKET_ID: 0x1E_c000001d_BAD_IP_USBXHCI!Isoch_RetrieveNextStage

PRIMARY_PROBLEM_CLASS: 0x1E_c000001d_BAD_IP_USBXHCI!Isoch_RetrieveNextStage

TARGET_TIME: 2016-04-06T00:48:03.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

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: 2016-02-24 00:48:00

BUILDDATESTAMP_STR: 160223-1728

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728

ANALYSIS_SESSION_ELAPSED_TIME: 14c01

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c000001d_bad_ip_usbxhci!isoch_retrievenextstage

FAILURE_ID_HASH: {d8d2d5ad-982f-0ed8-4d65-b4d771492dde}

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

I'll remove my GPU tomorrow and try to see what happens.

 

[logainofhades]

If I am reading that correctly, your USB is causing your BSOD. Make sure you have those drivers up to date. Also, try a CMOS reset, on the motherboard.

 

[TooMuchStarbucks]

If I am reading that correctly, your USB is causing your BSOD. Make sure you have those drivers up to date. Also, try a CMOS reset, on the motherboard.

Oddly enough the MSI site lists no USB specific driver for the board, which would lead me to assume it's sorta bundled in with the chipset driver or something. All the other drivers are up to date.

I have also reset the CMOS, and will see if crashes still occur.