>>105733333 (Wasted)
No it doesn't, and never has.
The "crashed in driver X" has always been a guess: it's simply where the faulting instruction or memory access occurred. While it's possible for there to be a correlation, I could trivially write a driver that pokes the memory space being used by your driver - and boom, "BSOD in 10573333.SYS".
This is actually much of the reason Microsoft removed the name of the driver from BSODs: they got sick of OEMs bitching them out for some random unrelated driver partying on their kernel memory, then Window crashing with "fault in BIG_OEM_NAME.SYS".
