If so, having Driver Verifier list a Microsoft driver as the probable cause leads us to the back to the direction of unknown hardware failure as the probable cause. The Driver Verifier instructions state to only select 3rd party drivers (non-Microsoft drivers). However, the driver named was the Microsoft Windows Network I/O Subsystem driver netio.sys, which really makes no sense here.

Of the 3 remaining dumps, 2 of them had bugchecks = 0xc4 which means that Driver Verifier flagged a driver. Again, that was just an example and I was NOT referring to your system. At best, dumps can point us in a general direction, for example, telling us that an I/O error occurred, which to me means that the system encountered trouble with a hard drive. In fact, dump files are incapable of telling us which piece of hardware is/has failed. This means that Windows came down so fast that it did not have time to write a dump or an 'unknown' hardware problem exists and the computer literally shut off/lost power before it could write the dump (akin to someone pulling out the electrical plug on a desktop PC).īSOD Kernel memory dumps are created to help software developers debug their code, not really to help us with hardware issues. It'd be really cool if someone helped me out.Įdited by catcatcat, 12 August 2019 - 04:10 AM.Ģ of the 5 dumps you submitted were zero (-0-) bytes in size. I think the culprit is a driver, but I don't know which one. This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0) SysnativeFileCollectionApp.zip 1.35MB 4 downloads dumpfile.zip 504.16KB 0 downloads

I have attached SysnativeFileCollectionApp.zip and a dump file (in zip). I still got the same BSOD error on Saturday. I did (last Wednesday) and it was of no use. Went to a nearby Lenovo service store and ran all (h/w) tests, found no errors (They told me to reset).Ī friend told I should 'reset this PC' and it would fix itself. I did run (all) tests with Lenovo Diagnostics Tool and found no errors. Last month my laptop crashed and I got this BSOD error (4-7 times).

Laptop driver power state failure