Home > Blue Screen > BSOD When Adding Hard Drives To 64-bit Version

BSOD When Adding Hard Drives To 64-bit Version


This is not acceptable on a work situation (well, I wouldn't accept that on my home computer either), so I installed another ramdisk with another software as drive S:, copied all I am running version 3.3.3 The system seems to BSOD on when ever i try to load a second ramdisk. (I have a 12gb and a 38gb ram disk, yes i Rebooted from Win 7 installation disc and immediately had the following exception: PAGE_FAULT_IN_NONPAGED_AREA ***STOP: 0x00000050 (0xFFFFF7FFF6E6B74F,0x0000000000000000,0xFFFFF8000D26B706,0x0000000000000002) 21 JAN 2013 1600hrs: rebooted from Win 7 installation disc, proceeding normally. The BSOD mini dump files have pointed to NTFS errors, Windows Kernel, IRQ, and others. http://gbcmedina.com/blue-screen/bsod-associated-with-bios-version.php

I tried windows recovery, but that was a dead end probably due to the HDD being encrypted (it claimed the MBR was corrupted - it is really just fine). Installation & Setup Our Sites Site Links About Us Find Us Vista Forums Eight Forums Ten Forums Help Me Bake Network Status Contact Us Legal Privacy and cookies Windows 7 Forums Make sure the top radio button is selected and click next. To repair boot configuration data, you need to use the Bootrec.exe tool. here

Ssd Blue Screen Windows 7

Then once a crash occurs, please send me the MEMORY.DMP file (compress it and upload to a file sharing service) and the screenshot taken in step 3. So not everything is lost Best Regards, John Reply Quote Joe 3.2.3 - BSOD Sometimes at Startup Win7 64 Bit 30 January 2013, 01:42 The exact same problem still exists It works now, no more BSOD! My Win7-64 install is on a clean formatted drive.

As a workaround, please try creating a RAM disk with the Hard Disk Emulation mode turned on. Your computer's manufacturer website should have more information and resources on the drivers available. If not, then that "protective" MBR can easily be corrupted and then everything tries to default to the "new" MBR instead. Stop: 0x0000007a When the computer boots up, Windows 7 will install the AHCI drivers automatically.

If it still crashes, if possible, could you please do the following: Enable the kernel memory dump (a minidump is not sufficient). But as soon as I set it back to Z I get the crash. by cassaday / April 6, 2015 3:04 AM PDT In reply to: Try this. solved List of Things I can Copy To My Clean Re-install of Win7 HDD With New Mobo and CPU?

Can this be a reason? First I installed the debug version and switched to kernel dump. I'll appreciate any fixing you can give me.I have tested the RAM with 12 passes without an error. Also, could you please run this tool and save its report to an ARN file?

Ssd Bsod Windows 10

Flag Permalink This was helpful (0) Collapse - We'd have to test that on another system. http://superuser.com/questions/539452/bsod-continuing-after-wiping-hard-drive-and-starting-clean-windows-7-installatio Just for your understanding - the reason for Z is that I have many external drives with many partitions. Ssd Blue Screen Windows 7 Are controllers aware of TCAS RA taking place? Ssd Causes Blue Screen Asus P5WD2-E giving BSOD during Win XP installation Tom's Hardware Around the World Tom's Hardware Around the World Denmark Norway Finland Russia France Turkey Germany UK Italy USA Subscribe to Tom's

Often there is no entry of the crash in the event log. this contact form Best Regards, John Reply Quote Andrew 3.2.2 - BSOD Sometimes at Startup Win7 64 Bit 19 November 2012, 23:28 Admin Registered: 11 years ago Posts: 5 411 It's actually quite Restart and no problem. That is, in its current version, SoftPerfect ramdisk is too risky to even try without having a separate test machine to play with, and we don't have such test machine or Ssd Blue Screen On Boot

It could be a bad port or a bad driver. Proffitt Forum moderator / April 7, 2015 8:24 AM PDT In reply to: Second Hard drive install caused BSOD and now won't boot. To fix this error, try running the chkdsk utility tool. http://gbcmedina.com/blue-screen/bsod-os-version-6-1-7601-2-1-0-256-48-locale-id-1033.php All submitted content is subject to our Terms of Use.

And normally my system creates a dump. We were able to rip along without having to discuss how to make/use/etc.Bob Flag Permalink This was helpful (0) Collapse - You didn't make the entire drive by James Denison / I found that this means: 0x000000F4: CRITICAL_OBJECT_TERMINATION One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated.

solved Win 7 BSODs during first few startups solved Error during Windows 7 installation.

Reinitiated Win 7 install, no problems until it reached 99% then the following unspecified BSOD appeared: ***STOP: 0x0000007F (0x0000000000000008,0x0000000080050031,0x00000000000006F8,0xFFFFF8000D2Df610) Within my BIOS the only values that appeared to be out-of-range were Regards Zeebie Reply Quote Markku BSOD Sometimes at Startup Win7 64 Bit 07 April 2013, 21:32 Yet another confirmation of this issue (and another one, too). Restart the system. I have 8GB of RAM and I ran MEMTEST (8 passes) with no errors.

by R. Save period was set to 10 minutes. I do not have the problem with the same image file and Win 7 32 (at least it never occurred so far). Check This Out Thanks!

Then, you can restore the registry if a problem occurs. After cloning drive, reboot computer. The original problem occurred the first time after I loaded a Win 7 32 image into Win 7 64 (drive letter was Z). This is our home computer and having it out of service is challenging.