Colif :
Every pc I have had apart from my 1st IBM had an Asus motherboard, I haven't had any problems with them. The 10 year old pc I mentioned has an Asus motherboard, Admittedly for a long time I just didn't bother updating drivers as I assumed parts were so old it was a waste of time. I only did it if I had to. Now, on newer pc I try to keep more up to date, as it can still help. If I hadn't got this one last year I probably would have updated to Win 10 on it too, and had so much fun with new drivers.
I know they support things for a long time span so I have to wonder if its AMD that are the ones showing lack of support.
Get an optical drive too, its so much easier to install Win 10 onto a Z170 board with DVD than with USB. It seems to me that motherboard makers don't want us installing anything on their boards as its a fight to even install Win 10 the first time.
Mums pc works but it has some boots where it sits on a blank screen for over 10 minutes and then eventually starts. That would be cause her Radeon is 8 years old and AMD don't even release drivers for cards half that age, so she using the beta Crimson drivers I guess.
Yeah I've already got an optical drive to make it much easier to install it first time through! Still working on a bit of extra cash before purchasing the parts, but I just wanted to keep you up, still no sign of a fix yet, but there were more crashes:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On Fri 5/20/2016 10:07:07 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052016-11484-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF801B78A1997, 0xFFFFD00029205FA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/20/2016 10:07:07 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF801B78A1997, 0xFFFFD00029205FA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5/20/2016 9:08:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052016-11765-01.dmp
This was probably caused by the following module: usbfilter.sys (usbfilter+0x23C6)
Bugcheck code: 0xD1 (0xFFFFF803513C83C5, 0x2, 0x1, 0xFFFFF80016B2C5B3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbfilter.sys
product: AMD USB Filter Driver
company: Advanced Micro Devices
description: AMD USB Filter Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: usbfilter.sys (AMD USB Filter Driver, Advanced Micro Devices).
Google query: Advanced Micro Devices DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 5/14/2016 9:10:53 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051416-13421-01.dmp
This was probably caused by the following module: ladfgss.sys (ladfGSS+0x6F5C)
Bugcheck code: 0xD1 (0xFFFFD000250F03BB, 0x2, 0x1, 0xFFFFF8014009AEA3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ladfgss.sys
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: ladfgss.sys .
Google query: ladfgss.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 5/14/2016 12:22:49 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051316-10796-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT!USBPORT_TxCsqReleaseLock+0x73)
Bugcheck code: 0xD1 (0xFFFFF8006B9C2577, 0x2, 0x1, 0xFFFFF800662BD8C3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 5/13/2016 6:08:09 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051216-13718-01.dmp
This was probably caused by the following module: e1i63x64.sys (e1i63x64+0x14966)
Bugcheck code: 0xD1 (0xFFFFF8006E7B96C8, 0x2, 0x0, 0xFFFFF800EE76332E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\e1i63x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: e1i63x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Oh well I guess I just need to replace my motherboard, I really hope this fixes the problem because it's really frustrating to crash so much in the middle of gaming/talking with friends