• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 7 rtm install leads to bsod

amddude

amddude

Golden Member
I'm trying to do a fresh install of 7 on my pc (e6400, 4gb ram, ip35, pretty vanilla) and when the install 'finishes' and the system reboots, I get a bsod for 0x0000000f4. I'm not overlocked or anything. My memory passes memtest86 and I've never had any problems with my server 2008 install.

Has anyone else had similar issues?
 
It may help if you post the other four parameters that come with the 0x0000000f4 error.

Also, check to see if you are getting a memory dump file. It's not too hard to analyze the dump file for more hints on what's going wrong.
 
The bsod goes by too fast. The memory dump isn't in the C:\windows folder. Does it go somewhere special in 7?

Edit: I did a file search of the entire drive including hidden, non-indexed and no memory.dmp file to be found. I don't have a C:\windows\minidump folder.
 
Try disabling the JMicron controller and give it a shot. I've had some issues with those things misbehaving under Win7 when in AHCI mode and using the included drivers.
 
I tried disabling the micron controller and setting the sata to ide mode instead of ahci, same problem. I know this sounds bizarre, but after the second reboot during the install, my raptor stops being picked up by cmos and it boots from the cd again (at which point setup no longer sees the drive). If I power off my pc and power it right back up, bam the drive is back. It's reproducible only in this way and I've never had this problem before, nor has the drive had any problems. This is x64 btw.
 
Have to ask - how did you end up with a RTM install? I assume Bittorrent. If so, there's likely your problem right there.
 
The hash matches, so it's not a question of data integrity. I have a technet account anyway, they just haven't released it yet.
 
Originally posted by: amddude
The hash matches, so it's not a question of data integrity. I have a technet account anyway, they just haven't released it yet.
Click to expand...

The hash matches what? The tracker's hash? Did I miss something, cause I haven't seen an "official" has from Microsoft for the RTM build yet.
 
I'll stop posting unless someone replies to this post, but I managed to reproduce the problem during the install of 2008 R2 with the jmicron controller still turned off.
 
In XP, you could boot to a BART PE disk with an add-in Registry editor and disable the "Automatically Restart" option. I assume you can do this in Vista/Win7, but I haven't found out how yet. If you can disable those auto restarts, you should get more info about what's causing the reboots.
 
Originally posted by: amddude
I would do that, except I can't actually ever completely finish setup to get to a desktop.
Click to expand...
You boot to a separate CD/DVD and edit the Registry from there. This was definitely doable with XP. I'm not sure how you do it with Vista/W7.
 
I'm saying I don't think setup has completed to have a windows install to modify in the first place--but I do have a bartpe cd and I will try.
 
Originally posted by: amddude
I'm saying I don't think setup has completed to have a windows install to modify in the first place--but I do have a bartpe cd and I will try.
Click to expand...
Yeah, I wondered if that was what you were saying. I don't know how early the Registry files get written. They are certainly LOADED very early in the boot process.
 
The bartpe trick couldn't work with the registry to do it. However, I tried another install and I noticed if I try to make any changes to the drive (the raptor) during setup, like deleting a partition, creating a partition or formatting, it does the little wheel spinny trick then finishes, and my drive disappears from the list of drives in the "Where do you want to install Windows?".

I'll try another drive and see what happens.

Edit: I tried another drive (toshiba 2.5in), it does not have that symptom but after the first reboot during install, the pc prompts to boot from the cd, times out, then at the point where it would boot from the drive, my pc just sits there. It doesn't boot anything. I tried the startup repair from the 7 cd and it didn't find a problem. Bcdedit gave back what looks like valid entries.
 
I've tried disabling all the on-board devices, integrating the intel inf drivers, changing to ide mode--I even created a vm in vmware that wrote to the physical drive in question and then booting from it....all roads lead to bsod. I'm out of ammo.
 
0xF4 is a Critical Object Termination.

From Debugging Tools for Windows Help -> Debugging Techniques -> Bug Checks -> Bug Check Code Reference:

Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION
The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The terminating object type:
0x3: Process
0x6: Thread

2 The terminating object
3 The process image file name
4 Pointer to an ASCII string containing an explanatory message

Cause
Several processes and threads are necessary for the operation of the system. When they are terminated for any reason, the system can no longer function.
Click to expand...

Win7 doesn't keep memory dumps around on non-domain machines anymore. If it's a non-domain computer, it assumes you're a home user and much more likely to continue on your merry way after the occasional BSOD than invest the time and money to get a dump professionally analyzed.

http://blogs.msdn.com/wer/arch...vior-in-windows-7.aspx

Use safe mode to create and set this registry key: HKLM\SYSTEM\CurrentControlSet\Control\CrashControl\AlwaysKeepMemoryDump Type: REG_DWORD Value: 1

Then download and install the Debugging Tools for Windows (http://msdl.microsoft.com/down..._amd64_6.11.1.404.msi) on a working system and copy over the crash dump. Double-click the crash dump (which will open up the debugging tools) and type "!analyze -v". Post the full output up here..

Ray
[MSFT]
 
Ok here's what I did:

Booted from win7 cd, deleted all partitions on drive, ran through install. After the first reboot, my bios stops seeing the hard drive and it boots from the cd again. I powered off the pc and booted it from bartpe (note: my hard drive came back after the cold boot and during some of my previous install attempts, a different hard drive also disappeared at this stage). I loaded the system hive and added HKLM\SYSTEM\CurrentControlSet\Control\CrashControl\AlwaysKeepMemoryDump Type: REG_DWORD Value: 1 to the registry. (CurrentControlSet did not exist at this point, I had to create the keys from there on down)

I let it boot from my hard drive, it gets to the 'Starting Windows' splash screen and right before it should start the animation, bsod and my pc reboots. Same thing happens with safe mode.

I connected another drive that has server 2008 installed and loaded the debugging tools--however, I could not find any *.dmp files on the windows 7 drive and I was searching for hidden files. The C:\windows\minidump folder did not exist.

Edit: I did want to note that the raptor drive used here has been working perfectly fine prior to this. It never has a problem where it disappears from cmos except precisely at the point where the installer reboots my pc--and again I've reproduced that problem with yet another drive. I've also installed the RC with success on this drive in the past.
 
Interesting that the HD is disappearing from the BIOS, even with different HDs attached. Have you checked to see if there is a BIOS update for the MB?
 
Yes, and I have the latest bios. The weird thing is this ONLY happens when I attempt to install windows 7.

Edit: I tried a third hard drive, install worked. I ghosted back to the raptor, everything works fine.

wtf
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top