Blue Screen (BSOD) After System Image Restore - *** STOP 0x000000F4...

[miketh2005]

I backed up my old system before sending it in for repairs. They replaced the HDD and sent me back the refurbished PC. So I started to restore my old system to the same computer. I put in the repair disc I just made on the new OS they put on the new HDD (Home Premium). I went to system image restore, and it recognized the system image etc. on my external HDD. I checked to format & repartition, etc. so it set about restoring the system, it took about 3 or 4 hours for 315 or so GB. (my external HDD is 320GB, but the computer HDD is 640GB)

When it was done it restarted and ran CHKDSK (I wouldn't skip it even if I pressed a button). It fixed a few things and restarted. Then it said "Starting Windows" or whatever, and the BSOD. It says:

*** STOP 0x000000F4 (0x0000000000000003, 0xFFFFFA800701A060,0xFFFFFA800701A340, 0xFFFFFA80003393460)


I've tried all of the "Safe Mode" options and they all result in the BSOD.

I have gotten the Minidump file from a Ubuntu Live CD. Here it is:

http://www.mediafire.com/download.php?axa8afxx5jcx06l

Please help, thank you!

 

[bagavan]

see this

Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION (Windows Debuggers)

I am not familiar with this. Hopefully some other member will help you

 

[miketh2005]

I have used startup repair and it did not work also.

 

[miketh2005]

Anyone?

 

[Northernsoul55]

Hi Mike,

Was the computer running fine before you restored the image?
And can I just ask...is the new Hard drive a SSD?

You could also try these:
Run memtest.
Check Windows system event logs and see if a lot of NTFS errors are accessing your drive.
Make sure drivers are uptodate and no problems in Device manager. ( Ive seen this issue caused by bad display drivers and/or by conflicting display drivers)
Check all drive cables are seated correctly or try known working cables to be safe
Try running minus 1 DIMM, then minus the other one.
Try disabling Graphics card in Device manager and reboot.
Try PSU swap.
Try a different hard drive


Usually this error is either a disk problem or a memory problem or a power problem or software/driver related.

Saying that I once had the same error on a computer and believe it or not I fixed it by removing the CMOS battery for 15 mins and rebooting the machine (you will have to change back any Bios settings you had previously as this will restore defaults)


Hope this helps, let me know any outcome, good luck.
Cheers

Dave

 

[miketh2005]

Hi Mike,

Was the computer running fine before you restored the image?
And can I just ask...is the new Hard drive a SSD?

You could also try these:
Run memtest.
Check Windows system event logs and see if a lot of NTFS errors are accessing your drive.
Make sure drivers are uptodate and no problems in Device manager. ( Ive seen this issue caused by bad display drivers and/or by conflicting display drivers)
Check all drive cables are seated correctly or try known working cables to be safe
Try running minus 1 DIMM, then minus the other one.
Try disabling Graphics card in Device manager and reboot.
Try PSU swap.
Try a different hard drive


Usually this error is either a disk problem or a memory problem or a power problem or software/driver related.

Saying that I once had the same error on a computer and believe it or not I fixed it by removing the CMOS battery for 15 mins and rebooting the machine (you will have to change back any Bios settings you had previously as this will restore defaults)


Hope this helps, let me know any outcome, good luck.
Cheers

Dave

Yes, it was working fine before the image restore besides a cooling system problem. This is a laptop btw. I had Windows working fine on it before I formatted it in order to do a system image restore. Which leads one to believe it is a problem with the system image. All my files got restored, as I was able to retrieve them with a Ubuntu Live CD. But I am afraid of losing all of my settings (registry), bookmarks, etc. which is not as easy to just backup. It is not a SSD.

I can't access Windows at all. Can I do any of your steps via cmd or a Ubuntu Live CD?

Thanks so much.

 

[Northernsoul55]

Hi Mike,

PLEASE SEE CENTAUR78 EXCELLENT ADVICE AND FIX BELOW

Cheers

Dave

 

[Golden]

This is a better tutorial - all SevenForums ones are
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Northernsoul55]

I stand corrected Golden..apologies, and have corrected

 

[centaur78]

Mike

Based on the BSOD there are two drivers that has caused this BSOD....

1. avfwim.sys ( which is a AVIRA Antivirus NDIS packet driver) caused and IRP fault twice

2. MijXfilt.sys (Motionjoy driver... used by Xbox) which caused a driver violation.

Now you would need to disable these 2 in order to boot... If you are using the Ubuntu Live CD ... then go the Windows\System32\drivers... look for these two drivers and rename it to avfwin.sys_old and MijCfilt.sys_old. This is make sure that these drivers are not loaded why windows boots...

Once this is done.. When you reboot and reach the desktop... your AVIRA antivirus ... as well as your Xbox driver will not work.

For Antivirus ... remove AVIRA and install Microsoft Security Essential

Then Reinstall the Xbox driver.

 

[miketh2005]

Mike

Based on the BSOD there are two drivers that has caused this BSOD....

1. avfwim.sys ( which is a AVIRA Antivirus NDIS packet driver) caused and IRP fault twice

2. MijXfilt.sys (Motionjoy driver... used by Xbox) which caused a driver violation.

Now you would need to disable these 2 in order to boot... If you are using the Ubuntu Live CD ... then go the Windows\System32\drivers... look for these two drivers and rename it to avfwin.sys_old and MijCfilt.sys_old. This is make sure that these drivers are not loaded why windows boots...

Once this is done.. When you reboot and reach the desktop... your AVIRA antivirus ... as well as your Xbox driver will not work.

For Antivirus ... remove AVIRA and install Microsoft Security Essential

Then Reinstall the Xbox driver.

Thank you so much. At least we are getting somewhere. Unfortunately I still cannot boot to Windows, but I am getting different errors this time.

*** STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8007FEC060, 0xFFFFFA8007FEC340, 0xFFFFF800033DD460)

Is this the same error written a different way or are we making progress here?

May I ask how you researched the BSOD so that maybe I can fix it myself instead of taking up your time? I really appreciate it, though, I guess it's my pride in me.

Also may I ask why you said to install Microsoft Security Essentials instead of Avira? I download a lot of things, so I want to be protected as much as I can. Is there really little difference in the two?

Thank you so much again, it is really appreciated!

EDIT: My old BSOD is here for comparing purposes:

*** STOP 0x000000F4 (0x0000000000000003, 0xFFFFFA800701A060,0xFFFFFA800701A340, 0xFFFFFA80003393460)

 

[miketh2005]

This is a better tutorial - all SevenForums ones are
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

It said Windows Resource Protection found corrupt files but was unable to fix some of them.

 

[Golden]

Please run it an additional 3 times, rebooting your computer between each run of sfc - sometimes this corrects previously non-correctable corruptions.

 

[miketh2005]

Please run it an additional 3 times, rebooting your computer between each run of sfc - sometimes this corrects previously non-correctable corruptions.

I did it 3 times. No luck.

 

[centaur78]

Thank you so much. At least we are getting somewhere. Unfortunately I still cannot boot to Windows, but I am getting different errors this time.

*** STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8007FEC060, 0xFFFFFA8007FEC340, 0xFFFFF800033DD460)

Is this the same error written a different way or are we making progress here?

Well its the same error.... but can't say for sure what has caused it .... without a dump file to look into. Upload the latest dumps.

May I ask how you researched the BSOD so that maybe I can fix it myself instead of taking up your time? I really appreciate it, though, I guess it's my pride in me.

No problem.. there is lots of tutorial you can google for debugging windows. If you can read codes, know about hardware and software and a little bit of assembly language.. you can pretty much do it yourself

Also may I ask why you said to install Microsoft Security Essentials instead of Avira? I download a lot of things, so I want to be protected as much as I can. Is there really little difference in the two?

We here advice MSE because it has less memory footprint and works well with Windows Firewall. Avira is good too but.. we have seen lots of people have issue with AVIRA,AVAST, NORTON... as a matter of fact.... look at the first point in my previous post .... its the network driver of AVIRA that caused the BSOD !!

 

[miketh2005]

Thank you so much. At least we are getting somewhere. Unfortunately I still cannot boot to Windows, but I am getting different errors this time.

*** STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8007FEC060, 0xFFFFFA8007FEC340, 0xFFFFF800033DD460)

Is this the same error written a different way or are we making progress here?

Well its the same error.... but can't say for sure what has caused it .... without a dump file to look into. Upload the latest dumps.

May I ask how you researched the BSOD so that maybe I can fix it myself instead of taking up your time? I really appreciate it, though, I guess it's my pride in me.

No problem.. there is lots of tutorial you can google for debugging windows. If you can read codes, know about hardware and software and a little bit of assembly language.. you can pretty much do it yourself

Also may I ask why you said to install Microsoft Security Essentials instead of Avira? I download a lot of things, so I want to be protected as much as I can. Is there really little difference in the two?

We here advice MSE because it has less memory footprint and works well with Windows Firewall. Avira is good too but.. we have seen lots of people have issue with AVIRA,AVAST, NORTON... as a matter of fact.... look at the first point in my previous post .... its the network driver of AVIRA that caused the BSOD !!

Ahhhhh. I didn't know it was the dump file that you looked into, I thought it was the BSOD code that was telling you these things, lol. Sorry. I am crap at coding, and tried, lol. I wonder why Microsoft can't release a dump analyzer for amateurs. Oh well. Thank you very much for helping me.

Latest dump: Minidump(2).zip

 

[centaur78]

mike the dumps you uploaded are old.. the latest being dated on 14/11/2012

You mentioned you had a BSOD just recently ???

 

[miketh2005]

mike the dumps you uploaded are old.. the latest being dated on 14/11/2012

You mentioned you had a BSOD just recently ???

Oh man. I just restored Windows in December sometime, so it wouldn't be in November. That must have been an old BSOD that I had fixed (I think I even remember that). So that means this new BSOD is not dumping.

I went ahead and tried to set it to dump with the commands found here: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

I thought that would fix it. But upon restarting the computer it is going back and saying again:

DebugInfoType
0

What the hell?

I tried setting it to 1 and restarted, went to the BSOD, restarted, booted to Linux, and found the dump files were the same. Latest being in November. I was like what the hell? So I went back to command prompt, and did wmic RECOVEROS get DebugInfoType and it was set back to 0! I set it to 2 this time, restarted, and did get DebugInfoType, and again it was RESET back to 0!

Why the hell won't it let me change it to dump???

Is there a different command I need to do or something?

I was using the exact command:

wmic RECOVEROS set DebugInfoType = 2

Do I need to add a Windows directory or something to this maybe?

Thanks again.

 

[miketh2005]

Anyone?

 

[centaur78]

try running this command and let me know the output

reg query \\\HKLM\SYSTEM\CurrentControlSet\Control\CrashControl

then try using this for ex.

wmic recoveros set MiniDumpDirectory = D:\Minidump ( or whichever drive you have)

then try

wmic recoveros set DebugInfoType = 3