I consider myself pretty tech savvy, savvy enough to know when things are going wrong and where to look to resolve them. but this time myself, and my pc hardware major friend are both stumped!
I've tried reseating the apu, reapplying thermal compound, cleaned the barely dirty heatsink, reseated the ram, tested multiple bios settings, underclocking etc.
I have no idea what's going on, Task manager says I only have 1 phys core, 2 logicals, and also says I have 4Gb of ddr3 but I have 8gb in dual channel (no 4Gb are not system-reserved that would be crazy high)
Gaming, League of Legends mind you, a relatively low end game, temps reach 80+ Celsius, no more than 5 FPS is possible, earlier today I was running at 60-120FPS at about 50-60 Celsius.
I have also tried bench marking which returned results far lower than others using the same hardware.
I'm trying to figure out if it's the APU failing or the motherboard, or something else entirely.
All of these problems occurred soon after a BSOD (the atikxxxx.sys BSOD, 2nd dump from the bottom, is where the problems occurred, listed from latest to earliest crash) details provided below:
[/code]
I've tried reseating the apu, reapplying thermal compound, cleaned the barely dirty heatsink, reseated the ram, tested multiple bios settings, underclocking etc.
I have no idea what's going on, Task manager says I only have 1 phys core, 2 logicals, and also says I have 4Gb of ddr3 but I have 8gb in dual channel (no 4Gb are not system-reserved that would be crazy high)
Gaming, League of Legends mind you, a relatively low end game, temps reach 80+ Celsius, no more than 5 FPS is possible, earlier today I was running at 60-120FPS at about 50-60 Celsius.
I have also tried bench marking which returned results far lower than others using the same hardware.
I'm trying to figure out if it's the APU failing or the motherboard, or something else entirely.
All of these problems occurred soon after a BSOD (the atikxxxx.sys BSOD, 2nd dump from the bottom, is where the problems occurred, listed from latest to earliest crash) details provided below:
Code:
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-9KIEEME
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: Gigabyte Technology Co., Ltd., F2A68HM-H
CPU: AuthenticAMD AMD A10-7800 Radeon R7, 12 Compute Cores 4C+8G AMD586, level: 21
2 logical processors, active mask: 3
RAM: 3699568640 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 3/29/2018 9:47:56 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032918-22234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0x139 (0x3, 0xFFFFE48ED2B95580, 0xFFFFE48ED2B954D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 3/29/2018 9:47:56 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x94B9)
Bugcheck code: 0x139 (0x3, 0xFFFFE48ED2B95580, 0xFFFFE48ED2B954D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 3/29/2018 5:42:17 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032918-24968-01.dmp
This was probably caused by the following module: atikmdag.sys (0xFFFFF80AB23D7310)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80AB23D7310, 0xFFFFC200A9A76428, 0xFFFFC200A9A75C70)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys .
Google query: atikmdag.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Thu 3/29/2018 9:02:38 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032918-25468-01.dmp
This was probably caused by the following module: lvrs64.sys (0xFFFFF8001F692FC9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8001F692FC9, 0xFFFFB6826B948768, 0xFFFFB6826B947FB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\lvrs64.sys
product: Logitech Webcam Software
company: Logitech Inc.
description: Logitech Kernel Audio Improvement Filter Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: lvrs64.sys (Logitech Kernel Audio Improvement Filter Driver, Logitech Inc.).
Google query: lvrs64.sys Logitech Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
C++:
[code="actionscript3"]
Facebook
Twitter
Instagram