Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › crash dump thing while plugging in other hdd after installing an ssd
New Posts  All Forums:Forum Nav:

crash dump thing while plugging in other hdd after installing an ssd

post #1 of 3
Thread Starter 
Well, it is a lot to say but I will try to explain as clearly as possible.

I just got a samsung 840pro 128gb and I decided that I would not uninstall my os from my previous hard drive, that I would just use it as a storage drive and in the event of the ssd failing i will still have my os on there. So I hooked up my ssd and it seems to be working fine, but once I hook up my hdd (I checked to make sure the ssd has the boot priority) this crazy blue screen crash dump happens, it happens so fast I can't read the errors on there. And then I am stuck in an infinite cycle of the computer rebooting over and over.

Now, what I did was unplug the hdd completely, the power, the sata on it, and the sata end corresponding to it on the motherboard. And I STILL got the crash dump, which scared me at first. After the crash dump it always gives me 2 options, one is continue with system resume or something, and another is like delete system location or something like that. I always picked the system resume because the delete known system location (thats probably not exactly what it said it just sounded scary like it was going to format everything on my ssd that I spent the whole day installing). Anyway when I turned off my PC and all of a sudden I tried the continue with system resume and it booted up fine, no problems. So now I'm confused, if the ssd has boot priority why would it even give me a crash dump, the hdd should have no effect or just be undetectable if it can not work properly, right?

I thought I could simply hook it up, make sure its not the primary boot drive, and then it would just show up as another c, d, e, f, etc in my computer.

BTW the hard drive is a wd cav blue 1tb if thats relevant. I installed the same exact windows on the ssd from the same exact product key as was already on the HDD as well, if thats significant, it was Windows 7 Home Premium 64bit.

The wd drive was split into 2 or 3, probably 3, partitions and the ssd is split into 2 partitions i know thats probably useless but maybe the wd is trying to use d or something which is taken by the SSD, I dont know.

Thanks for your help

Sorry if its in the wrong section, maybe this would be more appropriate in hdd/ssd section, I suppose I should post it there too
Edited by ilikesoldat - 5/14/13 at 11:54pm
post #2 of 3
    You will probably have to reinstall Windows on that SSD.  First, make sure that you're plugging the SSD into the SATA0 port and the HDD into SATA1 (or SATA2).  Otherwise, you could be giving boot priority to the SSD, even though it's the second device.
    My next thought is that you could be experiencing "partition collision."  That's what I call it when you get disk's partitions interleaved like this: Disk0/Part0, Disk1/Part0, Disk0/Part1, Disk1/Part1.  I'm guessing that you didn't have the HDD installed when you installed Windows on the SSD?
    My recommendation if plugging the SSD into SATA0 doesn't fix the problem is this: With your HDD disconnected, boot Windows 7 setup.  When you get to the page where it is asking where you want to install Windows 7, delete all the partitions on your SSD.  Create one partition that fills the SSD, format it, and then cancel setup and turn off your computer.  Reconnect your HDD, and boot setup again.  The single partition for your SSD should be on the top of the list of disks you can install Windows 7 to, with your HDDs partitions visible below.  Select the SSD's partition as the destination and proceed with installing Windows 7.

    Don't let Windows partition the drive automatically (i.e. don't hit "Install now" without partitioning and formatting the SSD first), because by default, setup will create a tiny "recovery" partition as the first partition, and create a second partition that spans the rest of the disk.  It will install Windows on this second partition.  In that case, when you turn on your computer after connecting the HDD, the bootloader on the SSD will look for Windows on disk #2 like it normally does—except your HDD's first partition is now disk #2, and the disk the bootloader is looking for is now disk #3!  I'm guessing that this is what you did; if not, please explain how you partitioned and formatted the SSD before installing Windows.

    At the very least, boot into Windows setup with both your SSD and HDD connected.  Get to the page where you select the disk to install to, and see if the two disk's partitions are interleaved something like this:

Recovery 300 MB (SSD)
Windows 7 (HDD)
Windows 7 (SSD)
Second partition (HDD)
Third partition (HDD)

If they are interleaved like this, that's probably the problem.
Edited by Techie007 - 5/15/13 at 5:55am
My desktop PC
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7-3770K Gigabyte P67A-D3-B3 NVIDIA GeForce 8400 GS  1x Corsair 8 GB 
Hard DriveHard DriveHard DriveOS
Kingston SV300S3 WesternDigital WD10EZEX Samsung HD154UI Windows 7 Ultimate SP1 x64 
MonitorMonitorKeyboardPower
Daewoo L947BK Gateway FPD1530 HTK-2001 Dynex DX-400WPS 
MouseAudio
Kensington K72400 Realtek ALC889 
  hide details  
Reply
My desktop PC
(14 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7-3770K Gigabyte P67A-D3-B3 NVIDIA GeForce 8400 GS  1x Corsair 8 GB 
Hard DriveHard DriveHard DriveOS
Kingston SV300S3 WesternDigital WD10EZEX Samsung HD154UI Windows 7 Ultimate SP1 x64 
MonitorMonitorKeyboardPower
Daewoo L947BK Gateway FPD1530 HTK-2001 Dynex DX-400WPS 
MouseAudio
Kensington K72400 Realtek ALC889 
  hide details  
Reply
post #3 of 3
Thread Starter 
K, I will check if they are interleaved in a moment. No, I did not make the first partition the recovery. Windows wanted to make a 100mb for the first one and then put the whole 120gig on the second one. What I did is I put the 120 gig on the first one, and the 100mb on the second one. So I would say it's extremely unlikely they're interleaved. Yes, the ssd is on sata 0 and the hdd on sata 1. Well I'm about to put the boot disk in and I'm going to check it out, if it will even get to that without crash dumping me, which technically it shouldn't crash dump since its only going into Windows installation.






--->OK I replugged the HDD and for some reason there are no more problems now it booted and I can view the hard drive and everything that's in it. Very strange, very strange indeed. Perhaps foreshadowing for future problems? I hope not.
Edited by ilikesoldat - 5/15/13 at 6:56pm
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › crash dump thing while plugging in other hdd after installing an ssd