Solved BSOD after installing old HDD

[megamanenm]

I bought a new computer and wanted to install my old HDD to recover some old files. I made sure the two cables were connected to the HDD and tried booting it. It started loading but gave a BSOD short thereafter with the error code STOP: 0x0000007b (0x80786B58, 0xC0000034, 0x00000000, 0x00000000);

No idea what could be the cause, it even recognized the HDD when I pressed F10 and checked before it booted. I don't need the old HDD to stay there forever, just need to get a couple of files, so does anyone know where I'm supposed to go from here?

 

[JMH]

To give a definitive answer we would of course need the DMP files.

Re
Stop message 0x0000007B Descriptive text: INACCESSIBLE_BOOT_DEVICE

FYI
Usual cause: A problem occurred during the initialization of the I/O system (usually the startup device or the file system).
Solution:

1. Check for viruses on your computer. This Stop message is frequently displayed when there is a virus in the boot sector.
2. Repair or recover the hard disk. For ways to fix the hard disk, see Repair overview and Recovery Console overview.
3. Remove any newly added hard disks or controllers.
4. If you are using a SCSI adapter, obtain the latest driver from the adapter vendor, disable sync negotiation, check termination, and check the SCSI IDs of the devices.
5. If you are using Integrated Device Electronics (IDE) devices, define the onboard IDE port as the primary channel. Check the master/subordinate settings for the IDE devices. Remove all IDE devices except for the hard disk. See your hardware manufacturer's documentation for more information.
6. Check for hard disk corruption by running chkdsk. If you cannot run chkdsk, you might have to move the hard disk to another computer that is running a product in the Windows Server 2003 family and then run the chkdsk command. For more information, see chkdsk. (Note that chkdsk is available, with a limited set of options, in Recovery Console.)
7. If the computer will not start normally, try starting it in Last Known Good Configuration. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.
   
   Important
8. When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

Further Reading
Microsoft TechNet Search

 

[megamanenm]

I'm not sure how to make or access DMP files, but I do have one in the minidump folder, I assume that's the one? Problem is, it says that it's an invalid file.

 

[JMH]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

IF you are OVERCLOCKING STOP!

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.


The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.

To ensure minidumps are enabled:

*Go to Start, in the Search Box type: sysdm.cpl Press Enter.
*Under the Advanced tab, click on the Startup and Recovery - Settings... button.
*Ensure that Automatically restart is unchecked.
*Under the Write Debugging Information header select Small memory dump (256 kb) in the drop down box (the 256kb varies).
*Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
*OK.
Reboot if changes have been made.

 

[megamanenm]

Done. I should also mention that the PC boots perfectly fine if I disconnect the red cable from the HDD.

 

[zigzag3143]

Done. I should also mention that the PC boots perfectly fine if I disconnect the red cable from the HDD.

Couple of problems


1-Old drivers from as far back as 2005

[COLOR=Red]MarvinBus64.sys    9/23/2005 [/COLOR]4:17:03 PM        fffff880`03c00000    fffff880`03c44000    0x00044000    0x433470cf                        
emScan64.sys    6/21/2007 7:51:28 PM        fffff880`05d35000    fffff880`05d36800    0x00001800    0x467b1d10                        
emFilter64.sys    6/21/2007 7:51:31 PM        fffff880`05ced000    fffff87f`05cee900    0xffffffff00001900    0x467b1d13                        
emDevice64.sys    6/21/2007 7:51:44 PM        fffff880`05cef000    70626bf5`05d23b00    0x7062737500034b00    0x467b1d20                        
emAudio64.sys    8/31/2007 4:15:32 PM        fffff880`05d37000    fffff89f`05d4f000    0x0000001f00018000    0x46d884f4

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

2- Your Avast.

I notice your avast which is often at least a contributing cause of BSOD'S . Please remove and replace your Avast with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/


3-TRD 116

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help

http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

 

[megamanenm]

I couldn't find any new drivers for those old ones, although I did update some AMD drivers. I also installed Microsoft Security Essentials instead. I should also mention that I tried booting it up multiple times, yet I only found one crash dump, is that normal? It also seemed to be from two days ago as opposed to today. I also forgot to mention that when I boot my pc up with the old HDD fully connected, it shows a black screen asking whether to start the recovery program or start normally; starting it normally gives a BSOD. It also said to remove any newly installed hardware, but I'm fairly certain the HDD itself is fine. It could also be that I just didn't install it correctly, so is there a guide to tell me how to install it correctly?

 

[megamanenm]

It's working now! I'm copying my files now. I did have to disconnect the power cable for the CD ROM though, since there were only two. No idea what fixed it out of all the things I did, but I'm glad it's finally functioning properly. Thanks you guys for the help!

 

[JMH]

Happy news for you.
Thank you for reporting back.
Safe surfing...

Merry Christmas too!