system crash Archives

Winsage

December 25, 2024

Five lesser known Task Manager features in Windows 11

Windows 11's Task Manager includes several features that enhance productivity and system management: - Users can generate a live kernel or full crash dump to troubleshoot crashes, which can be analyzed for root cause identification. - Holding the CTRL key pauses the Task Manager updates, allowing users to easily locate processes, while the F5 key refreshes values for real-time updates. - The "Efficiency Mode" can be activated by right-clicking on an app or process to limit CPU usage, reducing power consumption and freeing up resources. - The Startup Apps section provides an overview of applications that launch at boot, allowing users to disable unnecessary ones to improve startup time and system performance. - The App History tab shows resource usage by applications since the last shutdown, helping users identify which apps are consuming significant resources.

Winsage

November 30, 2024

Windows 11 Recall finally arrives, but with one new problem

The Windows 11 Recall feature is currently in a testing phase and has faced significant challenges, particularly with saving snapshots necessary for its operation. Users have reported delays of several minutes in saving snapshots, and some, like Tom Warren, have experienced issues where snapshots do not save at all. Microsoft has advised users to restart their computers as a potential solution to these problems. The Recall feature, which aims to provide a "photographic memory" for PCs, is available only to beta testers on specific devices and has been delayed due to security and privacy concerns. Other companies, such as Google, are also developing similar AI functionalities.

AppWizard

October 24, 2024

Android 15’s QPR1 Beta 3 is finally here with system crash and foldable fixes

Google has released Android 15 QPR1 Beta 3 for enrolled testers with eligible Pixel devices, addressing a blank screen issue on foldable devices and improving Bluetooth functionality. The update is available for Pixel 6 to Pixel 9 series, Pixel Fold, Pixel 9 Pro Fold, and Pixel Tablet, with version AP41.240925.009. Notable fixes include resolving Bluetooth volume control issues, complications with profile switching, and a blank screen problem when unfolding certain devices. Additional fixes address truncated notifications, system memory paging problems, app icon reversion, system UI crashes, heads-up notification interaction issues, and various stability and connectivity problems. The OTA update began rolling out on October 24, and users can manually check for updates in their settings. The update follows a previous Beta 2 release aimed at Bluetooth and NFC payment issues and hints at future enhancements for Android 16. Some users have reported issues with the stable OS, including inoperability on Pixel 6 devices.

Winsage

August 12, 2024

CLFS Bug Crashes Even Updated Windows 10, 11 Systems

A vulnerability has been discovered in the Common Log File System (CLFS) driver, designated as CVE-2024-6768, which can cause blue screen crashes on various Windows operating systems, including Windows 10, 11, and Windows Server 2022. The flaw is due to improper validation of input data sizes in the CLFS.sys driver, specifically in the "IsnOwnerPage" field of base log files (BLFs). This allows an attacker to create a file with misleading size information, leading to system crashes via the KeBugCheckEx function. The vulnerability has a medium severity score of 6.8 on the CVSS scale and does not compromise data integrity or confidentiality. Fortra reported the issue to Microsoft on December 20, but after investigation, Microsoft did not recognize it as a vulnerability or implement a fix, leaving the flaw unaddressed in Windows systems. Windows Defender has started flagging Fortra's proof of concept as malware, but organizations currently lack a solution until a patch is released by Microsoft.

Winsage

August 12, 2024

Windows 11/10 system driver has BSOD-triggering CVE-2024-6768 flaw on fully updated PCs

A significant disruption occurred in the global landscape of Windows enterprise and business PCs due to a flawed CrowdStrike Falcon IPC Template Type, causing Blue Screens of Death (BSODs). Cybersecurity firm Fortra discovered a new vulnerability, CVE-2024-6768, in the Common Log File System (CLFS.sys) driver of Windows, affecting all versions of Windows 10 and Windows 11. This vulnerability is caused by improper validation of input data, leading to a denial-of-service-triggered BSOD. A crafted .BLF file can allow an unprivileged user to induce a system crash. The attack requires local access to the system. This flaw is similar to CVE-2023-36424, which Microsoft addressed in November 2023 updates.

Winsage

August 12, 2024

New Windows 10 And 11 Blue Screen Of Death Warning Issued

A new vulnerability, designated CVE-2024-6768, has been identified in Windows, affecting all versions of Windows 10, Windows 11, and Windows Server 2022. This flaw is related to the common log file system Windows driver and results from improper validation of input data, leading to a blue screen of death. The vulnerability allows a user with no privileges to crash the system using a specially crafted file, even if the system is fully updated. Microsoft was first notified of this issue in December 2023 but claimed it could not reproduce the vulnerability, despite Fortra's ability to replicate it. No workaround or mitigation has been found, and there is skepticism about Microsoft's likelihood of providing a fix. The timeline of the vulnerability includes multiple reports and evidence provided by Fortra, culminating in the planned publication of the CVE on August 12, 2024.

Winsage

August 12, 2024

Vulnerability in Windows Driver Leads to System Crashes

A newly identified vulnerability, CVE-2024-6768, exists in the Common Log File System (CLFS.sys) driver of Windows operating systems, discovered by Fortra researcher Ricardo Narvaja. This flaw allows an unprivileged user to cause a system crash, resulting in a Blue Screen of Death (BSOD), due to improper input data validation. The vulnerability affects all versions of Windows 10 and 11, regardless of updates. It can be exploited using a crafted .BLF log file format without user interaction, posing a risk of system instability and denial of service (DoS) attacks. The vulnerability has a CVSS base score of 6.8 and is categorized under CWE-1284 for improper validation of input. The attack must be executed locally and has low complexity, making it accessible to less experienced attackers. The exploit manipulates the CLFS client context structure, triggering the KeBugCheckEx function, which leads to the BSOD and system restart.

Winsage

August 4, 2024

How To Fix DPC Watchdog Violation Error In Windows – SlashGear

The DPC Watchdog Violation error is part of Windows's error-checking mechanism that triggers a Blue Screen of Death (BSOD) when a Deferred Procedure Call (DPC) or another process lags beyond its usual execution time. Factors contributing to this error include incompatibility with SSDs or external peripherals, corrupt or missing drivers, corrupted or deleted essential system files, and software conflicts. Troubleshooting steps include disconnecting external devices, checking internal connections, ensuring Windows is updated, booting in Safe Mode, updating the SATA AHCI driver, scanning for corrupted system files using DISM and SFC commands, and restoring the system to a previous point if necessary.

Winsage

August 3, 2024

Who wrote the BSOD screen? Former Windows developer finally has an answer

The Blue Screen of Death (BSOD) in Windows has three distinct origins attributed to different authors. The Windows 3.1 Ctrl+Alt+Del screen, referred to as the "blue screen of unhappiness," was written by Steve Ballmer but was not a response to system crashes. During crashes on Windows 3.1, users saw a black screen. The Windows 95 kernel error screen, which users could bypass, was finalized by Raymond Chen. The true BSOD, the Windows NT kernel error screen, was created by John Vert and indicates a critical system failure.

Winsage

August 2, 2024

Microsoft dev says Steve Ballmer didn’t write the text for the Blue Screen of Death: “There are three different blue-colored screens, and each has a different author”

Dave Plummer, a veteran Microsoft Software Engineer, discussed the history of the Blue Screen of Death (BSOD) in Windows. A recent global IT outage by CrowdStrike affected over 8.5 million Windows devices with BSOD errors. The authorship of the BSOD has been debated, with a blog post by Microsoft developer Raymond Chen clarifying that former CEO Steve Ballmer did not write the BSOD text. Chen identified three versions of blue screens: 1. Windows 3.1 had a "black screen of death" and no BSOD; Ballmer wrote the text for the Ctrl+Alt+Del screen but not the BSOD. 2. Windows 95 allowed users to skip the BSOD, and Chen contributed to its final form in 1995. 3. Windows NT, authored by John Vert, is referred to as the "true Blue Screen of Death," indicating an unrecoverable system failure.