4 ms·
Sources I've seen was that there was a .SYS file with all zeros that caused the BSOD. A configuration file shouldn't cause a bluescreen. EDIT: It is in the 'd
by cdchn 2y ago
Sources I've seen was that there was a .SYS file with all zeros that caused the BSOD. A configuration file shouldn't cause a bluescreen.
EDIT: It is in the 'drivers' directory, has a .SYS extension, but was something called a "channel file" but I couldn't get much info on what a channel file does other than "something something named pipes"
- smileybarry 2y agoIt's a ".sys" file but it's not a driver binary at all. It's a binary configuration file, and from what I gather it's a sort-of packed table. The actual kernel driver mounts it, parses the contents, and uses it as configuration. The ".sys" extension is probably for the believability of being a driver so users would leave it alone.