Firefox froze, then "Windows not responding", then BSOD twice

Hello,

I noticed my pc had blue screened while I was away from it and I restarted.

A few minutes later Firefox froze while I browsing with a few tabs open, but nothing too intensive. I was unable to open task manager with alt-ctrl-delete. I got a message saying something like "windows is not responsive, would you like to close it". The whole desktop became unresponsive and then BSOD.

I disabled UAC (put it on lowest setting) a couple months ago due to a software incompatability, but have since turned it back on AFTER zipping up the perfmon and BSOD reports

Thanks,
Phil


Windows 7 x64
original OS
OEM
2 years old

I removed a microsoft wireless controller from a usb hub and the pc hasn't froze for a couple of hours. Also a small whirring sound I noticed yesterday, which I wasn't sure was new, has gone away.

However, the system has only been stable for a couple hours so I do not know if the problem has been solved

ok, pc froze again. interesting thing is that alt ctrl delete does not work at all when this happens. nothing is responsive except the mouse pointer.

blue screen says KERNEL_DATA_INPAGE_ERRROR and 0x0000007A

Software Concerns:

Code:

Start Menu\Programs\Defraggler	
Start Menu\Programs\MSI Kombustor

The defrag program may interfere with the use of your SSD. Remove it promptly.

• I personally do not recommend 3rd party defrag tools. I have seen them damage restore points and even cause blue screen crashes. Windows has some nice command line flags for the defrag command that will accomplish the same tasks as 3rd party programs. The -b and -w flags will defrag boot files and the boot registry items as well as compact the data to the center of the disk for faster access.
  defrag c: -b
  defrag -c -v -w
  The first command optimizes boot performance for the Windows drive by defragmenting boot files and boot registry items.
  
  The second command includes all drives on the system through the -c command and optimizes the drives by compacting the data to the center of the disk. Verbose output through the -v option is optional to provide the user with more information about the defrag tasks. The commands have to be run in an Elevated Command Prompt.
  
  For more flags, see Disk Defragmenter - Open and Use.
  
  
• MSI Afterburner/RivaTuner is known to cause instability with systems. Please remove the software. Software overclocking does not provide reliable overclocking. Overclocking should be accomplished through the BIOS or through the graphics card manufacturer's software.

Analysis:

BugCheck 0x7A

0x7A:

Windows Dev Center - Hardware said:

Cause

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:

• 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
  
  
• 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
  
  
• 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
  
  
• 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
  
  
• 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).

Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check.

Resolution

Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.

If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.

Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.

Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.

Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.

Make sure that the latest Windows Service Pack is installed.

If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error.

Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

The above was taken from Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR.

Hard disk problems:

Your crashes primarily indicate hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• 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 (you may need to search for wininit instead of chkdsk).
  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.
  
  
• Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Check Windows for corruption. 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. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

SSD Disappears:

Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.

1. Power off the system.
2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
6. Let the computer remain in the BIOS for 20 minutes.
7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
8. Leave the drive disconnected for 30 seconds to let all power drain from it.
9. Replace the drive connection(s) and then do steps 4-8 again.
10. Repeat steps 1-4.
11. Start your computer normally and run Windows.

The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community

While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

Thanks for the fantstic post writhziden, I think it might be solved.

First I removed both Defraggler and MSI Kombustor from my system, though I'm pretty sure I wan't using them.

I ran disk check on my main hard drive, a Crucial 128g SSD, but running disk check on my secondary 1000g drive was taking so long that I cancelled out and decided to move on to your other suggestions. Also my pc had been crashing regularly and I didn't think it'd make it through the test.

I updated my chipset drivers using the upgrade utility on the Intel site.

Windows crashed again once after the upgrade.

Then I upgraded the firmware on my Crucial SSD drive and this seemed to do the trick. My pc has been running solid over a day since then through intensive activity, whereas before it was crashing about once an hour even when idle.

I forgot to add that somewhere in there I ran Malwarebytes and it didn't find anything.

Thanks for the help!

Phil

Ah, wish you'd said it was happening once an hour from the start...

https://www.sevenforums.com/crashes-d...ml#post1793840

Oh well, at least it is solved now. :) Glad I could help, and you are quite welcome.

When you are confident it is solved, let us know, and you may also mark the thread solved at that time.

The pc had only crashed twice at the time of my first post, as in the thread title. I posted again when it crashed one more time. Between then and your post is when the crashes began to increase in frequency.

I greatly appreciate your help and consider this problem solved.

Ah, that makes perfect sense. Sounds like you were nearing the end of the firmware's life period and finally reached it during your time getting help. Thanks for explaining that, and my apologies for my assumptions.

I am happy to see it solved!!