Runtime Error

Hi, all. I got a used Toshiba laptop, with Win 7 Pro:



I get this error:



The above error happens when I boot up my laptop. Sometimes, it will do it if it goes to sleep. Occasionally, I'll get "the blue screen of death," usually after I wake up my PC, and when it comes back online, I get this message, 4 - 8 of these boxes.

I tried a couple of fixes from the MS site, but nothing. Help?

 

A runtime error occurs because hardware is preventing a program from doing something but normally you can see what the program affected is. Is there anything on your error message that we cannot see such as Internet Explorer or some other program or browser being affected?
http://windows.microsoft.com/en-us/windows/what-is-runtime-error#1TC=windows-7

 

I was given the suggestion to use BlueScreenView. Here's what I have:

==================================================
Dump File : 060815-32183-01.dmp
Crash Time : 6/8/2015 10:18:17 AM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`50036168
Parameter 2 : ffffffff`c0000185
Parameter 3 : 00000001`198ef820
Parameter 4 : fffff8a0`06c2d8ae
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72a40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18798 (win7sp1_gdr.150316-1654)
Processor : x64
Crash Address : ntoskrnl.exe+72a40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060815-32183-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 283,080
Dump File Time : 6/8/2015 10:22:19 AM
==================================================

There are 6 crashes with ntoskrnl.exe+72a40. 1 has CLFS.SYS+23000:

==================================================
Dump File : 060115-71074-01.dmp
Crash Time : 6/1/2015 12:54:07 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`400065e0
Parameter 2 : ffffffff`c0000185
Parameter 3 : 00000000`b47c8860
Parameter 4 : fffff880`00cbc000
Caused By Driver : CLFS.SYS
Caused By Address : CLFS.SYS+23000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+72a40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060115-71074-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 283,080
Dump File Time : 6/1/2015 12:56:21 PM
==================================================

 

Hi, it is looking like a corrupt operating system file to me.
This might be corrected by a system file scan using the sfc /scannow.

Here is how to do it once you have managed to get it to fully boot up.

Click on the start orb and type into the search box Cmd or Cmd prompt.

A small black icon and Cmd should be at the top of the list. RIGHT click on that line and choose "Run as administrator" You might get the UAC asking if you want to run it, just click yes.
Copy and paste or type this into the box that opens and at the flashing cursor. (Note the space after sfc before the /

sfc /scannow

Then hit the enter key.

If it can it will find and repair any corrupt files.
If it finds files it cannot repair, try running it at least three more times as it can quite often fix things the second or third time round.
Let us know how you get on.

Nev.

 

Windows Resource Protection could not start the repair services.

Things are getting worse. Today, I couldn't even get to boot up, after "death blue screen." I tried system restore, and most of the other options. Even trying my Win & CD, it won't go off that, now. The only ways I can boot up are in safe mode [and with networking].

 

What are the error codes at the bottom of the BSOD?

 

I think you need a new hard drive and you need to boot to safe mode first with an external hard drive attached so you can copy off your files and data first and judging by the fact thihgs are getting worse I would not let much time lapse before doing so.

 

Hmmm... Seems like a lot of work.. Based on your log, I saw a combination of problems but I guess you can start by looking at the KERNEL_DATA_INPAGE_ERROR

 

I would agree that sure sounds like a failing hard drive. What make of hard drive is it?