Windows 10 3 errors BSDO!

[claudiocesar]

I have o Windows 10 PRO 64bits. I replaced new motherboard (ASUS M5A78L-M/USB3 to M5A97 R2.0).

I ran memtest86.
I ran sfc/scannow and chkdsk.
I tested stress CPU + GPU for 30 mins.

Without errors!

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DA, {504, ffffaed7c0283bf8, 40, 5077f}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption

Hi,
as your probably aware 2 of the dump files blamed memory management sometimes caused by either bad ram or drivers. The above bugcheck is caused by a driver which you can determine by a slight change in the registry:
Please create a system restore point before trying the change below:

A driver has corrupted system PTEs.
Set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes
to a DWORD 3 value and reboot.  If the same bugcheck occurs again the stack trace will
identify the offending driver.

If the above doesn't work then we could try what's called the driver verifier.

In order to run the verifer you will also need a recovery disk/USB.
https://support.microsoft.com/en-gb/help/4026852/windows-create-a-recovery-drive

This is just in case the verifier causes a blue screen loop on start up. If it does you can then use the recovery disk/usb to boot into the recovery console, enable safe mode and then turn the verifier off. Hopefully by that point the culprit will have been caught and written on the dump file.
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista

Lastly this issue is often caused by a driver as i wrote above. When updating your drivers did you use an application or did you go find them yourself?
Third party driver finding apps can often cause more issues than cure and your better off getting the drivers straight from the support page:
M5A97 R2.0 | Motherboards | ASUS United Kingdom


Please post any new dumps resulting from the above testing.

 

[claudiocesar]

I not find!

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes​

 

[kemical]

I not find!

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes

Hi Claudiocesar,
What couldn't you find? Remember that the more information you can give us the better.

 

[claudiocesar]

Hi Claudiocesar,
What couldn't you find? Remember that the more information you can give us the better.

I will make Driver verifier.

 

[kemical]

Ok, sounds good. Please remember about this:

In order to run the verifer you will also need a recovery disk/USB.
https://support.microsoft.com/en-gb/help/4026852/windows-create-a-recovery-drive

Hope all goes well. Please post any resulting dump files.