[SOLVED] BSOD on Win 8.1
- Thread starter mlee
- Start date
There were no collected dump files.
There was reported corruption of the drive file system.
Please perform the following steps:
1) Search for C:\windows\memory.dmp
If the file size is less than or equal to 2GB then save to the downloads folder > zip > post a share link into this thread using one drive, drop box, or google drive
2) Turn off Windows fast startup
How to:Disable or Enable Windows 10 Fast Startup (and Why)
3) Open administrative command prompt and type or copy and paste:
chkdsk /r /v C:
Plan to run overnight.
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
4) For any BSOD post a new Sysnative log collector share link into the newest post.
There was reported corruption of the drive file system.
Please perform the following steps:
1) Search for C:\windows\memory.dmp
If the file size is less than or equal to 2GB then save to the downloads folder > zip > post a share link into this thread using one drive, drop box, or google drive
2) Turn off Windows fast startup
How to:Disable or Enable Windows 10 Fast Startup (and Why)
3) Open administrative command prompt and type or copy and paste:
chkdsk /r /v C:
Plan to run overnight.
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
4) For any BSOD post a new Sysnative log collector share link into the newest post.
Last edited by a moderator:
The edit is malfunctioning.
BIOS Version/Date American Megatrends Inc. 0702, 10/23/2014
In addition to the earlier steps in the prior post upgrade the BIOS: 0702 > 0802
K30AD - Support
BIOS Version/Date American Megatrends Inc. 0702, 10/23/2014
In addition to the earlier steps in the prior post upgrade the BIOS: 0702 > 0802
K30AD - Support
- May 7, 2013
- 10,400
The post edit feature is not malfunctioning. There is time restriction as to when a post is editable for a non-moderator.
1. cannot find memory.dmp
2. cannot turn off fast startup (check box is grayed out)
3. Do you still want me to run chkdsk?
4. I don't understand what this means.
Thanks
When possible:
a) Upgrade the BIOS
b) Run chkdsk /r /v overnight
To find chkdsk results run: https://www.dropbox.com/s/xfsr4yyg5yun3k1/ListChkdskResult.exe?dl=1
c) During the thread troubleshooting turn off hibernation using administrative command prompt: powercfg -h off
(Turning off hibernation also turns off Windows fast startup)
d) type: win + r > sysdm.cpl > click the advanced tab > under startup and recovery click settings > post an image or share link of the startup and recovery window into this thread
e) type: win + r > sysdm.cpl > click the advanced tab > under performance click settings > on the performance options window click the advanced tab > under virtual memory click change > post an image or share link of the virtual memory window into this thread
f) In the opening post you attached the Sysnative log collector results. For any new crash or BSOD during this thread run the Sysnative log collector and post new results into the newest post
g) During the troubleshooting make sure that no cleaning software is used: for example Windows disk cleanup, Ccleaner, Wise cleaner, Glary Utilities, etc.
a) Upgrade the BIOS
b) Run chkdsk /r /v overnight
To find chkdsk results run: https://www.dropbox.com/s/xfsr4yyg5yun3k1/ListChkdskResult.exe?dl=1
c) During the thread troubleshooting turn off hibernation using administrative command prompt: powercfg -h off
(Turning off hibernation also turns off Windows fast startup)
d) type: win + r > sysdm.cpl > click the advanced tab > under startup and recovery click settings > post an image or share link of the startup and recovery window into this thread
e) type: win + r > sysdm.cpl > click the advanced tab > under performance click settings > on the performance options window click the advanced tab > under virtual memory click change > post an image or share link of the virtual memory window into this thread
f) In the opening post you attached the Sysnative log collector results. For any new crash or BSOD during this thread run the Sysnative log collector and post new results into the newest post
g) During the troubleshooting make sure that no cleaning software is used: for example Windows disk cleanup, Ccleaner, Wise cleaner, Glary Utilities, etc.
When available please update the progress with each step in post #6.
Today is 3/24.
The logs reported multiple BSOD between 3/8 and 3/21.
There were three BSOD on 3/21.
The Sysnative log collector has not been able to find or collect any dump files.
Search for:
C:\Windows\Minidump
C:\Windows\MEMORY.DMP
Please read this link on Windows Driver Verifier (WDV). (Do not use the tool until you report the results of each step in post #6).
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista
Today is 3/24.
The logs reported multiple BSOD between 3/8 and 3/21.
There were three BSOD on 3/21.
The Sysnative log collector has not been able to find or collect any dump files.
Search for:
C:\Windows\Minidump
C:\Windows\MEMORY.DMP
Please read this link on Windows Driver Verifier (WDV). (Do not use the tool until you report the results of each step in post #6).
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista
Minidump is an empty folder.
Memory.dmp does not exist.
The symptoms have changed since I first opened this thread.
Should I close this one and start a new one?
Or, should I describe the current symptoms here?
Briefly:
1. sfc /scannow found errors and repaired them.
2. shutdown/restart
3. sfc /scannow found no errors
4. "DISM /Online /Cleanup-Image /RestoreHealth" found errors and repaired them
5. shutdown/restart
6. "DISM /Online /Cleanup-Image /RestoreHealth" found no errors
Thanks.
Almost all of the BSOD bugchecks were 133.
There were no mini or memory dumps collected.
When available update the progress with the prior steps so that the thread has these results:
a) BIOS > upgrade > done or not done
b) Chkdsk /r /v > done or not done > report of the results
c) Hibernation turned off > done or not done
d) images or share links of the startup and recovery system failure window
e) Uncheck the startup and recovery system failure box to automatically restart
f) images or share links of the virtual memory / page file window
g) If there are new problems with scannow or restorehealth then post images of the commands with results into this thread
Once you've completed all of the above steps the next step is WDV to find misbehaving drivers.
Please complete the "housekeeping" steps before starting WDV.
Code:
03/08/2022 03:01 AM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_159226fc
03/08/2022 11:59 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_12c6131b
03/10/2022 11:24 PM <DIR> Kernel_133_d87a8acfe4d30fbc16fc50bf74427f9c49bc_00000000_cab_12e5e327
03/11/2022 12:42 AM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_181bb541
03/12/2022 03:23 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_189f88a9
03/12/2022 11:35 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_0c179d0c
03/12/2022 11:39 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_18c8ea6f
03/14/2022 04:01 AM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_1690e9e3
03/14/2022 02:03 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_14c98dc4
03/15/2022 12:13 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_07b08feb
03/15/2022 12:29 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_144cce8b
03/15/2022 12:37 PM <DIR> Kernel_133_d87a8acfe4d30fbc16fc50bf74427f9c49bc_00000000_cab_12e4ae7f
03/15/2022 12:52 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_15adeb45
03/15/2022 01:15 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_0c67670d
03/15/2022 01:34 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_045229a3
03/15/2022 01:40 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_1614b100
03/15/2022 10:09 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_022cb59c
03/16/2022 03:10 AM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_12508443
03/16/2022 07:47 PM <DIR> Kernel_c5_5cf43c832a6ed45b8e7f8cffef1b78b6d203d31_00000000_cab_139789db
03/19/2022 03:55 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_1330b0c2
03/21/2022 01:41 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_048b3866
03/21/2022 01:54 PM <DIR> Kernel_133_b4d5973ba8217068f19c9ce310ed1231fa1f637e_00000000_cab_064659be
03/21/2022 02:07 PM <DIR> ..
03/21/2022 02:07 PM <DIR> .
03/21/2022 02:07 PM <DIR> Kernel_133_d87a8acfe4d30fbc16fc50bf74427f9c49bc_00000000_cab_038ba3d2- May 7, 2013
- 10,400
If the bugchecks are predominantly Stop 0x133, then you need to check the dump file settings and ensure that dump files are being produced. This is most likely going to be a driver issue. There is no need to perform your "housekeeping" steps. You're just going to confuse the OP and waste their time.
@Melp Please provide a screenshot of your dump file settings in your next post. Please see here for instructions on how to do so.
a. According to ASUS update manager, BIOS is up to date
According to ASUS update manager, drivers are up to date
b. Chkdsk with your parameters, ran on System drive and booted into Windows normally. Do not know where log file is located.
c. Hibernation is disabled
d. see 2 images below
I do not know how to complete e, and f.
Do you want me to run a specific sfc or DIMM command?
Thanks
Attachments
see attached
dump file settingsIn the startup and recovery window please uncheck automatically restart.
Also display the virtual memory / page file window as per the instructions in the earlier post.
Start Windows Driver Verifier (WDV) when you understand the methods to turn off the tool in safe mode using: verifier /reset and / or verifier /bootmode resetonbootfail
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista
Make sure that you create a new restore point before starting the tool.
For any BSOD > run the Sysnative log collector > post a link into the newest post
If there is no immediate BSOD then run: verifier /querysettings
Post an image or share link into the newest post.
Also display the virtual memory / page file window as per the instructions in the earlier post.
Start Windows Driver Verifier (WDV) when you understand the methods to turn off the tool in safe mode using: verifier /reset and / or verifier /bootmode resetonbootfail
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista
Make sure that you create a new restore point before starting the tool.
For any BSOD > run the Sysnative log collector > post a link into the newest post
If there is no immediate BSOD then run: verifier /querysettings
Post an image or share link into the newest post.
I attached results of chkdsk
- May 7, 2013
- 10,400
mlee has reported that there has been no BSOD issues for the past week, I'm going to mark this thread as solved for now.
[SOLVED] - sfcfix.exe
[SOLVED] - sfcfix.exe
Has Sysnative Forums helped you? Please consider donating to help us support the site!