BSOD after finding laptop at System Repair

lenovoY560 · 13 Jul 2012

Earlier this morning I restarted my laptop to the desktop and left it running. After coming back to my room a couple hours later, I noticed that there was a System Repair window on the screen. And whenever you see this there is always a state of being very concerned.

I restarted my laptop only to be directed to the BSOD. I restarted the laptop, only to be presented with the same screen. I immediately took a picture with my cell phone to make sure I could read anything that could give me a clue as to what the error could be. Below are the error codes:

***STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA800CBABB30, 0xFFFFFA800CBABE10, 0xFFFFF80003B8B510)

I started up the laptop and was prompted with options to either start Windows as it usually would or to try and go through the system repair. I tried system repair again. I was brought to a screen to try and do a system restore to an earlier point. The closest restore point was earlier today and that was due to some critical updates that windows had automatically had downloaded and installed. So, I tried hitting that restore point only to be shown a window that stated that system restore was unsuccessful with the restore. I tried again with a restore point from a week ago and was again shown the same unsuccessful window.

The next thing I did was scour the internet for recent BSOD listings. Everything told me to get into Safe Mode by hitting the F8 button after restarting the computer. The first time I tried it, I hit Safe Mode (without networking or command prompt). I saw the screen fill up with file listings as it usually does, again to be prompted with the BSOD. The next time I tried hitting F8 I was only shown two options:
Start Windows normally or
the system restore option.

I tried again searching the internet on my phone to try and first power down the laptop, take out the battery and hold down the power button for 30 seconds, which I first did. Then I went into the command prompt located in the system restore window. I performed chkdsk /r on the C: drive by typing:
C:, then enter and
chkdsk /r

I was then prompted with something about having to dismount the C; drive in order to check the drive, and pushed Yes for that.

After that was completed I was successfully able to find all the boot options in the F8 menu when you restart the computer. This was an arduous journey to get this far. Took quite awhile and there were many unsuccessful other attempts before trying this route.

So, I tried the Safe Mode with Networking and booted successfully into Safe Mode. I tried running Norton which stated that I couldn't perform that action. So I tried restarting, FINALLY to boot into Windows. I am currently performing a full system scan with Norton 360 and will post my findings.

I am also posting the minidump files that were asked for, in order to post in this forum below.

System Specs:
Lenovo Y560
Intel Core i7CPU
1.73 GHz
64 bit Operating System
8.00 GB RAM

Basic System Spec:
Windows 7 Premium x64
Original installed OS
OEM
Age: 2yr

Thank you for any advice or info you find from the files provided.

writhziden · 13 Jul 2012

The crash report yields little new information. It tells me that Windows or its registry was corrupted. The disk check probably resolved the problem, but good steps to run Norton. Let us know if problems persist. My hypothesis is that your hard disk was corrupted and needed to be cleaned up for Windows to run properly.

My hypothesis is further substantiated by:

Code:

Event[108]:
  Log Name: System
  Source: Microsoft-Windows-StartupRepair
  Date: 2012-07-13T00:45:58.993
  Event ID: 1213
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Beast
  Description: 
Repaired the corrupted files from backup.

Startup Repair was able to repair some corrupted files from backup. That may not have helped if the file system itself was corrupted, though. Repairing/replacing the corrupted files with files from backup into a corrupted file system will just cause the files to be corrupted again.

It appears Norton was hanging prior to this happening, as well. That may indicate Norton is corrupted or a malicious item is on the system. I would be inclined to think it is corrupted, but let us know what Norton finds.

Code:

Event[2910]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-07-09T18:29:11.629
  Event ID: 7011
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Beast
  Description: 
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the N360 service.