New
#21
@MicRouS
What cooling setup do you have for the 9590 (did you also use higher end TIM recommended). Is it oc'd ?
I don't know the answers to any of that because i'm not that educated on this stuff. Sorry
According to the logs there was a new crash dump but no mini-dumps.
Please share the memory.dmp file using OneDrive or Dropbox.Code:Crash dump found at C:\Windows\MEMORY.DMP Creation date: 02/21/2018 21:38:07 Size on disk: 844 MB C:\Windows\Minidump contains no dump files.
Let's hope this works...I have a feeling it's corrupted again knowing my luck.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Also, I've had at least one crash since that was made. I had the beta make another zip and it looks like there actually is one minidump in there. So that might be good news...
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
No the files were not corrupted but the original memory.dmp has been overwritten by the new one.
I have looked at the crash dump which was a SYSTEM_SERVICE_EXCEPTION (3b) bugcheck. There is one misbehaving driver showing up in the threads although not in the process which actually crashed.
ladfGSS.sys Fri Apr 28 14:52:29 2017Code:0 TID:0001 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 00000015`3fcff758 00000000`00000000 0x00007ff7`cf3c9987 *** WARNING: Unable to verify timestamp for ladfGSS.sys *** ERROR: Module load completed but symbols could not be loaded for ladfGSS.sys 1 TID:0002 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 ffffa887`8bc30110 fffff800`bc2a5950 usbaudio!USBHwGetCurrentFrame+0x2 01 ffffa887`8bc30120 fffff800`bc2b7e5b usbaudio!USBCaptureBytePosition+0xb0 02 ffffa887`8bc301c0 fffff800`befb3e05 usbaudio!PropertyGetAudioPositionEx+0x5b 03 ffffa887`8bc30210 fffff800`befc2f81 ks!KspPropertyHandler+0x3e5 04 ffffa887`8bc30280 fffff800`befd2e6e ks!KspHandleAutomationIoControl+0x2e5 05 ffffa887`8bc30300 fffff800`befb3fe5 ks!CKsPin::DispatchDeviceIoControl+0x10e 06 ffffa887`8bc30360 fffff800`bef958e2 ks!KsDispatchIrp+0x55 07 ffffa887`8bc30420 fffff802`18a46669 ks!CKsDevice::PassThroughIrp+0x112 08 ffffa887`8bc30460 fffff800`bc2d53e8 nt!IofCallDriver+0x59 09 ffffa887`8bc304a0 00000000`00000001 ladfGSS+0x53e8 0a ffffa887`8bc304a8 00000000`00000000 0x1 2 TID:0003 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 ffffa887`87e37c38 fffff802`18b8acf2 nt!KiDpcInterrupt 01 ffffa887`87e37c60 00000000`00000000 nt!KiIdleLoop+0x32 3 TID:0004 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 ffffa887`87e45c38 fffff802`18b8acf2 nt!KiDpcInterrupt 01 ffffa887`87e45c60 00000000`00000000 nt!KiIdleLoop+0x32 4 TID:0005 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 00000015`408e7b20 00000000`00000000 0x00007ff7`cfbd82da # 5 TID:0006 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 ffffa887`88739478 fffff802`18b9a529 nt!KeBugCheckEx 01 ffffa887`88739480 fffff802`18b99abc nt!KiBugCheckDispatch+0x69 02 ffffa887`887395c0 fffff802`18b9013d nt!KiSystemServiceHandler+0x7c 03 ffffa887`88739600 fffff802`18ab5a50 nt!RtlpExecuteHandlerForException+0xd 04 ffffa887`88739630 fffff802`18ab65d4 nt!RtlDispatchException+0x430 05 ffffa887`88739d20 fffff802`18b9a60e nt!KiDispatchException+0x144 06 ffffa887`8873a3d0 fffff802`18b96633 nt!KiExceptionDispatch+0xce 07 ffffa887`8873a5b0 ffffc998`dc8916e1 nt!KiPageFault+0x4f3 08 ffffa887`8873a740 ffffc998`dc891140 win32kfull!TimersProc+0x1a1 09 ffffa887`8873a7c0 ffffc998`dcba7a1b win32kfull!RawInputThread+0x790 0a ffffa887`8873aa90 ffffc998`dc83ad7e win32kbase!xxxCreateSystemThreads+0xfb 0b ffffa887`8873aad0 fffff802`18b9a003 win32kfull!NtUserCallNoParam+0x5e 0c ffffa887`8873ab00 00007ffc`18ee1124 nt!KiSystemServiceCopyEnd+0x13 0d 000000ba`7b77f928 00000000`00000000 0x00007ffc`18ee1124 6 TID:0007 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 ffffa887`87e6f678 fffff800`bba98865 amdppm!ReadIoMemRaw+0xe8 01 ffffa887`87e6f680 fffff800`bba975bd amdppm!ReadGenAddr+0x21 02 ffffa887`87e6f6b0 fffff800`bba974f0 amdppm!C2Idle+0x6d 03 ffffa887`87e6f6e0 fffff802`18ada93a amdppm!AcpiCStateIdleExecute+0x20 04 ffffa887`87e6f710 fffff802`18ad9870 nt!PpmIdleExecuteTransition+0xf3a 05 ffffa887`87e6fb00 fffff802`18b8acec nt!PoIdle+0x340 06 ffffa887`87e6fc60 00000000`00000000 nt!KiIdleLoop+0x2c 7 TID:0008 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 ffffa887`87e7d678 fffff800`bba98865 amdppm!ReadIoMemRaw+0xe8 01 ffffa887`87e7d680 fffff800`bba975bd amdppm!ReadGenAddr+0x21 02 ffffa887`87e7d6b0 fffff800`bba974f0 amdppm!C2Idle+0x6d 03 ffffa887`87e7d6e0 fffff802`18ada93a amdppm!AcpiCStateIdleExecute+0x20 04 ffffa887`87e7d710 fffff802`18ad9870 nt!PpmIdleExecuteTransition+0xf3a 05 ffffa887`87e7db00 fffff802`18b8acec nt!PoIdle+0x340 06 ffffa887`87e7dc60 00000000`00000000 nt!KiIdleLoop+0x2c Threads: 8 of 8 Command: knL
The driver is for the Logitech USB Surround sound - possibly to do with your Headset?
Are there any newer drivers for this or could you temporarily remove it to see if it makes a difference?
Yes that would probably be my headset. It has 7.1 surround sound in it. I can't seem to find that driver under either of those names. I've found other ones related to it, though. I tried reinstalling the logitech headset drivers and I still received a red screen about 10 minutes into playing.
Can you confirm if the driver I pointed out has been changed or not? You may need to post a new set of logfiles so that we can check.
Well, since it didn't work when I updated it, I just uninstalled the driver to the USB adapter and plugged the headset straight into the audio jacks instead of using the USB adapter. It didn't crash yesterday, but I'll let you know if it does today.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
just crashed again...no red screen or blue screen. Just a freeze.