Solved Frustrating freezing and BSODs

[B Baggus]

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]

Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.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 http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  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]

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]

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]

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

 

[writhziden]

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

• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html 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: http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

 

[B Baggus]

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]

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]

Yep, same deal there.

 

[B Baggus]

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

 

[writhziden]

You have a number of these errors:

Event[113]:
  Log Name: System
  Source: atapi
  Date: 2012-03-23T19:43:47.128
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Home-PC
  Description: 
The driver detected a controller error on \Device\Ide\IdePort6.

I do not think your hard disk controller is working correctly with Windows. How is your BIOS configured for the hard disk controller? IDE/AHCI?


Make sure you have the drivers installed through SATA from your motherboard site: ASUS - Motherboards- ASUS P8P67 LE
You want the Marvell 1.0.0.1045 and Intel Rapid Storage Technology Version 10.1.0.1008 drivers installed.

 

[B Baggus]

Its IDE, I believe.

 

[B Baggus]

Okay, I am installing the drivers to a flash drive to transfer to the problem computer. After driver installation do you believe this may remedy the problem?

 

[writhziden]

It may. Your controller errors are sometimes less than a second apart, which could definitely explain the freezing and slowdowns you are experiencing.

 

[B Baggus]

Alright, I've installed the drivers you suggested. However, it doesn't seem to have made a difference in the performance?

 

[B Baggus]

Also, I have a Windows.old and a Windows.old.0 from previous re-installations. Could these folders be creating conflincts with the currently installed OS?

 

[B Baggus]

I just revieved the following error:

Status: 0xc00000e9

Info: An unexpected I/O error has occured.


Edit: After running Acronis Disk Monitor it didn't detect any hardware problems with the HDD but said something about critical I/O errors.

 

[B Baggus]

Also, Im not sure if this pertains to anything but when running chkdsk I get a lot of orphaned files.

 

[B Baggus]

I am now getting a blue screen upon start up after the windows logo saying:

STOP: c0000021a {Fatal System Error}
The verification of a knownDLL failed. system process terminated unexpectedly
with a status of 0x000012f (0x0023fa90 0x00000000).
The system has been shut down.

After restarting it suggested running windows repair. I can't exactly remember what it said after running but it was something like this...

Windows startup repair was unable to repair your machine.
*-----------------*
*diagnostic reports*
*-----------------*
Root cause: 1
Something about "corrupt volume"
Attempted to fix with chkdsk
Status: failed


Also recieving a black screen saying:

Windows has encountered a problem communicating with a device connected to your computer.

This error can be caused by unplugging a removable storage device such as an external USB drive while the device is in use, or by faulty hardware such as a hard drive or CD-ROM drive that is failing. Make sure any removable storage is properly connected and then restart your computer.

If you continue to recieve this error message, contact the hardware manufacturer.


Status: 0x00000e9

Info: An unexpected I/O error has occured.


Other times I'll get the black screen with just a large "P_" in the top left with a blinking cursor after it. Somtimes instead of a "P" it wall be a page filled with just random shapes, characters, and symbols.

After recieving those messages, the computer is no longer able to boot.

 

[writhziden]

It appears you have hard disk errors or a hard disk that is failing. What messages did you receive from the disk check? Did it make corrections to the file system? If so, the disk check needed to be run again to make sure it no longer had any problems.

• Use http://www.sevenforums.com/tutorials/666-advanced-boot-options.html to select Repair Your Computer and get to the http://www.sevenforums.com/tutorials/668-system-recovery-options.html. Then select the command prompt. Do the following:
  
  chkdsk /r c:
  chkdsk /r d:
  chkdsk /r e:
  chkdsk /r f:​
  .etc until you get the message that the volume could not be opened for direct access. For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run chkdsk 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.
  
  I realize you may only have one disk show up in Windows explorer, but you may have more than one disk through recovery options. This is because the system creates a hidden boot partition (which will be C: in recovery), you may have a recovery partition for your PC that is hidden (which will be D: in recovery), and you will have your primary Windows partition (which may be E: in recovery). A custom PC will likely have at least C: and D: to scan.

I would also check all the connections between the motherboard and hard disks. Avoid Static Damage to Your PC when you check.


If you are able to, obtain the DOS version of SeaTools using another system to download and burn a CD/DVD. Run the short and long tests on your hard disk to see if the disk is failing. If you have important information on your system that you need to backup, let us know before running the tests and we will provide steps to backup the data.