Windows 10: From BSOD to Windows Crash

None of the 2 dumps from today say they are Verifier Enabled, again please make sure you have driver verifier enabled.
These are the results

Code: CRITICAL_PROCESS_DIED (ef) A critical system process died Arguments: Arg1: ffffe0017958e840, Process object or thread object Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died. Arg3: 0000000000000000 Arg4: 0000000000000000[/quote] ISCTD64 Is Loaded. That is Intel Smart Connect Technology. I thought you uninstalled it.

Code: Use !analyze -v to get detailed debugging information. 　 BugCheck A, {8, 2, 0, fffff80113e562ec} 　 Probably caused by : memory_corruption 　 Followup: memory_corruption [/quote] Same as we started with

You are running Bios Version 2.20 Let's try updating BIOS to the latest version 2.50 (http://www.asrock.com/mb/Intel/Z97%2...wnload&os=BIOS)

Questions
Do you have a spare hard drive you can use for testing?
Please make sure the ISCT is uninstalled.
Please go to control Panel >Uninstall a Program and make a screenshot of everything you have installed. This will show how to post screenshots https://www.tenforums.com/tutorials/1...en-forums.html

Please post a screenshot of Disk Management Disk Management - How to Post a Screenshot of

Please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

Please verify the Game Cache of your game files.

Are you only crashing during games?

What USB or other external devices other than Mouse and Keyboard do you have connected?
Are you using any Wireless devices? if so what and make and model.

What brand of SSD do you have and what other hard drives do you have installed?

Hopefully @axe0 will come take a look at these dumps and the verifier dumps.

 

None of the dumps over the last 3 days were caused by driver verifier.

I would like to see a kernel memory dump with driver verifier enabled, a few interesting things are going on in the minidumps but they do not contain enough to reveal what it is.
A Page Table Entry not being valid, in many cases where I've seen it this resulted in faulty memory even when MemTest86+ gave zero errors.
Code: 3: kd> !pte 00000000002a395d VA 00000000002a395d PXE at FFFFF6FB7DBED000 PPE at FFFFF6FB7DA00000 PDE at FFFFF6FB40000008 PTE at FFFFF68000001518 contains 0BA00001A03B6867 contains 0B30000197537867 contains 01300002B44B9867 contains 0000000000000000 pfn 1a03b6 ---DA--UWEV pfn 197537 ---DA--UWEV pfn 2b44b9 ---DA--UWEV not valid[/quote] The 0xC9 minidump doesn't contain enough to show proper information of the IRP, @essenbe showed the possible cause but it is possible that other possible causes were present in this IRP.
Code: 0: kd> !irp ffffe0002d75f1e0 1 Irp is active with 5 stacks 3 is current (= 0xffffe0002d75f340) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned Flags = 40000000 ThreadListEntry.Flink = ffffe0002d75f200 ThreadListEntry.Blink = ffffe0002d75f200 IoStatus.Status = 00000103 IoStatus.Information = 00000000 RequestorMode = 00000000 Cancel = 00 CancelIrql = 0 ApcEnvironment = 00 UserIosb = 00000000 UserEvent = 00000000 Overlay.AsynchronousParameters.UserApcRoutine = 00000000 Overlay.AsynchronousParameters.UserApcContext = 00000000 Overlay.AllocationSize = 00000000 - 00000000 CancelRoutine = 00000000 UserBuffer = 00000000 &Tail.Overlay.DeviceQueueEntry = ffffe0002d75f258 Tail.Overlay.Thread = 00000000 Tail.Overlay.AuxiliaryBuffer = 00000000 Tail.Overlay.ListEntry.Flink = fffff802584dabe0 Tail.Overlay.ListEntry.Blink = fffff802584dabe0 Tail.Overlay.CurrentStackLocation = ffffe0002d75f340 Tail.Overlay.OriginalFileObject = 00000000 Tail.Apc = 00000000 Tail.CompletionKey = 00000000 cmd flg cl Device File Completion-Context [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffe0002958ce40 00000000 fffff802588cdfe8-ffffd000220b0a00 Success Error Cancel pending ffffe0002958ce40: Could not read device object or _DEVICE_OBJECT not found nt!ViFilterGenericCompletionRoutine Args: 00051100 00000000 00000001 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffe0002ce9f6b0 00000000 fffff801d5494248-00000000 Success Error Cancel pending ffffe0002ce9f6b0: Could not read device object or _DEVICE_OBJECT not found ISCTD Args: 00051100 00000000 00000001 00000002 >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffe0002ce9f2e0 00000000 fffff802588cdfe8-ffffd000220b0b70 Success Error Cancel pending ffffe0002ce9f2e0: Could not read device object or _DEVICE_OBJECT not found nt!ViFilterGenericCompletionRoutine Args: 00051100 00000000 00000001 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffe0002cea5040 00000000 fffff8025859cb4c-ffffe0002f1b3460 Success Error Cancel pending ffffe0002cea5040: Could not read device object or _DEVICE_OBJECT not found nt!PopSystemIrpCompletion Args: 00051100 00000000 00000001 00000002 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffffe0002f1b3460 Args: 00000000 00000000 00000000 00000000 Irp Extension present at 0xffffe0002d75f418:[/quote]

 

Thanks @BSOD Minidump - Configure to Create in Windows 10 - Windows 10 Forums[/b]

Also please enable Driver Verifier, this will tell you how. After configuring them, please go back and make sure they are enabled Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums. This video may help as well.

[youtube]BjsofLPNosc[/youtube]

Once you have a BSOD or two with verifier, the dumps will be fairly large, too large to upload here usually. You will find them by searching for %SystemRoot%\MEMORY.DMP (C:\Windows\MEMORY.DMP) Copy them and paste them to your desktop. Zip them up and upload them to a file sharing location like Dropbox or One Drive. Set them to shared and give us the link.

If you have any questions, please feel free to ask.

 

Important to note, the default setting is to overwrite the MEMORY.dmp with every BSOD. It is recommended to disable the overwrite setting OR move the MEMORY.dmp to a different location.

 

As Axe0 said please configure it not to overwrite dump files and upload the Dump files as they happen, just to make sure.

Attachment 86107

 

@essenbe @axe0 I know I had driver verifier enabled (and I have small dump files enabled too). I did shut down the computer and in the morning got a bsod driver verifier iomanager violation. I wonder if that removed verifier settings? I didn't think about it at the time because it was a bsod and I thought it would be caught in the dump files for you to see but now that makes me wonder.
I did uninstall ISCT
I will post the screenshots
I will run the scans
I just have my wired mouse (logitech g600 mmo gaming)
My wired keyboard (Microsoft) https://www.microsoft.com/accessorie...4000/b2m-00012
I just have the one hard drive Sandisk 240GB SSD

 

Driver verifier can only be disabled when you do so manually, a crash changes nothing to the settings.

 

updated my system specs from my reciept

 

Do you have a spare hard drive you can use for testing? - no
Please make sure the ISCT is uninstalled. - Check Control panel for yourself

Please go to control Panel >Uninstall a Program and make a screenshot of everything you have installed. This will show how to post screenshots Screenshots and Files - Upload and Post in Ten Forums
(Screenshot attached)
Please post a screenshot of Disk Management Disk Management - How to Post a Screenshot of
(Screenshot attached)
Please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

Please verify the Game Cache of your game files.- verify how?


Are you only crashing during games? - Yes because I only play games on this computer

What USB or other external devices other than Mouse and Keyboard do you have connected? - none
Are you using any Wireless devices? if so what and make and model. - no everything is connected

What brand of SSD do you have and what other hard drives do you have installed? - Sandisk, none

 

Question? When running:
Please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow .
At the command prompt, how do I "give admin permissions?"

 

If you right clicked the start flag and selected Command prompt (Admin) you will get a UAC asking for your password. If you give it, you have it with Admin permissions. You opened Command prompt as Admin and gave it permission. Tou have already given permission.

 

Got a PFN List corrupt BSOD with Driver Verifier running here are the files

 

Ran the sfc /scannow scan and Windows Resource Protection did not find any integrity violations.

 

I am going to let @axe0 look at the dump. Did you change your dumps to Kernel Memory Dumps?

 

Driver verifier doesn't look to be active in the dump *Sad
I would ask that you try to reseat the memory in different slots.
I would also suggest to update the BIOS
Code: 0: kd> !verifier fffff8011f0e37a0: Unable to get verifier list. 0: kd> !pte 000000000026f57a VA 000000000026f57a PXE at FFFFF6FB7DBED000 PPE at FFFFF6FB7DA00000 PDE at FFFFF6FB40000008 PTE at FFFFF68000001378 contains 42D0000193359867 contains 0D900001A48DA867 contains 0B400001A47DC867 contains 0000000000000080 pfn 193359 ---DA--UWEV pfn 1a48da ---DA--UWEV pfn 1a47dc ---DA--UWEV not valid DemandZero Protect: 4 - ReadWrite[/quote]