New
#1
Blue screen error after doing a restart and update
Last edited by Steviebabs2685; 18 Apr 2018 at 23:46. Reason: Adding DM log
Last edited by Steviebabs2685; 18 Apr 2018 at 23:46. Reason: Adding DM log
See posting instructions:
BSOD - Posting Instructions - Windows 10 Forums
On the bottom of the web page run the BETA log collector:
(extract > open)
See post #5 in this link for text and images to run the beta log collector:
beta log collector problems: DM Log tool problem Solved - Windows 10 Forums
If you are having problems with a normal boot then boot with safe mode with networking or safe mode or safe mode with command prompt.
Boot into Safe Mode on Windows 10 Windows 10 Tutorials
For a hardware boot into the Windows advanced troubleshooting menu:
a) power on the computer and as soon as you see the Microsoft Windows icon power off.
b) repeat power on and power off when you see the Windows icon.
c) power on and allow the computer time to open to the Windows advanced troubleshooting menu
d) click troubleshoot
e) click startup options (not startup repair) > click restart > click safe mode with networking
f) run the log collector (beta) > post a zip into the thread
Had you updated the 2018 Dell BIOS and updated drivers?
Had you ran the Dell diagnostics?
Support for Inspiron 24 5459 AIO | Drivers & downloads | Dell US
Support for Inspiron 24 5459 AIO | Diagnostics | Dell US
Last edited by zbook; 18 Apr 2018 at 03:13.
Post #1 was edited with an attached file that was blank.
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) chkdsk /scan
6) When these have 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
7) Run each the DM log collector and the BETA log collector after the above steps and post zips into the thread.
Microsoft Windows [Version 10.0.16299.309](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning 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 /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.309[==========================100.0%==========================]
No component store corruption detected.The operation completed successfully.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.309[==========================100.0%==========================]
The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is OS.Stage 1: Examining basic file system structure ... 388864 file records processed.File verification completed. 11884 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 19832 reparse records processed. 494570 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 19832 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 52854 data files processed.CHKDSK is verifying Usn Journal... 35281376 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 962641919 KB total disk space. 254995700 KB in 275763 files. 172232 KB in 52855 indexes. 0 KB in bad sectors. 567123 KB in use by the system. 65536 KB occupied by the log file. 706906864 KB available on disk. 4096 bytes in each allocation unit. 240660479 total allocation units on disk. 176726716 allocation units available on disk.
Restarted and when trying to login, get BSOD again.
Hi Steviebabs2685 ,
Welcome to Ten Forums BSOD forum.
For all tests / steps please post images into the thread.
For any problems posting images please use one drive or drop box share links.
Take Screenshot in Windows 10 Windows 10 Tutorials
Share OneDrive files and folders - Office Support
1) Run the BETA log collector and post a zip into the thread:
See text and images in this link: post #5
DM Log tool problem Solved - Windows 10 Forums
2) The RAM modules are mismatched.
When was the second module added?
3) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 12 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 Tutorials
4) Run HD Tune:
http://www.hdtune.com/
Post images into the thread for results on each of these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan
5) Backup all files to another drive or to the cloud
6) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
Backup the image to another drive or to the cloud
7) Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > zip > post a one drive or drop box share link into the thread
8) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
9) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread
HTML Code:4/18/2018 6:30 AM Windows Error Reporting Fault bucket 0xF5_FLTMGR!FltMgrOpenReparseEcpCleanup, type 0 Event Name: BlueScreen Response: Not available Cab Id: cb5ebdf8-cb14-401d-b242-500e85fd8e3f Problem signature: P1: f5 P2: 6f P3: ffffcd85fc1bdb98 P4: ffffcd85f83cd9b0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041818-52281-01.dmp \\?\C:\WINDOWS\TEMP\WER-661390-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBE5E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBE5F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBE8F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_f5_de53a358b9fd2b9e48137ac9fc7ced22ccd378e_00000000_cab_2267eaaa Analysis symbol: Rechecking for solution: 0 Report Id: cc3d8781-3778-4ec0-9c62-f763ce9bbf1f Report Status: 268435456 Hashed bucket:HTML Code:4/18/2018 6:11 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: f5 P2: 6f P3: ffffcd85fc1bdb98 P4: ffffcd85f83cd9b0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\041818-52281-01.dmp \\?\C:\WINDOWS\TEMP\WER-661390-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBE5E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBE5F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBE8F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_f5_de53a358b9fd2b9e48137ac9fc7ced22ccd378e_00000000_cab_03f2be8c Analysis symbol: Rechecking for solution: 0 Report Id: cc3d8781-3778-4ec0-9c62-f763ce9bbf1f Report Status: 4 Hashed bucket:HTML Code:4/18/2018 6:30 AM Windows Error Reporting Fault bucket LKD_0x1A1_WIN32K_CALLOUT_WATCHDOG_nt!KiSwapContext, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: c3a11e5a-173e-445c-9ba8-19aa99446baf Problem signature: P1: 1a1 P2: ffffe189a7ca9040 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20180320-0354.dmp \\?\C:\WINDOWS\TEMP\WER-661390-0.sysdata.xml \\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20180320-0354.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBD06.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBD34.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBD55.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a1_331b8e4c092dcd416c0e921c177cbd6a8a83b5_00000000_cab_2267941e Analysis symbol: Rechecking for solution: 0 Report Id: b17de353-223e-4c90-a1d0-01964e181e84 Report Status: 268435456 Hashed bucket:
Last edited by zbook; 20 Apr 2018 at 10:39.
Haven’t been able to do the other steps above because I haven’t had time. I ran into some problems where I had to restart and now I’ve been getting the BSOD when trying to login. It’s happened 4 or five times that I’ve tried today.
Steve
Last edited by Steviebabs2685; 05 May 2018 at 23:10.
If you have problems with BSOD before login then boot into safe mode:
Boot into Safe Mode on Windows 10 | Windows 10 Tutorials
In safe mode run the beta log collector > post new zip.
Whenever there is a BSOD > run the beta log collector > post a new zip into the thread.
The memtest86+ version 5.01 can be run overnight and can be run when there are problems with the operating system or boot.