Blue Screen of Death (BSOD) help needed
in IT Support ·
So, I just finished getting WhoCrashed all set up, and this is what popped up on my screen right after the run:
Crash dump directory: C:\Windows\Minidump
It looks like crash dumps are currently turned on for my machine.
Back on Thursday, November 6, 2014, at 5:37:27 PM GMT, my computer hit a wall and crashed...
crash dump file: C:\Windows\Minidump\110614-13447-01.dmp
From what I can tell, the culprit seems to be this specific module: win32k.sys (win32k+0xC4283)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000154283, 0xFFFFF8800C975060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft Corporation
company: Microsoft Corporation
description: Multi-User Win32 driver bug
Basically, the Bug check description says that some kind of exception went down while the system was trying to transition from non-privileged code to privileged code...
It really looks like your typical software driver glitch, so I don't think it's actually a hardware issue at all...
Since the crash happened inside a standard Microsoft module, it's possible my system configuration is just a bit wonky, or maybe there's some other driver lurking in the background that the system can't quite pin down yet...
Crash dump directory: C:\Windows\Minidump
It looks like crash dumps are currently turned on for my machine.
Back on Thursday, November 6, 2014, at 5:37:27 PM GMT, my computer hit a wall and crashed...
crash dump file: C:\Windows\Minidump\110614-13447-01.dmp
From what I can tell, the culprit seems to be this specific module: win32k.sys (win32k+0xC4283)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000154283, 0xFFFFF8800C975060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft Corporation
company: Microsoft Corporation
description: Multi-User Win32 driver bug
Basically, the Bug check description says that some kind of exception went down while the system was trying to transition from non-privileged code to privileged code...
It really looks like your typical software driver glitch, so I don't think it's actually a hardware issue at all...
Since the crash happened inside a standard Microsoft module, it's possible my system configuration is just a bit wonky, or maybe there's some other driver lurking in the background that the system can't quite pin down yet...