WIN 8.1 BSOD DRIVER_POWER_STATE_FAILURE (9f)

G

GooonE

Well-known member
Joined
May 6, 2016
Posts
80
Hi,

I'm getting BSOD after I awake my computer from sleep.
1. Put computer on sleep. 2. Wake him up. 3. Wait... 4. ??? 5. BSOD

OS - Windows 10, 8.1, 8, 7, Vista ? Windows 8.1
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? Windows 8.1
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? I bought it and it came with windows 8.1
· Age of system (hardware) At least two years
· Age of OS installation - have you re-installed the OS? Just restore

· CPU Intel i7-4710 HQ
· Video Card NVIDIA GTX 840M
· MotherBoard - (if NOT a laptop)
· Power Supply - brand & wattage (if laptop, skip this one)

· System Manufacturer
· Exact model number (if laptop, check label on bottom) Lenovo Y50-70

· Laptop or Desktop? Laptop

I tested RAM with memtest and I passed test.

Best regards,

GooonE
 

Attachments

Hi GooonE. :welcome:

This is for starters (I didn't analyzed your files and by the way there are experts that will help you better than me):

  • Are you under/over-clocking your PC?
    If yes, try to run it in normal conditions.

  • When have you cleaned your heatsinks, fans and their "breathers"/"air slits"(???) last time? And put a new layer of thermal past on the processor?
    If you didn't already do it, try it... I think you should already know how to do it, but if this isn't the case, ask a friend of yours.

  • What antivirus are you using? And firewall? And antimalware?
    It is usually better to try uninstalling third party suites and try to use on-board MS antimalware (Windows defender), antivirus (MS essentials) and firewall.
    You could have installed different programs of that type in the past: those information could also help (i.e. What AV/FW/AM suites did you use).

  • Did you install virtual drives - disk imaging software (like as examples Daemon tools, alcohol 52%, VirtualCloneCD, and so forth)? And what?
:wave:
 
Hi GooonE,

Please update your Realtek drivers & check Lenovo for driver & BIOS updates.
It seems the Realtek webcam driver has been flagged.
Driver Reference Table - rtsuvc.sys
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe001ffa30060, Physical Device Object of the stack
Arg3: ffffd000a956a960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: [COLOR="#FF0000"]ffffe00206786340[/COLOR], The blocked IRP

6: kd> !irp [COLOR="#FF0000"]ffffe00206786340[/COLOR]
Irp is active with 19 stacks 17 is current (= 0xffffe00206786890)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  1 ffffe001ffa30060 00000000 00000000-00000000    pending
	       \Driver\usbccgp
			Args: 00041100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 [COLOR="#FF0000"]ffffe001ffa50a20[/COLOR] 00000000 fffff80047d3776c-ffffe002061bf640 Success Error Cancel pending
	       \Driver\ksthunk	nt!PopRequestCompletion
			Args: 00041100 00000001 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe002061bf640    

			Args: 00000000 00000000 00000000 00000000

6: kd> !devobj [COLOR="#FF0000"]ffffe001ffa50a20[/COLOR]
Device object (ffffe001ffa50a20) is for:
 InfoMask field not found for _OBJECT_HEADER at ffffe001ffa509f0
 \Driver\ksthunk DriverObject ffffe001ff73a200
Current Irp 00000000 RefCount 0 Type 0000002f Flags 00002040
DevExt ffffe001ffa50b70 DevObjExt ffffe001ffa50b78 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) ffffe001ffa50c20Unable to load image \SystemRoot\system32\DRIVERS\rtsuvc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR="#FF0000"]rtsuvc.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for rtsuvc.sys
 \Driver\rtsuvc
Device queue is not busy.

6: kd> lmvm rtsuvc
Browse full module list
start             end                 module name
fffff800`2ac18000 fffff800`315b5000   rtsuvc   T (no symbols)           
    Loaded symbol image file: rtsuvc.sys
    Image path: \SystemRoot\system32\DRIVERS\rtsuvc.sys
    Image name: rtsuvc.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR="#FF0000"]Tue Jun 10 17:44:22 2014[/COLOR] (539727D6)
    CheckSum:         008C11B6
    ImageSize:        0699D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 
xilolee said:
Hi GooonE. :welcome:

This is for starters (I didn't analyzed your files and by the way there are experts that will help you better than me):

  • Are you under/over-clocking your PC? No
    If yes, try to run it in normal conditions.
  • When have you cleaned your heatsinks, fans and their "breathers"/"air slits"(???) last time? And put a new layer of thermal past on the processor? A long time ago but it doesn't matter
    If you didn't already do it, try it... I think you should already know how to do it, but if this isn't the case, ask a friend of yours.
  • What antivirus are you using? And firewall? And antimalware? - Windows Defender + MBAM + my brain
    It is usually better to try uninstalling third party suites and try to use on-board MS antimalware (Windows defender), antivirus (MS essentials) and firewall.
    You could have installed different programs of that type in the past: those information could also help (i.e. What AV/FW/AM suites did you use).
  • Did you install virtual drives - disk imaging software (like as examples Daemon tools, alcohol 52%, VirtualCloneCD, and so forth)? And what? - Nope
:wave:
Click to expand...

axe0 said:
Hi GooonE,

Please update your Realtek drivers & check Lenovo for driver & BIOS updates.
It seems the Realtek webcam driver has been flagged.
Driver Reference Table - rtsuvc.sys
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe001ffa30060, Physical Device Object of the stack
Arg3: ffffd000a956a960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: [COLOR=#FF0000]ffffe00206786340[/COLOR], The blocked IRP

6: kd> !irp [COLOR=#FF0000]ffffe00206786340[/COLOR]
Irp is active with 19 stacks 17 is current (= 0xffffe00206786890)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  1 ffffe001ffa30060 00000000 00000000-00000000    pending
           \Driver\usbccgp
            Args: 00041100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 [COLOR=#FF0000]ffffe001ffa50a20[/COLOR] 00000000 fffff80047d3776c-ffffe002061bf640 Success Error Cancel pending
           \Driver\ksthunk    nt!PopRequestCompletion
            Args: 00041100 00000001 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe002061bf640    

            Args: 00000000 00000000 00000000 00000000

6: kd> !devobj [COLOR=#FF0000]ffffe001ffa50a20[/COLOR]
Device object (ffffe001ffa50a20) is for:
 InfoMask field not found for _OBJECT_HEADER at ffffe001ffa509f0
 \Driver\ksthunk DriverObject ffffe001ff73a200
Current Irp 00000000 RefCount 0 Type 0000002f Flags 00002040
DevExt ffffe001ffa50b70 DevObjExt ffffe001ffa50b78 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) ffffe001ffa50c20Unable to load image \SystemRoot\system32\DRIVERS\rtsuvc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#FF0000]rtsuvc.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for rtsuvc.sys
 \Driver\rtsuvc
Device queue is not busy.

6: kd> lmvm rtsuvc
Browse full module list
start             end                 module name
fffff800`2ac18000 fffff800`315b5000   rtsuvc   T (no symbols)           
    Loaded symbol image file: rtsuvc.sys
    Image path: \SystemRoot\system32\DRIVERS\rtsuvc.sys
    Image name: rtsuvc.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=#FF0000]Tue Jun 10 17:44:22 2014[/COLOR] (539727D6)
    CheckSum:         008C11B6
    ImageSize:        0699D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Click to expand...

Hi,

thanks for posting. How did you figured out it's "Realtek webcam driver"? Because I read on microsoft forums that it's pointing on 'usbccgps.sys' but doesn't mean it's his fault.
I don't think updating bios will help.

I can't find Realtek webcam driver but I will update the Network adapter, "Sound, Video and Game Controllers" using SlimDrivers.

Best regards,

GooonE
 
Usbccgps.sys is a Windows driver, a Windows driver is basically never the cause but this driver does indicate issues with the USB devices or the USB drivers.
I can't really say what happens, I don't have a fine idea of what happens but I do know a few things that I can do blindly without knowing what happens, though it would help me if I knew what happens when I'm doing things :smile9:

I recommend against the use of driver update programs, you should only install drivers that Lenovo provides for your laptop.
Laptop manufacturer usually alter their drivers, this forced their customers to only use those drivers for proper functioning.
Of course you can install other drivers, but you should then expect problems.
Back to driver update programs, everytime I saw someone using them they had to either use a restore point or a backup from 3rd party software or they had to clean install Windows again to get rid of the problems caused by driver update programs.
 
axe0 said:
Usbccgps.sys is a Windows driver, a Windows driver is basically never the cause but this driver does indicate issues with the USB devices or the USB drivers.
I can't really say what happens, I don't have a fine idea of what happens but I do know a few things that I can do blindly without knowing what happens, though it would help me if I knew what happens when I'm doing things :smile9:

I recommend against the use of driver update programs, you should only install drivers that Lenovo provides for your laptop.
Laptop manufacturer usually alter their drivers, this forced their customers to only use those drivers for proper functioning.
Of course you can install other drivers, but you should then expect problems.
Back to driver update programs, everytime I saw someone using them they had to either use a restore point or a backup from 3rd party software or they had to clean install Windows again to get rid of the problems caused by driver update programs.
Click to expand...

Hello,

thank you for the response. I didn't have problem with SlimDrivers so far and I found the program from reddit . I updated lenovo easy camera.

I have one more question, which one I should update and which one I should not?

utohVJD.png

VFJxBFw.jpg

5HnJ0xb.jpg

yvVpyv7.jpg


Best regards,

GooonE
 
You should choose NO drivers from it!
I highly recommend that you revert the changes that this program has made using a restore point.
You don't need this software, all the drivers you need are provided by Lenovo.
 
How did you figured out it's "Realtek webcam driver"? Because I read on microsoft forums that it's pointing on 'usbccgps.sys' but doesn't mean it's his fault.
Click to expand...
To answer this question better:
My experience is that when the Windows USB drivers are being flagged it often is a USB network adapter that is the root cause, unfortunately I couldn't see if such a device is used as the msinfo32 file is missing. I was planning on posting instructions for you to provide us the file, but I remembered that there are a few commands that I could use, !devstack and !devobj on the address I've marked (not sure what kind of address it is)
This is the result when using !devstack on the same address showing that the Realtek driver is causing issues, though again I have not really a proper idea as to why.
I could go a bit deeper in the dump, but it doesn't provide much more useful data.
Code: 
6: kd> !devstack ffffe001ffa50a20
  !DevObj           !DrvObj            !DevExt           ObjectName
> ffffe001ffa50a20  \Driver\ksthunk    ffffe001ffa50b70  InfoMask field not found for _OBJECT_HEADER at ffffe001ffa509f0

  ffffe001ffa50c20 Unable to load image \SystemRoot\system32\DRIVERS\rtsuvc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rtsuvc.sys
*** ERROR: Module load completed but symbols could not be loaded for rtsuvc.sys
 \Driver\rtsuvc     ffffe001ffa50d90  InfoMask field not found for _OBJECT_HEADER at ffffe001ffa50bf0

  ffffe001ffa35c30  \Driver\ACPI       ffffe001faa94010  InfoMask field not found for _OBJECT_HEADER at ffffe001ffa35c00

  ffffe001ffa30060  \Driver\usbccgp    ffffe001ffa301b0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffe001ffa307d0 :
  DeviceInst is "USB\VID_5986&PID_055E&MI_00\6&330b8916&0&0000"
  ServiceName is "rtsuvc"
 
axe0 said:
How did you figured out it's "Realtek webcam driver"? Because I read on microsoft forums that it's pointing on 'usbccgps.sys' but doesn't mean it's his fault.
Click to expand...
To answer this question better:
My experience is that when the Windows USB drivers are being flagged it often is a USB network adapter that is the root cause, unfortunately I couldn't see if such a device is used as the msinfo32 file is missing. I was planning on posting instructions for you to provide us the file, but I remembered that there are a few commands that I could use, !devstack and !devobj on the address I've marked (not sure what kind of address it is)
This is the result when using !devstack on the same address showing that the Realtek driver is causing issues, though again I have not really a proper idea as to why.
I could go a bit deeper in the dump, but it doesn't provide much more useful data.
Code: 
6: kd> !devstack ffffe001ffa50a20
  !DevObj           !DrvObj            !DevExt           ObjectName
> ffffe001ffa50a20  \Driver\ksthunk    ffffe001ffa50b70  InfoMask field not found for _OBJECT_HEADER at ffffe001ffa509f0

  ffffe001ffa50c20 Unable to load image \SystemRoot\system32\DRIVERS\rtsuvc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rtsuvc.sys
*** ERROR: Module load completed but symbols could not be loaded for rtsuvc.sys
 \Driver\rtsuvc     ffffe001ffa50d90  InfoMask field not found for _OBJECT_HEADER at ffffe001ffa50bf0

  ffffe001ffa35c30  \Driver\ACPI       ffffe001faa94010  InfoMask field not found for _OBJECT_HEADER at ffffe001ffa35c00

  ffffe001ffa30060  \Driver\usbccgp    ffffe001ffa301b0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffe001ffa307d0 :
  DeviceInst is "USB\VID_5986&PID_055E&MI_00\6&330b8916&0&0000"
  ServiceName is "rtsuvc"
Click to expand...

Hi,

thanks so much. In young age I had BSOD and I was trying to handle it and so I joined here with hope to resolve it and learn about it.

I trust the program but if you tell me is wrong I believe you. I think that program is good because it's download from lenovo website, probably from DB...

How to do: "revert the changes that this program has made using a restore point " ?
Also, if I am going to restore would I need to download lenovo easy camera driver again?

PS: I am adding "MSInfo32.nfo" file, it was all time I just didn't add all because I didn't think it was necessary.(i.e. IPconfigAll, tracert, etc..)
(It doesn't let me to upload so I am adding zippyshare: http://www29.zippyshare.com/d/flFZzhbB/9249673/MSInfo32.7z)
Best regards,

GooonE
 
In control panel, click 'Recovery', click 'Open System Restore', click 'Next', choose a restore point prior the use of slimdrivers if possible and click 'next', click 'Finish' to start the restore point.
When you choose the restore point you can view what programs are removed and/or installed again.

Most likely you will have to reinstall the driver again yes.
 
Choose 'show more restore points' in System Restore, choose the oldest one created by slimdrivers.
 
I think that program is good because it's download from lenovo website, probably from DB
Click to expand...
It doesn't get the drivers from Lenovo, you can compare the available drivers at Lenovo with the drivers in slimdrivers.
For example the Intel Management Engine Interface driver, a chipset driver, I can't compare the version but I can compare the dates:
From slimdrivers per your screenshot: 10/07/2015
From Lenovo: 5/4/2014

Slimdrivers says the drivers are from their cloud, but where the drivers come from before they put it in their cloud isn't explained.
When I go through some 'reviews' I don't see any of them explaining what the root source is, only that it comes from the cloud and that it uses a few techniques for some things. That is the main problem with such software, you don't know where it comes from or what happens with the stuff before it comes in the cloud.
 
axe0 said:
I think that program is good because it's download from lenovo website, probably from DB
Click to expand...
It doesn't get the drivers from Lenovo, you can compare the available drivers at Lenovo with the drivers in slimdrivers.
For example the Intel Management Engine Interface driver, a chipset driver, I can't compare the version but I can compare the dates:
From slimdrivers per your screenshot: 10/07/2015
From Lenovo: 5/4/2014

Slimdrivers says the drivers are from their cloud, but where the drivers come from before they put it in their cloud isn't explained.
When I go through some 'reviews' I don't see any of them explaining what the root source is, only that it comes from the cloud and that it uses a few techniques for some things. That is the main problem with such software, you don't know where it comes from or what happens with the stuff before it comes in the cloud.
Click to expand...

Hi,

I did a system restore and then it didn't work so I select earlier, I mean I clicked 1. Show more restore points 2. added only one point 3. clicked on it 4. ??? 5. restore 6. reboot 7. error need to do chkdsk /r

I didn't do that so I select earlier.

Then it restored and then I also restored with SlimDrivers and I am not sure if it restored the original drivers.

Can you help me to check before installing Lenovo drivers?

Thanks,

Gooone
 
Hi,
I added verifier and now I received another BSOD which is different from the one below,

Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe00046cd4028, be000000, 800400}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00046cd4028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Best regards,

GooonE
 

Attachments

The drivers I updated so far:Camera Driver (Bison, AVC)Intel Video DriverIntel WLAN DriverRealtek Audio DriverTouchpad Driver(Synaptics, Elan, Alps)Best regards,GooonE
 
We may be dealing with unknown hardware problems, although an internal timer error often leads to a faulty CPU, as verifier is enabled but didn't flag anything.
I would suggest that you follow Hardware Diagnostics to test the CPU, GPU, hard drive, RAM & scan for malware.
Code: 
2: kd> !errrec ffffe000`46cd4028
===============================================================================
Common Platform Error Record @ ffffe00046cd4028
-------------------------------------------------------------------------------
Record Id     : 01d1a86289bf0ae4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/7/2016 14:32:08 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe00046cd40a8
Section       @ ffffe00046cd4180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe00046cd40f0
Section       @ ffffe00046cd4240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : c3 06 03 00 00 08 10 02 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffe00046cd4240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe00046cd4138
Section       @ ffffe00046cd42c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 2 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0xfffff800aecfbde8
  Misc.       : 0xfffff800aecfbde8
 
Hi,

can someone examine my latest BSOD and answer my question if I did System Recovery fine?
Maybe the BSOD I received is because of the system recovery and SlimDrivers Recovery?

I did memtest a long time ago and it was fine, about the hard drive I see the health status is good and GPU I don't think it's on because I see 0C degree from SpeedFan software.

Best regards,

GooonE
 
I already have examined your latest BSOD, see my previous post.
We may be dealing with unknown hardware problems, although an internal timer error often leads to a faulty CPU, as verifier is enabled but didn't flag anything.
Click to expand...
There is nothing much more we can get from a minidump. A kernel dump probably would only show how the crash occured, but not really the why part, at least that is what I remember from the guide x BlueRobot wrote (not sure if I remember it correctly).

Run all the tests suggested, that you've run them a long time ago can't be used as a reason to not run the same test again because since the time you ran it and now there have been many changes occured which may include the component being faulty.
It is the same as using a hard drive that is several years old & may have several problems, but claiming it is fine just because you've run a test on it a year ago.
 
Your Nvidia drivers seems to be old, and I can see on the manufacturer website a new version: Nvidia Video Driver for Windows 8.1 (64-bit) - Lenovo Y50-70, Y50-70 Touch (if I got the correct link...).
The acronis driver too.
I'm not sure you can run Windows ADK for Windows 10 on a 8.1 machine, even if it seems it installed well.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top