Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Hardware
Hardware Troubleshooting
My laptop has gone mental
Message
<blockquote data-quote="Deleted member 65228" data-source="post: 684070"><p>It is always because of an error in kernel-mode - and BSOD is exclusive to Windows, other OS may not even have a replication or may have their own sort of error system induced by kernel-mode crashes (OS X have Kernel Panic warning I think). This can be caused by improperly working hardware (now the code executing in kernel-mode can run into an issue it wouldn't have run into if the hardware was in correct condition) or a mistake by the developer.</p><p></p><p>If any Windows files are corrupt, as long as it is a user-mode component, no crash would happen (unless specific scenario -> read end of this bit). Crashes in user-mode won't be system-wide because user-mode programs don't have access to all the memory - this is why user-mode is especially important. However, user-mode components improperly working can prevent the OS from working correctly as well (whether crash or not). Also, some user-mode processes in Windows can have a "critical" status to force a BSOD crash if they are terminated (so if they crash as well that counts -> BugCheck detects the termination -> BugCheck CRITICAL_PROCESS_DIED).</p><p></p><p>Basically, when a crash happens in kernel-mode, it affects everything system-wide because you can access all the memory. In user-mode however, every application is restricted in the sense it can only access its own memory (by default). When that program crashes, it isn't big enough problem to cause a crash because the only affected memory was the processes' own. Also, Windows uses virtual memory and points it to the real addresses, it handles this all by itself by default. So when you use an address in memory, it will be a virtual memory address -> pointed to the physical address handled by the OS internally (unless you have privileged code via a device driver though -> the mechanism was designed to prevent user-mode applications from having too much control, separating running code so only the code that needs to access/operate hardware components can).</p><p></p><p>So anything like a device driver, "critical" user-mode process being terminated (-> kernel-mode detects this via BugCheck which is an internal feature in Windows -> crash - does the same for other things like detection of kernel-mode patching when PatchGuard is present), can cause a BSOD. Hardware issues -> can stop kernel-mode code working correctly -> crash. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>I recon that the crash is likely because of the Bluetooth driver update [USER=60798]@Weebarra[/USER] performed a few days ago, though. Who knows.</p></blockquote><p></p>
[QUOTE="Deleted member 65228, post: 684070"] It is always because of an error in kernel-mode - and BSOD is exclusive to Windows, other OS may not even have a replication or may have their own sort of error system induced by kernel-mode crashes (OS X have Kernel Panic warning I think). This can be caused by improperly working hardware (now the code executing in kernel-mode can run into an issue it wouldn't have run into if the hardware was in correct condition) or a mistake by the developer. If any Windows files are corrupt, as long as it is a user-mode component, no crash would happen (unless specific scenario -> read end of this bit). Crashes in user-mode won't be system-wide because user-mode programs don't have access to all the memory - this is why user-mode is especially important. However, user-mode components improperly working can prevent the OS from working correctly as well (whether crash or not). Also, some user-mode processes in Windows can have a "critical" status to force a BSOD crash if they are terminated (so if they crash as well that counts -> BugCheck detects the termination -> BugCheck CRITICAL_PROCESS_DIED). Basically, when a crash happens in kernel-mode, it affects everything system-wide because you can access all the memory. In user-mode however, every application is restricted in the sense it can only access its own memory (by default). When that program crashes, it isn't big enough problem to cause a crash because the only affected memory was the processes' own. Also, Windows uses virtual memory and points it to the real addresses, it handles this all by itself by default. So when you use an address in memory, it will be a virtual memory address -> pointed to the physical address handled by the OS internally (unless you have privileged code via a device driver though -> the mechanism was designed to prevent user-mode applications from having too much control, separating running code so only the code that needs to access/operate hardware components can). So anything like a device driver, "critical" user-mode process being terminated (-> kernel-mode detects this via BugCheck which is an internal feature in Windows -> crash - does the same for other things like detection of kernel-mode patching when PatchGuard is present), can cause a BSOD. Hardware issues -> can stop kernel-mode code working correctly -> crash. :) I recon that the crash is likely because of the Bluetooth driver update [USER=60798]@Weebarra[/USER] performed a few days ago, though. Who knows. [/QUOTE]
Insert quotes…
Verification
Post reply
Top