BSOD Disk Error. Press any key to restart. Lenovo Y560

How have you got the idea of disc error?

There are two crash dumps only (and nothing else) in the zip, and both of them are pointing out to a very common cause, an outdated XBox USB wireless controller.

Update it from here: Software Downloads | Microsoft Hardware

Also, install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

AVG antivirus, which is a crapware only, is contributing to the issues as usual.

Code:

fffff880`031b5098  fffff880`0f18b65aUnable to load image \SystemRoot\system32\DRIVERS\AVGIDSDriver.Sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AVGIDSDriver.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.Sys
 AVGIDSDriver+0xb65a

Uninstall AVG following http://www.avg.com/us-en/utilities . Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one, for a safety reason, as the installed antivirus is failing.

Let us know the results.
_________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {5, 0, 1024, fffffa80043c4e40}

*** WARNING: Unable to verify timestamp for xusb21.sys
*** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
Probably caused by : xusb21.sys ( xusb21+2888 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000005, A framework object handle of the incorrect type was passed to
    a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001024, Reserved.
Arg4: fffffa80043c4e40, Reserved.

Debugging Details:
------------------


BUGCHECK_STR:  0x10D_5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88000e54113 to fffff8000426f880

STACK_TEXT:  
fffff880`031c3678 fffff880`00e54113 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001024 : nt!KeBugCheckEx
fffff880`031c3680 fffff880`2330a888 : fffff880`2330a4cc 00000000`00000000 fffffa80`0b253360 fffffa80`0b253300 : Wdf01000!imp_WdfSpinLockAcquire+0x47
fffff880`031c36d0 fffff880`2330a4cc : 00000000`00000000 fffffa80`0b253360 fffffa80`0b253300 fffffa80`0b253300 : xusb21+0x2888
fffff880`031c36d8 00000000`00000000 : fffffa80`0b253360 fffffa80`0b253300 fffffa80`0b253300 fffffa80`0b253360 : xusb21+0x24cc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
xusb21+2888
fffff880`2330a888 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  xusb21+2888

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: xusb21

IMAGE_NAME:  xusb21.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a848f49

FAILURE_BUCKET_ID:  X64_0x10D_5_xusb21+2888

BUCKET_ID:  X64_0x10D_5_xusb21+2888

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x10d_5_xusb21+2888

FAILURE_ID_HASH:  {a6108764-9902-1ba7-ad7e-1007cd9377cc}

Followup: MachineOwner
---------

0: kd> lmvm xusb21
start             end                 module name
fffff880`23308000 fffff880`2331a100   xusb21   T (no symbols)           
    Loaded symbol image file: xusb21.sys
    Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
    Image name: xusb21.sys
    Timestamp:        Fri Aug 14 03:40:17 2009 (4A848F49)
    CheckSum:         00020048
    ImageSize:        00012100
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

EDIT: We need to see what is controlling ACPI externally there. Upload the list of all the third party drivers Using NirSoft DriverView :

• Download and execute Driverview
• View > Hide Microsoft Drivers
• Edit > Select all
• File > Save Selected Items
• In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
• Zip the .txt file and upload it.

Also upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Apparently there is no issue with Storage devices. But as it is an old laptop (and most probably be factory installed), some things are must to check.

Uchiha said:

I'm a bit reluctant about having to switch security systems (AVG to Security Essentials). SO you're gonna have to convince me otherwise.
My XBox driver was up-to-date (v1.2)
I've uploaded everything else you asked for.
Attachment 305386

Attachment 305387

I dont want to convince you. I interpret the data recorded by the memory during a BSOD; and nothing else. If you are reluctant at anything, that is your loss, not of me.

Please inform us only after completing the steps suggested, otherwise no further troubleshooting is possible with keeping the crasher in the system.

Hope you understand this point. Rest is on you, coz it is your computer.

BTW, your XBox driver was not up to date at all.

Code:

0: kd> lmvm xusb21
start             end                 module name
fffff880`23308000 fffff880`2331a100   xusb21   T (no symbols)           
    Loaded symbol image file: xusb21.sys
    Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
    Image name: xusb21.sys
    Timestamp:        Fri Aug 14 03:40:17 2009 (4A848F49)
    CheckSum:         00020048
    ImageSize:        00012100
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

xusb21.sys : As per Carrona.org:

Driver Description: XBox USB wireless controller
BSOD issues in Win7 with 2009 driver (found in mid-2012)

So that is just one of your wrong idea about your system.

Suggesting you again, take all the suggestions and report back.

Uchiha said:

So you want me to go for Microsoft Security Essentials?

Lol, I dont want, I suggest only :)
Because, AVG causes such a thing in a huge number of cases, as it is doing in your system.

Uchiha said:

What about the attachments I sent you?

Refer to post #5 .... see why I asked for the driverview output ....

Arc said:

EDIT: We need to see what is controlling ACPI externally there.

And now we know .....

Code:

==================================================
Driver Name       : AcpiVpc.sys
Address           : 00000000`088CC000
End Address       : 00000000`088E2000
Size              : 0x00016000
Load Count        : 1
Index             : 110
File Type         : System Driver
Description       : ACPI Virtual Power Controller Driver
Version           : 6.1.2601.0
Company           : Lenovo Corporation
Product Name      : Lenovo
Modified Date     : 10/19/2009 6:10:50 AM
Created Date      : 10/19/2010 1:58:44 PM
Filename          : C:\windows\system32\DRIVERS\AcpiVpc.sys
File Attributes   : A
Service Name      : ACPIVPC
Service Display Name: Lenovo Virtual Power Controller Driver
Digital Signature : 
==================================================

I cannot recommend you to keep it; as it will cause issues continuously. I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.