BSOD on startup with more than 1 hard drive

I'm running RTM x64 and other than this one issue it runs perfect. I'm really liking it overall, great performance too. But this one issue really bothers me since I have lots of things on other drives. Basically if I add another hard drive it starts to boot, sits on the Windows logo screen for 30 secs or so then BSOD. It's not just one drive either, I tried it with 3 different drives. All of which work fine and I can put them in any other(non-Win 7) system and they work with no issues. I can shut down, connect a drive, boot into another OS and access what's on them but that's really a pain in the ass and shouldn't be necessary, I should be able to have 2 or 3 drives without an issue.

Any help would be greatly appreciated.

Please copy the contents of your \Windows\Minidump folder to another location on your machine, zip them up, and upload the zip archive here. Analysis of those files may help to pinpoint the cause of the problem.

Unfortunately for some reason it's empty. In the Startup and Recovery options it's set to dump there but just isn't for some reason. The cause is just having more than 1 drive though. Doesn't matter if its a drive with any partitions or not, parallel or serial ATA or SCSI. It's just the presence of more than 1. This really sucks.

Thanatopsis said:

Unfortunately for some reason it's empty. In the Startup and Recovery options it's set to dump there but just isn't for some reason.

Make sure you've got a pagefile of at least 1GB on your boot partition (where \Windows lives). It's necessary for dump generation.

If that still doesn't manage to get you a memory dump, try unticking the "auto reboot" option in the dump settings dialog and noting down the numbers on the first line of the BSOD message.

Done all of that. I'm not a novice by any means, I've worked as a network admin for ISP's, the NHL, did support back when I was a teenager. This has been going on for a couple weeks, I've never before had a problem I couldn't solve either completely on my own or with some research, that's why it's getting to me so much.

Thanatopsis said:

Done all of that. I'm not a novice by any means, I've worked as a network admin for ISP's, the NHL, did support back when I was a teenager. This has been going on for a couple weeks, I've never before had a problem I couldn't solve either completely on my own or with some research, that's why it's getting to me so much.

So what was the bugcheck code?

Yup somethings crazy with my external drive too. I got a 500 gb Maxtor drive with power cable. If I shut down my pc with the drive still connected, I get a Bsod while shutting down, but if I remove it then windows shuts down normally. Other then that I get no other problems like repetitive restarts. Judt 1 Bsod and then windows boots up normally. Win 7 Ultimate, 32 bit.

110409-17097-01.dmp 04-11-2009 14:21:14 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e 0xc0000005 0x85973c21 0x951c4288 0x951c3e60 32-bit

Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

"0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred."

Attaching a .rared .dmp file for H2SO4 or others to analyze would probably help pinpoint a possible solution, well.

In the meantime, see if you can update your chipset drivers by visiting your mainboard manufacturer's site. Bios update never hurts either, when done correctly.

Attaching a .rared .dmp file for H2SO4 or others to analyze would probably help pinpoint a possible solution, well.

That flew over my head, could u elaborate?

In the meantime, see if you can update your chipset drivers by visiting your mainboard manufacturer's site. Bios update never hurts either, when done correctly.

I got the drivers from the manufactures website.

Sure, I apologize. I usually explain in greater detail than that.

C:\Windows\Minidump

At that location should be files with .dmp extension. You want to copy the latest few to another directory anywhere on your computer. Then use Winrar to create a .rar file.

You can then attach the .rar file to your next post and it will be looked at.