3 ms·
I miss BSoDs telling you which kernel driver it was. It was super useful, even without research, to tell just from the name that the e.g. Nvidia driver had done
by Someone1234 12y ago
I miss BSoDs telling you which kernel driver it was. It was super useful, even without research, to tell just from the name that the e.g. Nvidia driver had done it. It was removed in Windows NT 5.1-2/XP/Server 2003 (2000/NT 5.0 told you, as did Windows ME).
Now, assuming a crash dump was successful (they can and do fail), you have to download the "Debugging Tools for Windows" package and then run WinDbg. Load up the crash dump and only then will it give you the same basic information that 2000 and prior gave you at the BSoD.
If the crash dump didn't save (e.g. it was an issue in a storage subsystem, not enough space on the drive, etc) then you're just shit out of luck. No useful information for you, bonus points if it couldn't even store anything in the event log (that happens too, funzies!).
Even for less serious issues, having that driver name was amazingly useful for doing phone support:
User: A blue screen has come up!
Tech: At the end of the second line do you see something ending in .sys?
User: Yes! It says scanner.sys
Tech: Ah! Can you restart and install your scanner's latest software? That will solve it!
... etc etc...
Seriously was a step backwards when they removed that.
- benjaminpv 12y agoI'd had one just last night in 8.1, it displayed the driver. Do you have the memory dump turned off, maybe?
- Someone1234 12y ago> Do you have the memory dump turned off, maybe? I don't know what that question relates to? I am talking about lack of information in the BSoD and that the alternative has limitations (e.g. that memory dumps fail sometimes). It wasn't a technical support request. As to Windows 8, last time I had a BSoD it looked more like this: https://i.imgur.com/OFkIvBT.jpg https://i.imgur.com/OFkIvBT.jpg Which has as little diagnostic information as XP and later.
- freehunter 12y agoIf it's a driver that caused the crash, where it says CRITICAL_STRUCTURE_CORRUPTION, it will say the name of the driver that crashed.
- freehunter 12y agoI can confirm, my ATI driver continuously crashes and the Win 8.1 blue screen tells me it's ati.sys.
- wlesieutre 12y agoIt's atikmdag.sys for me. Except on occasion when Netflix kills it with a different message (but IIRC related to video decoding, so possibly the ATI driver's fault there too).
- freehunter 12y agoYeah I knew it was ati(something).sys. Couldn't remember it exactly, most of the time when it happens I'm looking at a blue screen but seeing red because I was in the middle of a game when it shut down.