Windows 10: Frequent irql_not_less_or_equal and tcpip.sys errors. Can't discern cause.

I have been getting somewhat irregular BSOD errors about irql_not_less_or_equal and tcpip.sys. I have looked through the various sources online to repair this error and so far I have been unsuccessful. Last night I was getting the BSOD almost back-to-back. I couldn't even get my PC to boot into Safe Mode. This morning I started up my PC and there was no problem. I've attached the 5 most recent minidump files in a zip file below, maybe there will be something in them to help.I am almost at my wits end. Getting to the point where I just want to completely reset my PC, start from a fresh install.

:)

 

'IRQL_NOT_LESS_OR_EQUAL' and 'DRIVER IRQL_NOT_LESS_OR_EQUAL (Netwtw02.sys)' Errors

Update: my computer blue screened again with the "DRIVER IRQL_NOT_LESS_OR_EQUAL (Netwtw02.sys)" error. Not sure what the reason could be. I'll check the link you gave and see if there are any solutions
to my problem.

cheers

David

 

'IRQL_NOT_LESS_OR_EQUAL' and 'DRIVER IRQL_NOT_LESS_OR_EQUAL (Netwtw02.sys)' Errors

Hi there,

Recently I bought myself a new laptop with windows 10 and on multiple occasions my computer has blue screened and displayed both the 'IRQL_NOT_LESS_OR_EQUAL' and 'DRIVER IRQL_NOT_LESS_OR_EQUAL (Netwtw02.sys)' error messages. I've had a look around other forums
to fix this, but because of my poor knowledge about computers, I didn't understand how to execute the suggested fixes. Can anyone here help me with these computer issues?

Here's a link to my 3 latest dump files from my minidump folder:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Please let me know if there is any more information I need to give you in order to help me.

cheers

 

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?