New
#101
OK, still not having a lot of luck. To answer your question, turn Driver Verifier off, as I think you did. Here are what the dump files say.
The rest wereCode:Use !analyze -v to get detailed debugging information. BugCheck A, {8008080, 2, 1, fffff802ab96c959} Probably caused by : memory_corruption ( nt!MiClearFilePointer+3d ) Followup: MachineOwner
try this. Go to your motherboard's web site (http://www.asrock.com/mb/Intel/Z97%2...oad&os=Win1064) and download your Windows 10 drivers to a USB drive and keep them. Install your Lan driver.Code:KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). Arg2: ffffd000208a5800, Address of the trap frame for the exception that caused the bugcheck Arg3: ffffd000208a5758, Address of the exception record for the exception that caused the bugcheck Arg4: 0000000000000000, Reserved Debugging Details:
If you still crash, uninstall all of your Nvidia graphics drivers making sure to uninstall the graphics driver last. It will tell you to restart. Don't restart, shut down instead. Unplug the PSU, hold the start button down for about 30 seconds. Completely remove the graphics card from the computer. Attach the monitor to the on board graphics. Be sure to use the same type cable or change the input method on your monitor so it will know which type signal to look for. Plug the PSU back in and start up the computer. It should load a graphics driver for the on board graphics. Run it that way for a while and see how it does. That should tell us once and for all whether the graphics card is your problem.
In the meantime upload the DM Log if you get a BSOD. I know this is frustrating to you. But, trust me, it is frustrating to me too. But, the dump files are not making things easy. There are only indications in the dump files other than the memory corruption. Some are pointing to problems with the Network driver, memory, Graphics and hard drive. When you get problems like that, it usually points to bad memory. But, let's try to eliminate the Network and Graphics problems first if we can. As it seems to me right now, we can't run many of the tests because it keeps crashing while running them.