If driver verifier doesn't crash your system after 48h, stop driver verifier and run hard drive tests. There is no system error when we do a scan and the drivers are all up to date. I decided to do a clean re-install of Windows 10, hoping it would clear up the issues. I did a check and it says they are current. Hopefully I've collected enough info that someone can help me finally figure this bugger out. I'm almost positive that it could be a driver conflict with your wireless card. If DriverVerifier creates a minidump upload it and post the link here so we can analyze it.
I'm running Windows 10 on a Dell Latitude E6410. After upgrading to Windows 10, several buggy things started occurring: 1. It seems to point to the nxusbs. From the callstack I can see that virtual memory operation where done: 00 nt! The data read from storage does not match the original data written. Make sure the vents are clear and that the fans are working.
I did Memtest86+ for 18. I provided a link to the driver details page on Dell's website for that laptop for further details. Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first. I used to have Windows 7 on this system with no issues. Please create a restore point. Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation. See driver update methods below.
Everything I've searched on this is very vague. Run the memory tests see methods below. KiSystemServiceCopyEnd+0x13 0x00007ff9'bbdf37aa 0x00007ff9'bbdf37aa is of particular interest here, because that is what is where the chain of calls originates from. I ran MemTest86 and memory checked out. I have attached some info files. Any insight on what might be causing this? As usual the 0x1A crashes do not reveal any driver possibly causing it, forcing the use of driver verifier to attempt to find any driver. Please follow to run driver verifier.
. It may take some time, but please take the time you need to perform it properly. I used the BlueScreenView program to look at the minidump files and with all of them the driver in the stack at the time of the error is ntoskrnl. If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there. The drivers that start with nx. We upgraded to Windows 10 from Windows 7, using a custom build. Until you have more information, you have way too much possible solutions to try.
Try adding a small fan blowing into the vents as a test. This indicates the data was corrupted by the storage stack, or device hardware. However, there is no information about that because your system is not configured to take : Mini Kernel Dump File: Only registers and stack trace are available It's also not yet guaranteed that every dump you get results in the same, that needs to be verified. It happens both when I'm at the computer and when it's idle. Have you added any hardware lately? It seems to happen every 1-2 days on average. Arg1: 0000000000041201, The subtype of the bugcheck. This indicates that a severe memory management error occurred.
There has been no particular program or activity that seemed to cause it. Please make a backup of your important files and get your rescue media or. I'm not very good at decoding these dumps. Also check with MyEventViewer at the time of the BlueScreen. More dumps that contain more complete information will spare you the hassle to go through all that.
Have you updated any driver just before these started? After restorehealth is successful finished, run sfc twice with a reboot between them, that should completely resolve the corruption. In medical terms, you are consulting from and referring to Doctor Google instead of learning about and diagnosing the actual cause. The first thing you said was to update the drivers of NoMachine Microphone adapter audio device. . . .
. . . . .