Second Hard drive install caused BSOD and now won't boot.

Hi, I purchased a Seagate 4TB internal HD and installed it as a second drive. My 4 year old 1.5 TB Barracuda drive is close to full.

Originally my PC only recognized half the new drive space. I partitioned and started to format but changed my mind and cancelled. Suddenly the next day my PC recognized all of the disc space so I decided to partition and quick format. During the quick format process I received a BSOD. Now the PC won't boot. If I remove the second drive my PC boots normally.

Also, I've already gone into BIOS and verified my boot order is correct. Please help!!!
12 answers Last reply
More about hard drive install caused bsod boot
  1. I assume you have 64 bit windows 7 or 8.x
    the max size for a master boot record partition is 2 TB
    you will need to make the partition type as GPT and have UEFI support to make a 4 TB partition.

    Note: you can break up the drive into (2) 2TB partitions and that should work.
    Also, you might consider doing a full format rather than a quick format if you run windows 7.
    I know it will take a long time but it will mark weak sectors as bad. Windows 8, it would not matter as much because it will check your drive for problems latter as a background process.
  2. johnbl said:
    I assume you have 64 bit windows 7 or 8.x
    the max size for a master boot record partition is 2 TB
    you will need to make the partition type as GPT and have UEFI support to make a 4 TB partition.

    Note: you can break up the drive into (2) 2TB partitions and that should work.
    Also, you might consider doing a full format rather than a quick format if you run windows 7.
    I know it will take a long time but it will mark weak sectors as bad. Windows 8, it would not matter as much because it will check your drive for problems latter as a background process.


    Hi johnbl. Yes, I have 64 bit Windows 7 and I used GPT partitioning. Obviously I can't make any changes to partitioning or formatting right now as I can't boot my system. That is the problem I need help with.
  3. I assume you pulled the 4TB drive and tried to boot on the old drive. If so what bugcheck code do you get?
  4. johnbl said:
    I assume you pulled the 4TB drive and tried to boot on the old drive. If so what bugcheck code do you get?


    Yes, Windows boots fine with the new drive removed.

    Bug Check String: KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code: 0x0000001e
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+74e90
  5. the first parameter has the execption error code. That might help determine problem.
    you could also put the memory dmp on a server and post a link and I can look it up.

    cassaday said:
    johnbl said:
    I assume you pulled the 4TB drive and tried to boot on the old drive. If so what bugcheck code do you get?


    Yes, Windows boots fine with the new drive removed.

    Bug Check String: KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code: 0x0000001e
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+74e90
  6. johnbl said:
    the first parameter has the execption error code. That might help determine problem.
    you could also put the memory dmp on a server and post a link and I can look it up.

    cassaday said:
    johnbl said:
    I assume you pulled the 4TB drive and tried to boot on the old drive. If so what bugcheck code do you get?


    Yes, Windows boots fine with the new drive removed.

    Bug Check String: KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code: 0x0000001e
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+74e90




    You want to see the whole dump file? Where's the best place to put it?
  7. yep, whole dump is best, you can put it on any public access server like microsoft onedrive or mediafire.

    cassaday said:
    johnbl said:
    the first parameter has the execption error code. That might help determine problem.
    you could also put the memory dmp on a server and post a link and I can look it up.

    cassaday said:
    johnbl said:
    I assume you pulled the 4TB drive and tried to boot on the old drive. If so what bugcheck code do you get?


    Yes, Windows boots fine with the new drive removed.

    Bug Check String: KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code: 0x0000001e
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+74e90




    You want to see the whole dump file? Where's the best place to put it?
  8. johnbl said:
    yep, whole dump is best, you can put it on any public access server like microsoft onedrive or mediafire.

    cassaday said:
    johnbl said:
    the first parameter has the execption error code. That might help determine problem.
    you could also put the memory dmp on a server and post a link and I can look it up.

    cassaday said:
    johnbl said:
    I assume you pulled the 4TB drive and tried to boot on the old drive. If so what bugcheck code do you get?


    Yes, Windows boots fine with the new drive removed.

    Bug Check String: KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code: 0x0000001e
    Caused By Driver: ntoskrnl.exe
    Caused By Address: ntoskrnl.exe+74e90




    You want to see the whole dump file? Where's the best place to put it?




    http://www.mediafire.com/download/b5r3xcktozbv4mb/040115-17784-01.dmp
  9. I think you have a BIOS bug in a sleep function.
    there are BIOS updates that indicate updates to the BIOS sleep functions. I would install the update and see if this problem goes away.
    http://www.asrock.com/mb/Intel/H97M%20Pro4/?cat=Download&os=BIOS


    looking at the memory dump: your machine was up for 2 days but it clearly looks like your system is having sleep problems. I would do a full restart of the system and then download and update the BIOS.
    --------------
    looking at the first bugcheck.
    the system called this function: nt!PopUnlockAfterSleepWorker+0x42
    then bugchecked because it detected a buffer overrun.
    (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

    BugCheck 139, {3, ffffd00022b7ba50, ffffd00022b7b9a8, 0}

    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure. The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd00022b7ba50, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd00022b7b9a8, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

    machine info:
    BIOS Version P1.20
    BIOS Release Date 07/29/2014
    Manufacturer ASRock
    Product H97M Pro4
    Processor Version Intel(R) Pentium(R) CPU G3220 @ 3.00GHz
    Processor Voltage 8ch - 1.2V
    External Clock 100MHz
    Max Speed 3000MHz
    Current Speed 3000MHz
  10. johnbl said:
    I think you have a BIOS bug in a sleep function.
    there are BIOS updates that indicate updates to the BIOS sleep functions. I would install the update and see if this problem goes away.
    http://www.asrock.com/mb/Intel/H97M%20Pro4/?cat=Download&os=BIOS


    looking at the memory dump: your machine was up for 2 days but it clearly looks like your system is having sleep problems. I would do a full restart of the system and then download and update the BIOS.
    --------------
    looking at the first bugcheck.
    the system called this function: nt!PopUnlockAfterSleepWorker+0x42
    then bugchecked because it detected a buffer overrun.
    (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

    BugCheck 139, {3, ffffd00022b7ba50, ffffd00022b7b9a8, 0}

    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure. The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd00022b7ba50, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd00022b7b9a8, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

    machine info:
    BIOS Version P1.20
    BIOS Release Date 07/29/2014
    Manufacturer ASRock
    Product H97M Pro4
    Processor Version Intel(R) Pentium(R) CPU G3220 @ 3.00GHz
    Processor Voltage 8ch - 1.2V
    External Clock 100MHz
    Max Speed 3000MHz
    Current Speed 3000MHz





    Hi John. Is that the right bugcheck and mainboard / CPU you're seeing for my PC? CPU-Z is showing my BIOS as American Megatrends P01-A3 and I'm running the i7 2600k processor. I don't want to update my BIOS incorrectly and make things worse.
  11. I think something is corrupting your memory, most likely one of the suspect drivers.
    I would update or remove drivers and run a malwarebytes scan and system file checker.
    run cmd.exe as an admin then run
    sfc.exe /scannow
    -------------
    ok, I think i have the correct memory dump this time.

    the bugcheck was caused by a bad memory address used by
    Acronis Virtual Disk driver for the Virtual Disk Storage Filter
    \SystemRoot\system32\DRIVERS\vidsflt.sys Wed Feb 13 23:04:41 2013
    it could be a problem with the driver or something corrupted the drivers data.

    suspect drivers:
    \SystemRoot\System32\Drivers\a0x7fsrj.SYS Sat Jul 17 03:58:04 2010
    \SystemRoot\System32\Drivers\ai8bbcwp.SYS Tue Sep 10 06:56:12 2013

    not sure about:
    : Citrix ICA Client USB Monitor Driver
    \SystemRoot\system32\DRIVERS\ctxusbm.sys Mon Sep 07 11:09:28 2009
    http://www.citrix.com/downloads.html

    your intel storage drivers are pretty old
    \SystemRoot\system32\DRIVERS\iaStor.sys Mon Sep 13 18:23:32 2010

    your doubleTwist iPod Driver is pretty old:
    C:\Windows\system32\drivers\iPodDrv.sys Thu Apr 09 21:07:40 2009

    your network driver has bugs you should update this:
    \SystemRoot\system32\DRIVERS\netr28x.sys Tue Aug 10 20:39:23 2010
    Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer)
    maybe get update from here: http://www.mediatek.com/en/downloads/

    very old software driver:
    C:\Windows\system32\drivers\NTIDrvr.sys Tue Mar 24 20:09:39 2009
    NTI CD-ROM Filter Driver by NewTech Infosystems (likely a part of Acer Empowering Technology)

    antivirus software from 2011, remove:
    C:\Program Files\SUPERAntiSpyware\SASDIFSV64.SYS Thu Jul 21 16:03:00 2011
    \C:\Program Files\SUPERAntiSpyware\SASKUTIL64.SYS Tue Jul 12 14:00:01 2011

    machine info:
    BIOS Version P01-A3
    BIOS Release Date 02/18/2011
    Manufacturer Gateway
    Product FX6850
    Processor Version Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
    Processor Voltage 8ch - 1.2V
    External Clock 100MHz
    Max Speed 3400MHz
    Current Speed 3400MHz
  12. cassaday said:
    Hi, I purchased a Seagate 4TB internal HD and installed it as a second drive. My 4 year old 1.5 TB Barracuda drive is close to full.

    Originally my PC only recognized half the new drive space. I partitioned and started to format but changed my mind and cancelled. Suddenly the next day my PC recognized all of the disc space so I decided to partition and quick format. During the quick format process I received a BSOD. Now the PC won't boot. If I remove the second drive my PC boots normally.

    Also, I've already gone into BIOS and verified my boot order is correct. Please help!!!


    Hey did you ever resolve this issue? I'm running into a very similar issue with a hard drive, that whenever it is "initiated/turn-on" in Windows 10 it crashes my system with the same error code of "kmode_exception_not_handled"

    This happened since I was having sync issues with the hard-drive on a dual boot system, so I had quick formatted it and copied data over. Ever since then, regardless if I use a USB docking station or direct SATA connect to the MB, I get that error message. Happens on 3 different Win 10 computer. The drive spins up fine, is detected fine in the BIOS but crashes Win10.
Ask a new question

Read More

Blue Screen Boot Hard Drives Systems