Unable to get into Windows 7 with BSOD 0x0000000F4.

[nirashauser]

Unable to get into Windows 7 with BSOD 0x0000000F4, I'm getting some error message like "A thread or process crucial to system has exited...".

This started happening after I moved the CPU cabinet to replace the monitor cable connecting.

So far I tried "chkdsk /f /r" and "sfc /scannow" on the system drive but nothing changed. When I ran those commands from the recovery option of the default system installation, computer was restarting while in the middle. When I ran those commands from Windows 7 DVD, "chkdsk /f /r" it didn't resolve, when I tried to ran "sfc /scannow" it showed a message like "a repair process is pending", etc. But when I restarted the same problem reoccurred.

 

[axe0]

Download an ISO from this post and mount the ISO on a USB, this way you have a Win10PE with preinstalled programs that could help troubleshoot the issue.

 

[nirashauser]

Download an ISO from this post and mount the ISO on a USB, this way you have a Win10PE with preinstalled programs that could help troubleshoot the issue.

What directions should I follow?

I forgot to mention that I almost re-installed the Window 7, but I clicked close button just the moment it started to copy files. Will this complicate?

 

[axe0]

If you can boot the Win10PE, we can possibly have a look at the dumps to find out what the system is complaining about.

 

[nirashauser]

If you can boot the Win10PE, we can possibly have a look at the dumps to find out what the system is complaining about.

I'm multi-booting this system with Linux and I have access to system partition from Linux. What files do you want to check?

 

[axe0]

I was not aware of that

I would like to check the minidumps that BSODs usually create, normally they are located in C:\Windows\Minidump, but with Linux I'm not sure where they might be located.

 

[nirashauser]

I was not aware of that

I would like to check the minidumps that BSODs usually create, normally they are located in C:\Windows\Minidump, but with Linux I'm not sure where they might be located.

I've dedicated a separate partition to Windows 7. I'm able to access that partition and they are in the same location, but Linux doesn't assign drive letters.

There are three files in Minidump folder, I've attached all three below in a zip, I couldn't upload them individually in their native file format. Thanks a lot for your help.

 

[axe0]

The site doesn't support the extension for dumps (.dmp)

Is your Linux installation on the same drive as your Windows installation?

 

[nirashauser]

The site doesn't support the extension for dumps (.dmp)

Is your Linux installation on the same drive as your Windows installation?

No, the Linux one is on a completely different HDD, either one wasn't present when the other OS was getting installed. I've attached the all three files I found in Minidump folder in a zip file in my post above yours.

 

[axe0]

There is a fairly chance that the HDD may be causing issues, there are ways to find out what the status of the hard drive is but I'm not familiair enough with the results to interpret them properly.
Atm I'm trying to learn to interpret the results properly.

 

[nirashauser]

There is a fairly chance that the HDD may be causing issues, there are ways to find out what the status of the hard drive is but I'm not familiair enough with the results to interpret them properly.
Atm I'm trying to learn to interpret the results properly.

This Windows 7 is installed on a new one, do you think I should get it replaced?

 

[axe0]

I think so.

 

[nirashauser]

When I'm trying to sfc /scannow, a file or folder in c:\windows\winsxs\temp\pendingrenames is preventing it, and asking me to run chkdsk, but when I run chkdsk it is exiting abruptly. I'm unable to delete the pendingrenames file, is there a way I can force it?

 

[axe0]

Possibly, by taking ownership of the folder or by using disk cleanup utility.

FYI, when taking ownership of the folder there is a chance that something goes wrong.

 

[nirashauser]

Possibly, by taking ownership of the folder or by using disk cleanup utility.

FYI, when taking ownership of the folder there is a chance that something goes wrong.

I'm trying this from installation environment, how would I do that? I'm thinking it is because of some corruption.

 

[axe0]

Doubtful, it is used by Windows Update to temporary store files when the existing files are already in use by the system. It normally is being cleared when files are updated during a restart (or with disk cleanup).

To completely understand when this issue happened (and to make sure we're on the right track)

This started happening after I moved the CPU cabinet to replace the monitor cable connecting.

With 'cabinet' you mean the case of your system?
If not, I'm afraid I don't understand what you mean since I know only 1 translation of it in my native language which translates to the government.

 

[nirashauser]

Doubtful, it is used by Windows Update to temporary store files when the existing files are already in use by the system. It normally is being cleared when files are updated during a restart (or with disk cleanup).

To completely understand when this issue happened (and to make sure we're on the right track)

With 'cabinet' you mean the case of your system?
If not, I'm afraid I don't understand what you mean since I know only 1 translation of it in my native language which translates to the government.

Yes, from the context it should be clear.

 

[axe0]

I'm going to have a look from a different perspective, because when moving the case not carefully enough some wires may get loose what can cause a lot of headaches.

Where in the house is your system located?
I assume you moved the case carefully? Enough vibrations can loosen some cables.
Have you checked inside the case if everything is properly connected (cabling, GPU, RAM, drives, etc.)?