BSOD after laptop sitting idle / Not sure how long of idle time

[cowboyzx6]

BSOD happens randomly, not all the time.
Dump files attached

 

[ICIT2LOL]

Hello and welcome cowboy mate the first dump I opened has shown up a very common fault and it can be due to a multitude of things.

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002e05000 nt
DEBUG_FLR_IMAGE_TIMESTAMP:  55a6901f
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS: fffffa801ca4ca60
DEVICE_OBJECT: fffffa800cdf8a10
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  [COLOR=red]WIN7_DRIVER_FAULT[/COLOR]
BUGCHECK_STR:  0x9F
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff80002ee8740 to fffff80002e785c0
STACK_TEXT:  
fffff800`00b9a388 fffff800`02ee8740 : 00000000`0000009f 00000000`00000003 fffffa80`0cdf8a10 fffff800`00b9a3d8 : nt+0x735c0
fffff800`00b9a390 00000000`0000009f : 00000000`00000003 fffffa80`0cdf8a10 fffff800`00b9a3d8 fffffa80`1ca4ca60 : nt+0xe3740
fffff800`00b9a398 00000000`00000003 : fffffa80`0cdf8a10 fffff800`00b9a3d8 fffffa80`1ca4ca60 00000000`c00000bb : 0x9f
fffff800`00b9a3a0 fffffa80`0cdf8a10 : fffff800`00b9a3d8 fffffa80`1ca4ca60 00000000`c00000bb 00000000`00000000 : 0x3
fffff800`00b9a3a8 fffff800`00b9a3d8 : fffffa80`1ca4ca60 00000000`c00000bb 00000000`00000000 fffff800`0302ebe0 : 0xfffffa80`0cdf8a10
fffff800`00b9a3b0 fffffa80`1ca4ca60 : 00000000`c00000bb 00000000`00000000 fffff800`0302ebe0 fffff800`00000002 : 0xfffff800`00b9a3d8
fffff800`00b9a3b8 00000000`c00000bb : 00000000`00000000 fffff800`0302ebe0 fffff800`00000002 00000000`00018000 : 0xfffffa80`1ca4ca60
fffff800`00b9a3c0 00000000`00000000 : fffff800`0302ebe0 fffff800`00000002 00000000`00018000 fffff800`0302ebd0 : 0xc00000bb

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt+735c0
fffff800`02e785c0 48894c2408      mov     qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt+735c0
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  [COLOR=red]ntoskrnl.exe[/COLOR]
BUCKET_ID:  WRONG_SYMBOLS
FAILURE_BUCKET_ID:  [COLOR=red]WRONG_SYMBOLS[/COLOR]
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:wrong_symbols
FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner

Can you tell us please if you have installed any new hardware or software recently??

Let us know the temps in the machine use this for that https://www.piriform.com/speccy/download

and can you run these please if you have not done so already

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2 >in safe mode if need be

then these

https://www.malwarebytes.org/mwb-download/index.html

http://www.superantispyware.com/

http://www.bleepingcomputer.com/download/adwcleaner/

ADW download from bleepingcomputer delete any rubbish found with the malware scans

NB If anyone is runningKaspersky security it may rant about ADW - just ignore it or disable it for awhile

 

[cowboyzx6]

I have not changed the hardware and I believe SW has stayed the same.

I am attaching the output from speccy: "speccy lapz.txt"

Malwarebytes did reveal 2 PUP. I have removed them. "malware.txt"

Running "sfc /scannow" and got "Windows Resource Protection found corrupt files but was unable to fix some of them".
I then ran the System Update Readiness Tool and re-ran sfc. Same results. "sfcdetails.txt"

Also ran chkdsk on my primary and all good.

I do see some issues in the sfcdetails.txt but not sure how to fix them or even if they are the root of my problem?

 

[ICIT2LOL]

The temps are ok mate and I am wondering if the SAS and ADW came up with anything - most unusual for SAS not to show up PUP's especially as MBAM picked some up.

Now the other issue with the sfc I am not real sure it needs someone with better knowledge of that coding to see what is wrong I might ask for some others to take a look.

 

[cowboyzx6]

Ok. thanks for looking at it. Since our last conversation, I went to the DELL website and updated a couple of drivers.

When I run SFC now, it alternates between telling me "Windows Resource Protection found corrupt files and successfully repaired them" and "Windows Resource Protection found corrupt files but was unable to fix some of them."

I have attached the log file for that. It all seems to related to "usbhub.sys.mui"

Having said that, I have not had a BSOD for at least a week. Maybe the Dell driver update has fixed some issues?

I will consider it closed for now. Thanks for the help.

 

[ICIT2LOL]

Right then if the machine is running ok then maybe the drivers have fixed the issue. As I aid earlier the ntoskrnl.exe is a dump that comes up a lot and it means digging around to find the cause.

Am not that good with the sfc readout to be honest and it the problem persist post back and perhaps someone else can interpret that properly as I would only be guessing unless it is very obvious.