Bluescreen.

F

farmerjohn1324

Member
I just got the bluescreen, but when I run BlueScreenView, nothing comes up.

Here's what happened: It was running slow, so I ran Malwarebytes and quarantined 22 files. Then, I restarted the computer and it was still running slow and went to the blue screen.

I restarted and ran BlueScreenView, but nothing shows up.

I am currently doing an Avast scan.

I know that the computer has enough RAM and that the CPU is fast enough to not be causing the problem.

Why does nothing show up on BlueScreenView.
 
Did you run a temp file remover program? If so, then you deleted the dump file. Go to C:\windows\minidumps and see if there are any files inside that folder.
 
johnb35 said:
Did you run a temp file remover program? If so, then you deleted the dump file. Go to C:\windows\minidumps and see if there are any files inside that folder.
Click to expand...

I did not run any temp file removers since the blue screen. The folder c:\Windown\minidumps does not exist on this computer.

I am running Windows 7 on an HP Notebook 2000.
 
Do you remember what the bluescreen said? Maybe you don't have the setting enabled to save dump files.

 
It was a bit too long to remember. It took up the whole page. If I did not have these settings saves, is there no way to find out what caused the BlueScreen and I should just hope it doesn't happen again?

I cannot find this Startup and Recovery screen that you're showing. Is it in Control Panel?

Without starting a new thread...

What could the reasons for this be? All Malware was quarantined, albeit recently. There are no viruses. There is enough RAM and CPU. What could the potential reasons be?
 
There's another program called Whocrashed you may want to check out. It will tell you if the logs are on too.
 
I'd also untick the automatically reboot field in the previous screenshot so you can jot down some details as well if you're having problems locating it.
 
Make sure you are saving the dump files.

Right click Computer | Properties | click on system protection | Advanced Tab.

  • Click on the Settings... button located under Startup and Recovery.
  • Under System failure make certain that Automatically restart is unchecked, if it is checked, uncheck it.
  • Click the drop-down menu under Write debugging information and select Complete memory dump if that option is not already selected.
  • Make certain that you know the path where the dumps are saved, which by default will be %SystemRoot%\MEMORY.DMP. (C:\Windows\MEMORY.dmp)
  • Make certain that Overwrite any existing file is checked, if it is unchecked, check it.
 
I did all of that except that "Complete memory dump" was not an option. It only had "Kernel memory dump" and "Small memory dump (256 KB)." Kernel is selected.

I noticed that the file is not in the MiniDump folder that was talked about earlier. Does this mean the files from the crashes might exist?
 
The next time it blue screens, write the code down that it gives you or the filename it lists. Not sure why the dumps aren't being saved.
 
A problem has been detected and windows has been shut down to prevent damage to your computer.

KERNEL_DATA_INPAGE_ERROR

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware
or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as
caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to
select Advanced Startup options, and then select Safe Mode.

Technical information:

***STOP: 0x0000007A (0xFFFFF6FC40008F08, 0XFFFFFFFFC00000B5, 0X0000000110E33860, OXFFFFF880011E1EF0)

*** dfsc.sys - Address FFFFF880011E1EF0 base at FFFFF880011D4000, Date Stamp 4ce79447

Collecting data for crash dump...
Initializing disk for crash dump...
Physical memory dump FAILED with status 0xC000009c.
Contact your system admin or technical support group for further assistance.

No dump file saved. I posted another one about MS Office, but maybe the problems are related. Where do I get TDSskiller from?
 
Last edited by a moderator:
Here's the explanation of that BSOD

This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.
Click to expand...

If the I/O status is C0000185 and the paging file is on a SCSI disk, the disk cabling and SCSI termination should be checked for problems. Check your computer for viruses, using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. An I/O status code of 0xC000009C or 0xC000016A normally indicates the data cannot be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map out the bad sector. If Autochk does not scan the hard disk for errors, manually launch the disk scanner. Run Chkdsk /f /r on the system partition. Restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r. Caution: If your system partition is formatted with the FAT file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOSbased hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks. Another common cause of this Stop message is failing RAM. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. Check that all network adapters in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure network adapter contacts are clean. Check the System Log in Event Viewer for additional error messages that might help pinpoint the device causing the error. Disabling memory caching of the BIOS might also resolve it. Finally, if all the above steps fail to 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 also cause this error. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.
Click to expand...
 
You must log in or register to reply here.
Back
Top