https://1drv.ms/f/s!Alb8kThDFSWph0bwuV4s30AFSsAv
Here are my .dmp files fom my pc LiveKernelReports.
And here are my dxdiag
I have done a clean install of the recommended drivers of my R7 360 radeon with the help of an uninstaller program . I can not roll back the drivers because of it and the version of the drivers is 18.9.3. The problem still persists.
Could I have some help with this problem of mine?
1 Solution
Need to supply more information on your computer.: INFORMATION REQUIRED WHEN POSTING A QUESTION
Here is the latest Desktop APU Driver for your A10-7860K from AMD Download: A10-7860K with Radeon™ R7 Series Drivers & Support | AMD
In laptops, the APU driver installs both the integrated and Discrete GPU drivers. But for Desktop APU drivers I don't know if that applies or not. But in case it doesn't here is the latest R7 360 Driver from AMD Download: https://www.amd.com/en/support/graphics/amd-radeon-r7-series/amd-radeon-r7-300-series/amd-radeon-r7-...
NOTE: I would first suggest to install the latest APU driver without installing the R7 360 driver and see if everything is updated including your R7 360 and your GPUs are working correctly.
You need to use this method to install the AMD Driver without conflicts:
install AMD driver:
1) Download the correct AMD Full Set of drivers from AMD Support. Make sure your Windows is fully updated via Windows Update. Windows Must be fully updated because the latest AMD Drivers requires all the latest "Optional" and "Recommended" updates to be installed.
2) Use Windows Uninstall to uninstall current AMD driver and software and disconnect the internet from your computer. Then use DDU (Display Driver Uninstaller) Display Driver Uninstaller (DDU) from Wagnardsoft Forum in Safe Mode. This will eliminate all traces of the AMD driver and software from your computer.
Delete C: \ AMD folder from the Root Directory. Reboot
3) Go to Device Manager and click "Display Adapter" and make sure you are on the MS Basic Display Adapter. If not, uninstall the AMD driver using Properties.
4) Try reinstalling the AMD FULL SET OF DRIVERS that you have downloaded manually. Make sure you disable the Internet to prevent Windows from installing a newer version. So configure windows to prevent it from updating drivers via windows update. So it has been mentioned to disable any anti-virus programs before installing AMD Drivers.
5) If the new AMD drivers installs and works correctly, delete again the C: \ AMD folder from the root directory. To save space on the HDD.
6) Enable both the Internet and Anti-Virus program (if applicable).
7) Go back to Device Manager and check your GPU card driver is working and identified correctly.
Your MiniDump Files indicates that this driver was the cause of your crash - USBPORT.SYS.:
Copied from Mini Dump file:
==================================================
Dump File : 080618-28421-01.dmp
Crash Time : 8/6/2018 3:24:48 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : fffff801`3a272e70
Parameter 3 : 00000000`01aaa4e0
Parameter 4 : fffff801`3d73c912
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+1c912
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+198560
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : D:\Internet Downloads\080618-28421-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 17134
Dump File Size : 870,164
Dump File Time : 11/16/2018 1:45:01 PM
==================================================
From Microsoft about your BSOD Error in the minidump: Bug Check 0x7F UNEXPECTED_KERNEL_MODE_TRAP - Windows drivers | Microsoft Docs
0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:
- A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.
- A hardware problem.
Cause:
Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.
Again from Microsoft concerning your error: UNEXPECTED_KERNEL_MODE_TRAP
Error Message:
UNEXPECTED_KERNEL_MODE_TRAP
Explanation:
This Stop message means that one of two types of problems occurred in kernel-mode, either the kind of condition that the kernel is not allowed to have or catch (a bound trap), or an unrecoverable error. Occasionally, this message can be caused by software problems, but the most common cause is hardware failure. It usually occurs after the installation of faulty or mismatched hardware (especially memory) or in the event that installed hardware fails. Setting the CPU to run at speeds above the rated specification (known as overclocking the CPU) can also cause this error.
User Action:
If hardware was recently added to the system, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner, to determine which hardware component has failed. For details on these procedures, see the owners manual for your computer. Check that all network adapters in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure network adapter contacts are clean. If the error appears on a newly installed system, check the availability of updates for the following: firmware on RISC systems, as well as BIOS revisions on the motherboard, the SCSI controller, or network adapters. Updates of this kind are typically available on the web site or BBS of the hardware manufacturer. Confirm that all hard disks, hard disk controllers, and SCSI adapters are listed on the Microsoft Windows 2000 Hardware Compatibility List (HCL) on http://www.microsoft.com/. If the error occurred after the installation of a new or updated device driver, remove or replace the driver. If, under this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, start the computer using the Recovery Console in order to access the file. Restart your computer, and then press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If the CPU was overclocked, return the CPU to the default clock speed setting. Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver causing the error. Disabling memory caching of the BIOS might also resolve it. If you encountered this error while upgrading to Windows 2000, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners prior to upgrading. Contact the software manufacturer to obtain updates of these tools. Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.
I would run MEMTEST86 to check your memory in case you have a bad RAM MEMORY Module. Also I would uninstall all the AMD Graphics Drivers from your computer and just install the APU Driver by itself and see if you get any more BSODs or error and both your GPUs (integrated and Discrete) are working correctly.
