Solved BSOD Critical Object Termination

[Vadgebender]

For the past few days I've been getting BSODs around 3-4 times a day periodically. At times it would happen back to back or after a few hours at a time. I've included the attachments as instructed. I'm stumped at what I can do and have little to no experience with this kind of thing.

 

[essenbe]

Hello Vadgebender, I will see if I can be of some help to you. You had 8 dump files in the files you uploaded. 7 of the 8 listed the same thing.

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
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.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800e040b30, Terminating object
Arg3: fffffa800e040e10, Process image file name
Arg4: fffff800033c8270, Explanatory message (ascii)

FOLLOWUP_NAME:  MachineOwner
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  X64_[COLOR=red]0xF4_IOERR_IMAGE[/COLOR]_csrss.exe
BUCKET_ID:  X64_0xF4_[COLOR=red]IOERR_IMAGE[/COLOR]_csrss.exe
ANALYSIS_SOURCE:  KM
[COLOR=red]FAILURE_ID_HASH_STRING:  km:x64_0xf4_ioerr_image_csrss.exe[/COLOR]

An I/O error is a disk read problem usually.

You had one listed as

Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc40009818, ffffffffc000000e, 374039860, fffff8800130363c}
GetPointerFromAddress: unable to read from fffff8000330d278
[COLOR=red]Probably caused by : memory_corruption[/COLOR]
Followup: memory_corruption

From my perspective the memory corruption is the most important. It can cause all of the other ones. But, we will do the easy part first. I am going to give you several things to do. Please read the instructions and follow them. If at any time you don't understand the instructions or have any questions, feel free to ask. I don't mind explaining anything I ask of you.

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Also please run Seatools for DOS on your Mechanical Hard drive, both the long and the short test.
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

Also run check disk http://www.sevenforums.com/tutorials/433-disk-check.html

Make sure you have the latest firmware update for your SSD. The 840 EVO had a firmware problem and issued an update for it. Make sure you have also installed the Performance restoration Update. It supposedly affected the reads from the disk on older data. You can find it about half way down this page Samsung SSD Downloads | Samsung SSD

After that please run a full virus scan with your AV and also run these online sacns.

Scan with Kaspersky TDSSKiller:
Anti-rootkit utility TDSSKiller
Anti-rootkit utility TDSSKiller
ESET online scanner:
Free Virus Scan | Online Virus Scanner from ESET
Free Online Virus Scanner | ESET

Also, you can Download and install Malwarebytes (Malwarebytes | Free Anti-Malware & Internet Security Software) and run a full scan. During the installation, please uncheck the trial real time protection and just use it as an on demand scanner.

Also use Superantispyware ( SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware! ) use the free version and run a full san.

As with all downloads, watch out for the add ons they try to install with it. Just uncheck them and they will not install. After running all of these scans, I believe you will see why people use 2 or 3 anti virus programs. But, you should never have but 1 real time anti virus. Use the others as on demand scans.

After that see if your problem improves any and let us know.

 

[Vadgebender]

sfc /scannow CMD command hangs around 20% for about 50 mins and going still. Gonna try the other tests after this post.

 

[essenbe]

Vadgebender, sfc /scannow is scanning hidden system files. The reason it won't complete is that they have been altered. You are running an Asus OEM_SLP OS on a retail Motherboard. Not only is that not legal, but to be activated it has to alter internal system files.

Counterfeit installations such as yours contain heavily modified code that causes the installation to behave it unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a Genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them

 

[Vadgebender]

Told the friend last week to go buy a copy if he wants me to help him further after dealing with all of this. Since then he's been on his own. I don't really like dealing with thieves and their issues. Sorry for the delayed response.

Gonna close this thread for now. Thank you for your help so far. Issue may have been solved idk but I stopped helping after the last post about the false OS.

 

[essenbe]

Thanks for letting us know. I think it was a good decision on your part.