Frustrating freezing and BSODs

B Baggus · 23 Mar 2012

Okay, i had a very detailed post about my problem, however my computer decided to delete all my text for some reason, and i REALLY don't feel like typing all of that again. So, this post will pretty much be just a list but still get the point across.

Problems: Computer runs very slow. Computer freezes randomly. Does not want to boot past windows startup except for in safe mode(SOMETIMES). IF IT BOOTS takes and an incredibly long time to get to the desktop (20-45min). Does not want to run programs. Runs EXTREMELY slowly (makes a windows 95 pc look like a speed demon.) Random restarts, restart loops, and shutdowns. Sometimes after turning on it will immediately shut off then turn back on. Keeps recommending windows repair on startup. Wants to run chkdsk, then freezes on it.

Fixes tried: Malware detection programs. Hardware diagnostic programs. registry tools. disk defrags. Driver updates. Windows updates. BIOS update System restore. Windows repair tool. Repair installation (twice). WINDOWS 7 CLEAN INSTALLATION (twice).

Did any of these fix any of the problems? Absolutely not. Exactly the same as the first day it started happening. So not only did I lose all programs and files, but my pc still runs like crap. Also, this is a high end pc under a year old.

ANY help would be EXTREMELY appreciated as this issue is frustrating the hell out of me.

Thanks

Here are some examples of the errors Im encountering...

computer name: HOME-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4275277824 total
VM: 2147352576, free: 1983229952
-------------------------------------------------------------------------------

On Fri 3/23/2012 9:08:27 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005D0B060, 0xFFFFFA8005D0B340, 0xFFFFF80002F852D0)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
-------------------------------------------------------------------------------

On Fri 3/23/2012 7:37:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032312-27783-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005E5C060, 0xFFFFFA8005E5C340, 0xFFFFF80002F7DE20)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
-------------------------------------------------------------------------------

On Sat 3/3/2012 7:20:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030312-39655-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x52047)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000006, 0xFFFFF80002C71047, 0xFFFFF880046627E8, 0xFFFFF88004662040)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
-------------------------------------------------------------------------------

BSOD ERROR MESSAGE:

*** STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8005A19550, 0xFF8005A1927, 0xFFFAxFFFFF80002F8CE20)

*** STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8006287060, 0xFFFFFA8006287340, 0xFFFFF8002F932D0)

writhziden · 23 Mar 2012

Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with more information.

I can do a somewhat cursory analysis looking at the crash bugcodes: CRITICAL_OBJECT_TERMINATION signifies one of two possibilities: A failing hard disk or a virus.

Run the long and short tests of SeaTools
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
Use the Microsoft Standalone System Sweeper Beta | Microsoft Connect to check for viruses outside Windows.

B Baggus · 23 Mar 2012

Okay this may take a while. The only reason I didn't follow the posting instructions is that it quite hard to do basically anything on the computer.

writhziden · 23 Mar 2012

I understand. If you'd like, you could start with the troubleshooting steps I gave and see what turns up. Those steps will be among what I suggest, regardless.

B Baggus · 23 Mar 2012

I cannot do anything from the event viewer. This is what I get.

writhziden · 23 Mar 2012

That is odd. Are you sure your Windows 7 install disc is not faulty?

Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

Realized you may not be able to do that too well through Windows with as slow as things are, so here are the boot instructions for SFC: SFC /SCANNOW : Run in Command Prompt at Boot

B Baggus · 23 Mar 2012

Here are the results...

X:\Sources>sfc /scannow /offbootdir=d:\ /offwindir=d:\windows
Beginning system scan. This process will take some time.

Windows Resource Protection did not find any integrity violations.
X:\Sources>_

writhziden · 23 Mar 2012

Do you get the same message if you run Event Viewer in elevated mode?
Start Menu -> eventvwr (in Search programs and files); do not hit enter -> right click eventvwr.exe -> Run as administrator

B Baggus · 23 Mar 2012

Yep, same deal there.

B Baggus · 23 Mar 2012

Also, I have managed to get this in the proper format.