Getting BSOD Randomly

E

edurgesh

Journeyman
Hello friends,

I have the following laptop with me which I got two years ago from US, now out of warranty. This is my regular work horse for everyday work, which has be very faithful with good performance.
*www.newegg.com/asus-vivobook-s-s510ua-ds71-mainstream/p/N82E16834234873

Recently, it started randomly crashing while working for a long time and BSOD appears, then laptop restarts automatically. After restart, it goes to BIOS and could not find any boot device to load the Windows.

First time it happened last week, then when it booted I backed up everything on secondary disk (1TB HDD). Yesterday in the evening it crashed multiple times, then I kept it switched off for a couple of hours. After that it has been working fine; I'm typing currently on that only!

Please suggest what may be the issue and any solution for this. I'm not sure if this is because of Windows or primary SSD is failing?

Thanks a lot!
 
SaiyanGoku

SaiyanGoku

kamehameha!!
Check smart info using CrystalDiskInfo and update all drivers. Also check if there is a BIOS update available on the manufacturer's support page.
 
OP
E

edurgesh

Journeyman
Hello @SaiyanGoku ,
Please see the screen shot from CrystalDiskInfo; this looks good to me, not sure if something is abnormal here.

1586939220797.png


I checked the BIOS on Asus website, and looks like the laptop has the latest BIOS (I've updated couple of times in the past).
Also there are few drivers' new version available; I'll update those.

Thanks!
 
W

whitestar_999

Super Moderator
Staff member
ssd looks fine, which windows version are you using(if using win 10 then run winver command in start menu search box to see exact version number). Run memtest free version:
*www.memtest86.com/compare.html

Download HWiNFO - Free System Information, Monitoring and Diagnostics & check you processor & mobo temperatures.
 
Zangetsu

Zangetsu

I am the master of my Fate.
Check the EventViewer for any error messages during BSOD.
The windows dump files will help to pinpoint the issue, but need technical insights to read & analyze the dump.
 
OP
E

edurgesh

Journeyman
Hello @whitestar_999 and @Zangetsu !! Thanks for the tips; I did all those things and here is the outcome:

1. This is Windows 10 Home, Version 1909 (OS Build 18363.720).
2. Updated all the latest drivers (BIOS was already the latest).
3. Ran MemTest86; all successful, 0 errors (took almost 3 hours to complete; temp varied from 64C-68C).
4. Temperatures as per HWInfo looks normal; please check below

1587021622347.png


5. Event Viewer had few errors during that time; there are multiple of these. Please see below

(A) The previous system shutdown at 6:25:04 PM on ‎4/‎14/‎2020 was unexpected.
(B) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
(C) The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xffffba88edec2080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 15194e46-14be-4c00-89d7-85c4fd452482.
(D) The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Since yesterday, it has been working fine. Hope this continues! :)

Thanks a lot friends for your help and valuable tips!!
 
W

whitestar_999

Super Moderator
Staff member
See this thread, run the driver verifier tool to see if any driver is causing this issue:
*answers.microsoft.com/en-us/window...bugcheck/513afb92-d304-46dc-8ab6-dfd05a65c216
 
OP
E

edurgesh

Journeyman
Hello friends,

Yesterday it crashed again, so today I performed the driver verification. But after reboot, the windows was consistently crashing while loading and it never booted successfully. Tried three times, then finally booted into safe mode and disabled the verifier.

Analyzed the mini dump files generated yesterday and today both using WinDgb.exe, but not able to figure out what's wrong. Here I'm putting a small portion which I felt important; please see if something is wrong?

Yesterday's Dump:
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffff978eadaedc08, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00002000378b8860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8006db7dfa0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

*** WARNING: Unable to verify timestamp for win32k.sys
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
FAILURE_BUCKET_ID: 0x7a_c000000e_UsbHub3!McGenControlCallbackV2
BUCKET_ID: 0x7a_c000000e_UsbHub3!McGenControlCallbackV2
PRIMARY_PROBLEM_CLASS: 0x7a_c000000e_UsbHub3!McGenControlCallbackV2
FAILURE_ID_HASH_STRING: km:0x7a_c000000e_usbhub3!mcgencontrolcallbackv2
FAILURE_ID_HASH: {fde512e6-6c60-b9e2-ae2d-e06b76b39a6d}

Today's Dump:
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80480127b28, address which referenced memory

ffff880712f7e090: Unable to read TableSize for resource

READ_ADDRESS: fffff8048057b3b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
0000000000000002

ffff880712f7e090: Unable to read TableSize for resource
1 total locks

FAULT_INSTR_CODE: 8944d033
FAILURE_BUCKET_ID: AV_VRF_CI!SymCryptSha256AppendBlocks_ul1
BUCKET_ID: AV_VRF_CI!SymCryptSha256AppendBlocks_ul1
PRIMARY_PROBLEM_CLASS: AV_VRF_CI!SymCryptSha256AppendBlocks_ul1
FAILURE_ID_HASH_STRING: km:av_vrf_ci!symcryptsha256appendblocks_ul1
FAILURE_ID_HASH: {cec7eb1c-2599-30f1-3c52-7992c5d50f12}

Note: Yesterday's log says UsbHub few times; on that line, few days back I was trying to install an old USB webcam driver on laptop and it failed to install. Maybe that's causing the crash?

Thanks a lot!
 
W

whitestar_999

Super Moderator
Staff member
edurgesh said:
OK sure, I'll try that. Do I need to reinstall all the drivers again after Windows reset?
Thanks!
Click to expand...
If your win 10 has any preinstalled drivers from the beginning(like in case of laptops pre-installed win 10 & using that only) then those will remain but all other drivers will need to be reinstalled.
 
OP
E

edurgesh

Journeyman
whitestar_999 said:
If your win 10 has any preinstalled drivers from the beginning(like in case of laptops pre-installed win 10 & using that only) then those will remain but all other drivers will need to be reinstalled.
Click to expand...
OK great! It's a laptop and came with Windows 10 Home preinstalled, so I think it will retain all the drivers; only apps need to install after reset.
Thanks!
 
W

whitestar_999

Super Moderator
Staff member
edurgesh said:
OK great! It's a laptop and came with Windows 10 Home preinstalled, so I think it will retain all the drivers; only apps need to install after reset.
Thanks!
Click to expand...
Still no harm in being extra cautious, at least download wifi drivers from your laptop manufacturer's site.
 
You must log in or register to reply here.
Top Bottom