PC crahes randomly? (NDIS driver causing it?)

[sokfil]

After installing Windows to my SSD (previously installed on my HDD) on my HP m9765ch, Windows 10 started crashing randomly. Very often it was showing a different BSoD (for example: irql not less or equal, kmode exception not handled, what failed: iorate.Sys). Sometimes the system will just hang without showing a BSoD. I tried sfc and dism online restore, ran MemTest64, scanned for viruses with Kaspersky, updated and even reinstalled Windows. I ran driver verifier and ndis.sys caused an error. Here is the dmp file:
https://drive.google.com/open?id=1e2cWtQvaKU_GR4-l-zo8g...
After rebooting Windows sometimes only sees 8 instead of 16GB RAM. Any help would be appreciated!

 

[fredfinks]

Did you do a clean install? ( i.e. not a o/s rebuild 'move')
If not, wipe the drive (after backing up your personal data) and start over with fresh, new installation

 

[smorizio]

also download hardware info set it to logging and sensor. see if your power supply 12v rail having issues.

 

[Deleted member 217926]

MERGED QUESTION
Question from sokfil : "PC crahes randomly? (NDIS driver causing it?)"

After installing Windows to my SSD (previously installed on my HDD) on my HP m9765ch, Windows 10 started crashing randomly. Very often it was showing a different BSoD (for example: irql not less or equal, kmode exception not handled, what failed: iorate.Sys). Sometimes the system will just hang without showing a BSoD. I tried sfc and dism online restore, ran MemTest64, scanned for viruses with Kaspersky, updated and even reinstalled Windows. I ran driver verifier and ndis.sys caused an error. Here is the dmp file:
https://drive.google.com/open?id=1e2cWtQvaKU_GR4-l-zo8g...
After rebooting Windows sometimes only sees 8 instead of 16GB RAM. Any help would be appreciated!

 

[Deleted member 217926]

MERGED QUESTION
Question from sokfil : "PC crahes randomly? (NDIS driver causing it?)"

After installing Windows to my SSD (previously installed on my HDD) on my HP m9765ch, Windows 10 started crashing randomly. Very often it was showing a different BSoD (for example: irql not less or equal, kmode exception not handled, what failed: iorate.Sys). Sometimes the system will just hang without showing a BSoD. I tried sfc and dism online restore, ran MemTest64, scanned for viruses with Kaspersky, updated and even reinstalled Windows. I ran driver verifier and ndis.sys caused an error. Here is the dmp file:
https://drive.google.com/open?id=1e2cWtQvaKU_GR4-l-zo8gRAN86GUZbyN
After rebooting Windows sometimes only sees 8 instead of 16GB RAM. Any help would be appreciated!

 

[Deleted member 217926]

Please don't post multiple threads.

 

[sokfil]

Please don't post multiple threads.

Yes, I'm sorry for doing that. I posted my first thread under Systems and didn't get any answers, and I noticed that people usually post it under Windows 10. Then I accidentaly posted it under Systems again.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/h3EP.html

File: 060118-15281-01.dmp (Jun 1 2018 - 11:57:37)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
*** WARNING: Unable to verify timestamp for klim6.sys
*** WARNING: Unable to verify timestamp for kneps.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 32 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[Deleted member 217926]

Sounds like you might have a bad or incorrectly configured stick of RAM. It's also possible the new SSD is bad.

Did everything run fine before adding the SSD? Did anything else change as far as hardware goes?

You created bootable media with memtest and ran it for 8-10 hours? No errors at all?

Download the HD Tune free trial.

http://www.hdtune.com/download.html

Check the drive health and run an error scan.

 

[Colif]

try updating realtek HD audio drivers, they are from 2012, can get newest from: https://www.tenforums.com/drivers-hardware/5993-latest-realtek-hd-audio-driver-version.html

Driver verifer seems to have tripped over Kapersky on the last scan, you need to update this as its also too old for Win 10 and might explain why Kapersky crashed

Feb 15 2011 - e1y60x64.sys: Intel(R) Gigabit Adapter driver

Finding it is the fun part. This appears to be motherboard - https://support.hp.com/au-en/document/c01901210

this should contain the file you need as its a pack of drivers - https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10