Blue Screen When Unlocking Hard Drive

seanieboy500

Reputable
Dec 14, 2014
12
0
4,510
AMD FX-8350 Eight Core Processor 4.00 GHz

8GB RAM

MSI GTX 970 GPU

Seagate Barracuda 1000gb HDD

Asus M5A97 R2.0 Motherboard

Ultra HS 650 PSU

I have a 1TB WD External HDD that I use to store random movies, tv shows e.t.c.

Whenever I ever I try to unlock it my computer bluescreens and it says something about a crash dump.

Please Help
 

seanieboy500

Reputable
Dec 14, 2014
12
0
4,510
I only see this report once:

On Sat 27/12/2014 4:44:39 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xF46C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030F5622, 0xFFFFF8800D1C8660, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

And all the rest are these:

On Sat 27/12/2014 4:44:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122614-62384-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030F5622, 0xFFFFF8800D1C8660, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


 

kayper

Reputable
Oct 10, 2014
70
0
4,660
looks to me like a driver issue. I would disconnect the EHD and uninstall, then reinstall the drivers before plugging it back in. This should keep windows from installing drivers for you, which is never a good idea IMO.
 

kayper

Reputable
Oct 10, 2014
70
0
4,660
in your device manager( start-search"device manager") it will either be under disk drives, or other devices. once you locate it right click and uninstall. then disconnect the EHD from your computer and go to C:\windows\system32\driverstor and delete the file INFCACHE.1 . If you have a drivers disk that came with your EHD you would use it at this point, if not just plug it back in and let windows reinstall the driver for you.