Changed MOBO, RAM and CPU and now my system FREEZE or shows BSOD

[Rrigarsio]

Supp guys,

A few days back i upgraded my pc from a FX8320 to a I5 6600K, Gigabyte 970A DS3P to Asus Z170 Pro Gaming and 2x4 GSKILL DDR3 to 2x8 Kingston Hyper X Predator 3200.

At first i just used the normal format given by windows 10, instead of a normal format. Installed the GPU drivers again and updated the bios. The first problem i noticed was a freeze while playing TW3, the img just got frozen and the sound gots a noisy loop.

Then, when using Aida64, my system freeze when stressing GPU + Ram + CPU + SystemMem, but it didnt cause any problem when stressing only Ram + cpu + SystemMem. So i decided to clean install everything, but while playing again a BSOD showed up.

The error code was APC_INDEX_MISMATCH, without any number code.

It´s very weird since i was playing normally with everything with the GPU and RAM, CPU and MOBO seems to be fine.


Actual hardware:

Intel I5 6600K
Asus Z170 Pro Gaming
Radeon R9 380X Nitro
Kingston Hyper X Predator 2x8gb DDR4 3200
Aerocool Strike-X 600w

I didn´t OCed anything and i have no clue what´s missing in my system to get ready to play anything. :/

 

[Ironsounds]

Hello... Did you do a New OS install from the AMD system to the New intel system?

 

[Rrigarsio]

Hello... Did you do a New OS install from the AMD system to the New intel system?

Since i didnt have an original CD i just installed it with the Restore (Clean Install) version of my OS from my AMD OS.

But with a Clean Install everything was removed right?

Example

 

[Ironsounds]

Hello... There are different Files that get compiled during the Install procedure, between AMD and intel systems... I would recommend doing a clean/New install with the OS version install media... will only take 15-30 mins (if you have install media) B /

I think this would be the first place to start with your problem B /

 

[johnbl]

generally that bugcheck code would indicate that the BIOS version you have installed does not match the motherboard drivers. (or you have a old and a new motherboard driver installed for the same function)
a gigabyte motherboard driver attempting to call into a ASUS bios would not find the correct functions and would generate this bugcheck (or vice versa) generally it would be a bios extension for functions like super speed USB or maybe a SATA function. just check for drivers that are from the correct motherboard vendor.
SATA and USB drivers for windows should be matched to your BIOS version. Make sure you have all of the motherboard drivers installed to match the bios version

I would update to all of the current motherboard drivers from your motherboard vendors website.
if your system has custom firmware, you should also update it.
if you still get the same bugcheck then you need to look at the driver dates for each driver.
you can do this via two methods: use the driverquery command:
https://technet.microsoft.com/en-us/library/ee851682.aspx

or provide a memory dump and have someone use the windows debugger to dump the list of installed/running drivers on your system. (not many people actually do this)

if you changed the entire hardware without reinstalling windows then you should reinstall. Windows will detect your new hardware and assume that the old hardware is still there and not working. This forces windows to use alternative hardware settings for all of the new hardware detected. It kind of cripples windows by the limitations.

based on the bugcheck code I just assume you have a old motherboard driver installed rather than the current one from the manufacture website. (windows will often install a old driver from the windows update when you actually need one from the motherboard vendor)

 

[Rrigarsio]

generally that bugcheck code would indicate that the BIOS version you have installed does not match the motherboard drivers. (or you have a old and a new motherboard driver installed for the same function)
a gigabyte motherboard driver attempting to call into a ASUS bios would not find the correct functions and would generate this bugcheck (or vice versa) generally it would be a bios extension for functions like super speed USB or maybe a SATA function. just check for drivers that are from the correct motherboard vendor.
SATA and USB drivers for windows should be matched to your BIOS version. Make sure you have all of the motherboard drivers installed to match the bios version

I would update to all of the current motherboard drivers from your motherboard vendors website.
if your system has custom firmware, you should also update it.
if you still get the same bugcheck then you need to look at the driver dates for each driver.
you can do this via two methods: use the driverquery command:
https://technet.microsoft.com/en-us/library/ee851682.aspx

or provide a memory dump and have someone use the windows debugger to dump the list of installed/running drivers on your system. (not many people actually do this)

if you changed the entire hardware without reinstalling windows then you should reinstall. Windows will detect your new hardware and assume that the old hardware is still there and not working. This forces windows to use alternative hardware settings for all of the new hardware detected. It kind of cripples windows by the limitations.

based on the bugcheck code I just assume you have a old motherboard driver installed rather than the current one from the manufacture website. (windows will often install a old driver from the windows update when you actually need one from the motherboard vendor)

I went to the official Asus Z170 website to update all the drivers, now i have all this. Is it right?

https://1drv.ms/u/s!ArltMoWhaQYBhBY6NMLNsGGiH5uT

I guess all these Falses mean that the last ones are not working anymore.

 

[Rrigarsio]

But now, while playing for 10 mins or so to The Witcher 3, i got this error.

On Sun 11/12/2016 22:03:43 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121116-6671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x3D (0xFFFFF80376EACA58, 0xFFFFF80376EAC280, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[johnbl]

no, you want to focus on the dates of the drivers.
the drivers may start up during the boot process then find that no hardware exists for that driver and it then stops. This would be normal operation.

you would look at the dates of the drivers like amdsbs.sys dated 11/12/2012
then go here to see what the driver is for:
http://www.carrona.org/drivers/driver.php?id=amdsbs.sys
in this case it is a older AMD AHCI Compatible Controller driver
but it is much older than your other AMD drivers dated in 2016. I could be a mis matched driver, malware trying to hide as a AMD driver.
sometimes windows update will install a old driver when the OEM does not provide updates.
note: my system has the same amd driver installed with the same date so I don't think it is a problem.

generally that bugcheck code would indicate that the BIOS version you have installed does not match the motherboard drivers. (or you have a old and a new motherboard driver installed for the same function)
a gigabyte motherboard driver attempting to call into a ASUS bios would not find the correct functions and would generate this bugcheck (or vice versa) generally it would be a bios extension for functions like super speed USB or maybe a SATA function. just check for drivers that are from the correct motherboard vendor.
SATA and USB drivers for windows should be matched to your BIOS version. Make sure you have all of the motherboard drivers installed to match the bios version

I would update to all of the current motherboard drivers from your motherboard vendors website.
if your system has custom firmware, you should also update it.
if you still get the same bugcheck then you need to look at the driver dates for each driver.
you can do this via two methods: use the driverquery command:
https://technet.microsoft.com/en-us/library/ee851682.aspx

or provide a memory dump and have someone use the windows debugger to dump the list of installed/running drivers on your system. (not many people actually do this)

if you changed the entire hardware without reinstalling windows then you should reinstall. Windows will detect your new hardware and assume that the old hardware is still there and not working. This forces windows to use alternative hardware settings for all of the new hardware detected. It kind of cripples windows by the limitations.

based on the bugcheck code I just assume you have a old motherboard driver installed rather than the current one from the manufacture website. (windows will often install a old driver from the windows update when you actually need one from the motherboard vendor)

I went to the official Asus Z170 website to update all the drivers, now i have all this. Is it right?

https://1drv.ms/u/s!ArltMoWhaQYBhBY6NMLNsGGiH5uT

I guess all these Falses mean that the last ones are not working anymore.

 

[Rrigarsio]

no, you want to focus on the dates of the drivers.
the drivers may start up during the boot process then find that no hardware exists for that driver and it then stops. This would be normal operation.

you would look at the dates of the drivers like amdsbs.sys dated 11/12/2012
then go here to see what the driver is for:
http://www.carrona.org/drivers/driver.php?id=amdsbs.sys
in this case it is a older AMD AHCI Compatible Controller driver
but it is much older than your other AMD drivers dated in 2016. I could be a mis matched driver, malware trying to hide as a AMD driver.
sometimes windows update will install a old driver when the OEM does not provide updates.
note: my system has the same amd driver installed with the same date so I don't think it is a problem.

generally that bugcheck code would indicate that the BIOS version you have installed does not match the motherboard drivers. (or you have a old and a new motherboard driver installed for the same function)
a gigabyte motherboard driver attempting to call into a ASUS bios would not find the correct functions and would generate this bugcheck (or vice versa) generally it would be a bios extension for functions like super speed USB or maybe a SATA function. just check for drivers that are from the correct motherboard vendor.
SATA and USB drivers for windows should be matched to your BIOS version. Make sure you have all of the motherboard drivers installed to match the bios version

I would update to all of the current motherboard drivers from your motherboard vendors website.
if your system has custom firmware, you should also update it.
if you still get the same bugcheck then you need to look at the driver dates for each driver.
you can do this via two methods: use the driverquery command:
https://technet.microsoft.com/en-us/library/ee851682.aspx

or provide a memory dump and have someone use the windows debugger to dump the list of installed/running drivers on your system. (not many people actually do this)

if you changed the entire hardware without reinstalling windows then you should reinstall. Windows will detect your new hardware and assume that the old hardware is still there and not working. This forces windows to use alternative hardware settings for all of the new hardware detected. It kind of cripples windows by the limitations.

based on the bugcheck code I just assume you have a old motherboard driver installed rather than the current one from the manufacture website. (windows will often install a old driver from the windows update when you actually need one from the motherboard vendor)

I went to the official Asus Z170 website to update all the drivers, now i have all this. Is it right?

https://1drv.ms/u/s!ArltMoWhaQYBhBY6NMLNsGGiH5uT

I guess all these Falses mean that the last ones are not working anymore.

And i am supposed to delete all these old drivers? Sorry for the inconveniences but it´s the first time i experience this bugs.

 

[johnbl]

no, some drivers will be stopped when they are not needed but will be needed for the boot process and for plug and play to work correctly. I would just run with the updates you installed and see if you still get a problem.

no, you want to focus on the dates of the drivers.
the drivers may start up during the boot process then find that no hardware exists for that driver and it then stops. This would be normal operation.

you would look at the dates of the drivers like amdsbs.sys dated 11/12/2012
then go here to see what the driver is for:
http://www.carrona.org/drivers/driver.php?id=amdsbs.sys
in this case it is a older AMD AHCI Compatible Controller driver
but it is much older than your other AMD drivers dated in 2016. I could be a mis matched driver, malware trying to hide as a AMD driver.
sometimes windows update will install a old driver when the OEM does not provide updates.
note: my system has the same amd driver installed with the same date so I don't think it is a problem.

generally that bugcheck code would indicate that the BIOS version you have installed does not match the motherboard drivers. (or you have a old and a new motherboard driver installed for the same function)
a gigabyte motherboard driver attempting to call into a ASUS bios would not find the correct functions and would generate this bugcheck (or vice versa) generally it would be a bios extension for functions like super speed USB or maybe a SATA function. just check for drivers that are from the correct motherboard vendor.
SATA and USB drivers for windows should be matched to your BIOS version. Make sure you have all of the motherboard drivers installed to match the bios version

I would update to all of the current motherboard drivers from your motherboard vendors website.
if your system has custom firmware, you should also update it.
if you still get the same bugcheck then you need to look at the driver dates for each driver.
you can do this via two methods: use the driverquery command:
https://technet.microsoft.com/en-us/library/ee851682.aspx

or provide a memory dump and have someone use the windows debugger to dump the list of installed/running drivers on your system. (not many people actually do this)

if you changed the entire hardware without reinstalling windows then you should reinstall. Windows will detect your new hardware and assume that the old hardware is still there and not working. This forces windows to use alternative hardware settings for all of the new hardware detected. It kind of cripples windows by the limitations.

based on the bugcheck code I just assume you have a old motherboard driver installed rather than the current one from the manufacture website. (windows will often install a old driver from the windows update when you actually need one from the motherboard vendor)

I went to the official Asus Z170 website to update all the drivers, now i have all this. Is it right?

https://1drv.ms/u/s!ArltMoWhaQYBhBY6NMLNsGGiH5uT

I guess all these Falses mean that the last ones are not working anymore.

And i am supposed to delete all these old drivers? Sorry for the inconveniences but it´s the first time i experience this bugs.

 

[Rrigarsio]

no, you want to focus on the dates of the drivers.
the drivers may start up during the boot process then find that no hardware exists for that driver and it then stops. This would be normal operation.

Well, after some updates i definitely found myself in a tricky situation ´cause there is no sign of my old Gigabyte drivers, only this.

Edit; I found out that there is always one 3.1 port that doesn't get my headset, it just appears like disconnected until I unplug it and plug again.

So i tried again with a game and freezes the PC (still powered on but with no img) and needs a force reset. It didnt bring any error in the WhoCrashed, but this is from yesterday night.


On Sun 11/12/2016 22:03:43 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121116-6671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x3D (0xFFFFF80376EACA58, 0xFFFFF80376EAC280, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


2º Edit: I´ve read that some issues could be triggered during a CPU stress test with prime 95, here are my results.

On Mon 12/12/2016 17:40:50 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121216-4265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x139 (0x3, 0xFFFFD300FAA1A4C0, 0xFFFFD300FAA1A418, 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 Mon 12/12/2016 17:40:50 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: 0x139 (0x3, 0xFFFFD300FAA1A4C0, 0xFFFFD300FAA1A418, 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.

 

[Ironsounds]

Hello... The "Kernel" is the compiled file from your Hardware, during your OS install.

 

[Rrigarsio]

Hello... The "Kernel" is the compiled file from your Hardware, during your OS install.

Is there any methow to remove everything from my ssd (for my OS) and the HDD to avoid these files being inherited by the new system?

 

[Ironsounds]

Hello... Do the install with just the a OS drive... Move un-backupable data to the HD and ?... the OS drive just needs the install, your HD and programs/data on it will be un-affected if you un-attaché it during the process. Some programs may need to be re-installed for the NEW OS registry. and permissions. There is a Order to things, and you skipped over a important one, creating the proper OS "kernel" for your hardware.

 

[Rrigarsio]

Hello... Do the install with just the a OS drive... Move un-backupable data to the HD and ?... the OS drive just needs the install, your HD and programs/data on it will be un-affected if you un-attaché it during the process. Some programs may need to be re-installed for the NEW OS registry. and permissions. There is a Order to things, and you skipped over a important one, creating the proper OS "kernel" for your hardware.

I´ll try it tomorrow since i need the pc for some CAD works, ill post the results. Thx!

 

[johnbl]

put your actual memory dump from c:\windows\minidump directory on to a cloud server like Microsoft onedrive, google docs or mediafire. Share the files as public and post a link here.

I can take a quick look in the windows debugger and read why windows shut your system down with the bugcheck.

Hello... Do the install with just the a OS drive... Move un-backupable data to the HD and ?... the OS drive just needs the install, your HD and programs/data on it will be un-affected if you un-attaché it during the process. Some programs may need to be re-installed for the NEW OS registry. and permissions. There is a Order to things, and you skipped over a important one, creating the proper OS "kernel" for your hardware.

I´ll try it tomorrow since i need the pc for some CAD works, ill post the results. Thx!

 

[Rrigarsio]

put your actual memory dump from c:\windows\minidump directory on to a cloud server like Microsoft onedrive, google docs or mediafire. Share the files as public and post a link here.

I can take a quick look in the windows debugger and read why windows shut your system down with the bugcheck.

Hello... Do the install with just the a OS drive... Move un-backupable data to the HD and ?... the OS drive just needs the install, your HD and programs/data on it will be un-affected if you un-attaché it during the process. Some programs may need to be re-installed for the NEW OS registry. and permissions. There is a Order to things, and you skipped over a important one, creating the proper OS "kernel" for your hardware.

I´ll try it tomorrow since i need the pc for some CAD works, ill post the results. Thx!

There you go!

https://1drv.ms/f/s!ArltMoWhaQYBhD5jf6PKXSAKPLdF