BSOD browsing, waking from sleep. CRITICAL_STRUCTURE_CORRUPTION

zbook · 01 Jul 2017

Open administrative command prompt and type or copy and paste:

1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)

2) sfc /scannow

3) dism /online /cleanup-image /restorehealth

4) chkdsk /scan

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread

Make sure that there is no over clocking while troubleshooting.
Sometimes there are problems in the bios that produce bsod.

The bios in your computer: BIOS Version/Date American Megatrends Inc. F8, 18/09/2015
Please check to see if this is the most up to date version.
To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios.

So please make sure your files are backed up.

Please make a backup image with Macrium: Macrium Software | Macrium Reflect Free: Macrium Software | Macrium Reflect Free
And please create a restore point.How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

Windows driver verifier is a tool that is used to find misbehaving drivers.

It will repetitively produce bsod until it is turned off or until all misbehaving drivers are fixed.

In the left lower corner search type verifier. A pop up will appear to make customized settings for the tests and for the drivers.

This link has the customized settings: Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

In order to use windows driver verifier you must know how to navigate through the windows recovery or advanced troubleshooting menu.

To practice navigating though this menu open administrative command prompt and copy and paste:
shutdown /r /o /f /t 00

To turn off windows driver verifier you will navigate to startup options (not startup repair). In startup options it will restart and you will select #6 safe mode with command prompt. You will then type verifier /reset to turn off windows driver verifer. In case safe mode with command prompt verifier /reset does not turn off windows driver navigate in the windows advanced trouble shooting menu to command prompt.This is where you will see X:\windows \system32\cmd.exe
Enter the command: verifier /bootmode resetonbootfail to turn off windows driver verifier.
In case safe these two methods do not turn off windows driver verifier you can use the restore point that was recently created. Using this method though is likely to lose the minidmp file so it is the backup option.

Once windows driver verifier is turned off you will reboot to the desk top and use software to analyze the minidump files produced by windows driver verifier.

Download and install Bluescreenview and Whocrashed. They may each provide additional information in processing the minidmp files.

Blue screen of death (STOP error) information in dump files.
http://www.resplendence.com/whocrashed

When windows driver verifier produces a bsod the window will display a stop code. The stop code is typically driver verifier detected violation. Sometimes it will display the misbehaving driver in the form *.sys. If you see this you will record it. Each time you have a bsod you will want time to view the windows.

To modify the settings so that you have time to view the bsod window: Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure un-check automatically restart.

BSOD Finding and fixing them - Microsoft Community

Whenever a bsod occurs and your return to the desktop you will use bluescreenview and whocrashed to analyze the minidump. Then you will uninstall the misbehaving driver or application. The process will continue until you no longer have any bsod. You can reinstall drivers either immediately after they are removed or after all misbehaving drivers have been uninstalled. This is personal preference. The end result should be the same. Once there are no more bsod you will run windows driver verifier for 36 hours of typical computer use. If there are no longer any bsod the troubleshooting will be completed and preventative maintenance will have been performed.

When you have bsod please update or post a new zip file:
BSOD - Posting Instructions - Windows 10 Forums
We will process the windows driver verifier produced bsod minidmp files and guide you through the process.

Once you are comfortable navigating through the windows advanced troubleshooting menu, have created a new restore point, have backed up your files, and have made an image using Macrium you can start windows driver verifer.

slowcorals · 03 Jul 2017

Okay, I have now followed your advice and this it what I got. I have no overclocking enabled.

Firstly . This is what i got from the command promt when running the commands:

Version 1703 (OS Build 15063.413)

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>winver

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool

Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ... 399872 file records processed.File verification completed. 7725 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ... 487948 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...Security descriptor verification completed. 44039 data files processed.CHKDSK is verifying Usn Journal... 36136288 USN bytes processed.Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
233916415 KB total disk space. 145159200 KB in 203205 files. 127740 KB in 44040 indexes. 0 KB in bad sectors. 514271 KB in use by the system. 65536 KB occupied by the log file. 88115204 KB available on disk. 4096 bytes in each allocation unit. 58479103 total allocation units on disk. 22028801 allocation units available on disk.

C:\WINDOWS\system32>

As you can see windows found no problems by running the commands.

I found a new beta bios for my motherboard called f9b that promised would fix memory compability. I installed that version. I also did a reset on my bios.

After backing up my files by your instructions i ran driver verifier. I tested 3 times and got a bsod every time before it got a chance to boot into the login screen. The first bsod i got indicated that the realtek LAN driver was the problem so I disabled that driver and disabled LAN from my bios setting. The second time the bsod indicated that virtual bus driver was the problem which is my gaming controller driver. So i also disabled that driver. But the dump also said that it was a memory corruption caused by ntoskrnl.exe. The third time it was caused by ntoskrn and 1KBFLTR.sys. And this time I am at a loss. I can't find any information about 1KBFLTR.sys and ntoskrn is caused by a windows process so I need some help.

I have attached my minidumps below. unfortunately the first dump that was caused by Ethernet driver disappeared after using a restore point. The ones that was modified 2017-07-03 is the most recent ones.

philc43 · 03 Jul 2017

I can't find any information about 1KBFLTR.sys and ntoskrn is caused by a windows process so I need some help.

The driver is actually I1KBFLTR.SYS but I am not sure what it is either; it could be left over from an earlier OS if you upgraded to W10 rather than a clean install.

zbook · 03 Jul 2017

Code:

BugCheck C4, {2000, fffff80adb66b048, 0, 56706353}*** WARNING: Unable to verify timestamp for ScpVBus.sys*** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sysProbably caused by : memory_corruption

ScpVBus.sys

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver

http://forums.pcsx2.net/Thread-XInpu...6161#pid186161

Code:

ScpVBus      Scp Virtual Bus Driver Scp Virtual Bus Driver Kernel        Manual     Stopped    OK         FALSE       FALSE        16,384            12,288      0          05/05/2013 23:31:26    C:\WINDOWS\system32\drivers\ScpVBus.sys          4,096

Code:

BugCheck C4, {2004, ffffbb8b2813ebc8, fffff80cc7ec01e0, ffff8680b853d0a8}Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+6b )

Code:

ffff8680`b853cff8  fffff80c`c7ec01e0Unable to load image I1KBFLTR.sys, Win32 error 0n2*** ERROR: Module load completed but symbols could not be loaded for I1KBFLTR.sys I1KBFLTR+0x1e0

Code:

I1KBFLTR     T1 Gaming Keyboard     T1 Gaming Keyboard     Kernel        Manual     Running    OK         TRUE        FALSE        2,560             14,208      0          19/10/2011 06:43:33    C:\WINDOWS\system32\drivers\I1KBFLTR.sys         1,408

1) The Realtek driver did not appear in bsod minidump debugging. This may be due to the restore. This driver can be replaced via: Realtek

2) Uninstall ScpVBus.sys using device manager (C:\WINDOWS\system32\drivers\ScpVBus.sys)
Reinstall: reboot and reattach the device

2) Uninstall I1KBFLTR.sys using device manager (C:\WINDOWS\system32\drivers\I1KBFLTR.sys)
This appears to be the gaming keyboard.
Reinstall: reboot and reattach the device

slowcorals · 03 Jul 2017

I ran driver verifier again after reinstaling the mentioned drivers and i got bsod caused by the same problem as before. It seems that removing the Virtual Bus driver fixes the first bsod. But The second bsod is still caused by I1KBFLTR.SYS and ntoskrnl.exe

zbook · 03 Jul 2017

Code:

ScpVBus      Scp Virtual Bus Driver Scp Virtual Bus Driver Kernel        Manual     Stopped    OK         FALSE       FALSE        16,384            12,288      0          05/05/2013 23:31:26    C:\WINDOWS\system32\drivers\ScpVBus.sys          4,096

Sometimes corrupted drivers need to be replaced with the identical driver.
Other times a driver will need to be updated to a new driver.
And sometimes with a change in operating system there is no longer a supported driver.
In this case I am not aware of a different driver version. It appears to be an uninstall and reinstall to fix corruption.
There could also be an incompatibility in the computer environment.

1) Download and install Everything
voidtools
It will index everything on internal and external drives
It can be set to start on boot or opened when needed.
Search for ScpVBus.sys

2) Create a restore point

3) right click on ScpVBus.sys and uninstall

4) reboot

5) run windows driver verifier.

If this happens with I1KBFLTR.sys perform the above method.

slowcorals · 04 Jul 2017

Okay, this is really weird. I removed I1KBFLTR.sys which is my keyboard driver. But as soon as I rebooted the computer and connected the keyboard again I1KBFLTR.sys would install itself again. So i removed I1KBFLTR.sys completley and used another keyboard instead. Then i ran driver verifier and the BSODS seems to be gone. Atleast when booting the computer. It seems really weird that a keyboard would cause a bsod.

I tried finding new drivers for my keyboard but couldn't find any. The company func which is the brand for my keyboard has been bought up by another company so func's website doesn't exist anymore.

zbook · 04 Jul 2017

Sometimes software or a driver becomes corrupt and reinstalling them fixes the problem.
Other times the software or driver is incompatible with the current computer environment.
Were you able to completely uninstall the driver?
That is after uninstall and reboot using everything was it no longer there?
Did you get a bsod when you reattached the keyboard with the same driver?

slowcorals · 04 Jul 2017

immediately after I plugged in my keyboard again when running driver verifier I got a BSOD. But The crash report says that RTKVHD64.sys was the cause.

Yes, I was able to completley remove I1KBFLTR.sys

zbook · 04 Jul 2017

Reboot into safe mode, detach the keyboard, use everything to find any remaining driver and uninstall I1KBFLTR.sys
Let us know if you were or were not able to completely uninstall in safe mode.
This could be a permission issue if it does not allow complete un-installation in safe mode.

RTKVHD64.sys

Realtek High Definition Audio Function Driver

http://www.realtek.com.tw/downloads/...Level=3&Conn=2

Also in safe mode uninstall all realtek drivers using device manager and then everything search.
Let us know if you were or were not able to get all of the the Realtek software/drivers.
Again this may be a permission issue.

If you cannot remove the complete realtek driver see whether you get a bsod using driver verifier with wireless off and using cat 5e or ethernet to connect to the internet.