Windows 10: BSOD Error Critical_structure_corruption on tcpip.sys and ntfs.sys

I am currently facing the problem of getting BSOD again and again on tcpip.sysI already tried everything, what is standard recommendation no extra AntiVirus, Update drivers, reset netsh etc...Some days ago, BSOD was only for ntfs.sysI also repaired and reinstalled Windows - With the effect that now no more ntfs.sys errors are showing but now tcpip.sys BSODI have done also a memory diagnosis and encountered an Hardware error.Could this also be the reason for BSOD?If yes I would try to change the RAM...thanks

:)

 

Getting Critical_structure_corruption (tcpip/sys) BSOD on Windows 10 computer

Old title: critical_structure_corruption (tcpip/sys)

Hi,

I keeping getting a random BSOD with "critical_structure_corruption (tcpip/sys)" as the reason. I then have to wait approximately 10 seconds during which time Microsoft are collecting information about the error. This seemed to be introduced after the last
Windows update Tuesday. I couldn't find the cause so did a system restore and all was fine again until the following morning when Microsoft automatically installed the updates again. A rollback doesn't fix the problem now.

When are Microsoft going to fix it for me?

I have got an old-ish motherboard who's latest BIOS update was 2010 so I can't help but think this may be the reason. I've tried everything else.

Any ideas?

 

BSOD while using the internet. error (L1C63x64.sys)


Hi trainman81,

Welcome to the 10forums.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window


AVG is trying to request data from the internet, which is why the network driver is marked as the cause.
Code:

Code:

*** WARNING: Unable to verify timestamp for L1C63x64.sys *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys 0: kd> lmvm L1C63x64 start             end                 module name fffff801`89700000 fffff801`89722000   L1C63x64 T (no symbols)                Loaded symbol image file: L1C63x64.sys     Image path: \SystemRoot\System32\drivers\L1C63x64.sys     Image name: L1C63x64.sys     Timestamp:        Mon Apr 01 05:15:17 2013 (5158FBC5)     CheckSum:         000245C4     ImageSize:        00022000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

AVG drivers that have been flagged
Code:

Code:

*** WARNING: Unable to verify timestamp for avgwfpa.sys *** ERROR: Module load completed but symbols could not be loaded for avgwfpa.sys *** WARNING: Unable to verify timestamp for avgfwd6a.sys *** ERROR: Module load completed but symbols could not be loaded for avgfwd6a.sys

Please uninstall AVG and see if it helps
Uninstall AVG | AVG
It is further recommended to check your Qualcomm network driver for updates, its driver is not supported for Windows 10.
Driver Reference Table - L1C63x64.sys

 

QCAMAIN1.SYS CAUSING BSOD

This was probably caused by the following module:
qcamain1.sys (Qcamain10x64+0x108678)

Bugcheck code: 0x1D3 (0x333, 0x0, 0x0, 0x0)

Error: CUSTOM_ERROR

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: qcamain1.sys .

Google query: qcamain1.sys CUSTOM_ERROR

Using WhoCrashed I found this thread: https://answers.microsoft.com/en-us...37-error/3a99eb3e-3ba5-4937-a908-d4c478e266cd however without
solution, locked.

I did get BSOD almost everytime I moved the laptop.

This worked for me:

unscrew wifi module, push a little into the socket. Screw in. DONE