Two BSODs within the past week

Hiss13 · 01 Nov 2020

I had been having BSODs over the past week on my laptop while watching youtube videos on Chrome but with different stopcodes

My laptop is a GL62M-7RD.
OS:
Windows 10 Home Version 1903 Build 18362.1016
CPU: Intel i7-7700HQ @2.80 GHz
Memory: 16GB (16GB x1) DDR4 2400MHz
Graphics Card(s): NVIDIA GTX 1050 2GB GDDR5

I have interviews coming up so I really would like to have this issue fixed before then.

I have attached the V2 collector's Zip file to the post.

MrPepka · 02 Nov 2020

Update BIOS - Laptops - The best gaming laptop provider | MSI Global
Update Windows 10 - https://support.microsoft.com/pl-pl/...date-assistant
Update Intel Wi-Fi driver - Pliki do pobrania dla Intel(R) Dual Band Wireless-AC 3168

Hiss13 · 02 Nov 2020

MrPepka said:

Update BIOS - Laptops - The best gaming laptop provider | MSI Global
Update Windows 10 - https://support.microsoft.com/pl-pl/...date-assistant
Update Intel Wi-Fi driver - Pliki do pobrania dla Intel(R) Dual Band Wireless-AC 3168

Is there a specific issue causing these last two BSoDs or is this more of a scorched earth method to try and fix this?

zbook · 02 Nov 2020

Run: Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

Reinstall chipset drivers:

Download Intel(R) Driver & Support Assistant

Code:

iastora	iaStorA	c:\windows\system32\drivers\iastora.sys	Kernel Driver	Yes	Boot	Running	OK	Normal	No	Yes

Code:

Name	Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller
Manufacturer	Intel Corporation
Status	OK
PNP Device ID	PCI\VEN_8086&DEV_A103&SUBSYS_11C81462&REV_31\3&11583659&1&B8
Memory Address	0xDF328000-0xDF329FFF
Memory Address	0xDF32C000-0xDF32C0FF
I/O Port	0x0000F090-0x0000F097
I/O Port	0x0000F080-0x0000F083
I/O Port	0x0000F060-0x0000F07F
Memory Address	0xDF32B000-0xDF32B7FF
IRQ Channel	IRQ 4294967291
Driver	C:\WINDOWS\SYSTEM32\DRIVERS\IASTORA.SYS (15.2.0.1020, 776.99 KB (795,640 bytes), 1/25/2016 4:28 AM)

Code:

Event[1901]:
  Log Name: System
  Source: Ntfs
  Date: 2020-10-15T18:49:36.577
  Event ID: 55
  Task: N/A
  Level: エラー
  Opcode: 情報
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MSI
  Description: 
ボリューム Windows のファイル システム構造で破損が検出されました。

A corruption was found in a file system index structure.  The file reference number is 0x5000000000005.  The name of the file is "\".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

Code:

iaStorA.sys  Tue Sep 13 07:45:46 2016 (57D8111A)

Hiss13 · 02 Nov 2020

Are both of those something I'd have to run overnight or is it just the chkdsk command?

zbook · 02 Nov 2020

Tuneup typically takes < 30 minutes.

Run chkdsk overnight.

If there are significant underlying problems they may run for longer periods.

Hiss13 · 03 Nov 2020

This is the output from the tuneup.bat
I'll be running the chkdsk overnight.
I'll be honest, I do not know where all the Japanese text is coming from. I do have a locale emulator and a Japanese keyboard installed, but it doesn't make sense to me

Code:

###########################################################
# The following commands will be run in sequence.         #
# The first 5 will take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="MSI" get AutomaticManagedPagefile
wmic Computersystem where name="MSI" set AutomaticManagedPagefile=True
wmic Computersystem where name="MSI" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.900

Image Version: 10.0.18362.1016

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.900

Image Version: 10.0.18362.1016

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows.

Stage 1: Examining basic file system structure ...
  2098944 file records processed.
File verification completed.
  17076 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  134330 reparse records processed.
  2311652 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  134330 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  106355 data files processed.
CHKDSK is verifying Usn Journal...
  34649208 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 624077823 KB total disk space.
 549153604 KB in 713729 files.
    397556 KB in 106356 indexes.
         0 KB in bad sectors.
   2229687 KB in use by the system.
     65536 KB occupied by the log file.
  72296976 KB available on disk.

      4096 bytes in each allocation unit.
 156019455 total allocation units on disk.
  18074244 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\MSI\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\MSI\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>wmic pagefile list /format:list


AllocatedBaseSize=5888
CurrentUsage=420
Description=C:\pagefile.sys
InstallDate=20200517005541.059658-240
Name=C:\pagefile.sys
PeakUsage=423
Status=
TempPageFile=FALSE




C:\WINDOWS\system32>wmic Computersystem where name="MSI" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\WINDOWS\system32>wmic Computersystem where name="MSI" set AutomaticManagedPagefile=True
Updating property(s) of '\\MSI\ROOT\CIMV2:Win32_ComputerSystem.Name="MSI"'
Property(s) update successful.

C:\WINDOWS\system32>wmic Computersystem where name="MSI" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}
Environment variable 笳・Echo Echo not defined
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'#' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the path specified.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・' is not recognized as an internal or external command,
operable program or batch file.
'笳・.' is not recognized as an internal or external command,
operable program or batch file.

- - - Updated - - -

Also can't seem to find the edit button for my last post so I'll add the chkdsk stuff to this post. Sorry if I'm breaking the rules.

Also, I followed the instructions, but I wasn't sure what to copy so I copied the stuff from the general box on all wininit and chkdsk events listed.

zbook · 03 Nov 2020

C:

Code:

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

The computer can be monitored for stability / instability.

If there are no BSOD for 3 - 5 days that will complete the troubleshooting.

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using

Hiss13 · 03 Nov 2020

Alright. Thanks. Will report back in 5 days or if any BSoDs happen since then.

That being said, is there any reason for that bit under the RAM part of the tuneup output?

zbook · 03 Nov 2020

I've reported it to the person that created the script.
They appear to be puzzled too.

1) Open administrative command prompt (ACP) and type or copy and paste:

Lpksetup /u

View the pop up and use the snipping tool to post an image into the thread

2) Open administrative command prompt (ACP) and type or copy and paste:

dism /online /get-intl

When this has completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

3) Open administrative Powershell and copy and paste:

Get-WinUserLanguageList

When this has completed > right click on the top bar or title bar of the administrative PS box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread