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: 684059"><p>Blue Screen Of Death is always caused by code running in kernel-mode. When hardware is related to the crash, the crash is still caused by code running in kernel-mode AFAIK (although hardware is out of my scope - problem caused because of the hardware issue -> cannot do something properly -> crash).</p><p></p><p>I think it is probably caused by buggy code within a driver you have on your system which is of course active, as opposed to hardware. The developer probably made a mistake with the calculations when dealing with memory and this is likely the cause... Maybe it is to do with incorrect variable initialisation though; there can be many things which can lead to this cause. It seems the BugCheck code isn't documented in WDK (Windows Driver Kit) docs although I have never triggered it when developing...</p><p></p><p>For example... Memory might be allocated with ExAllocatePool/WithTag and then used a wrong calculation when dealing with the memory so the header for the block was messed up (e.g. maybe when using memcpy with it to copy to the memory or anything similar). -> assuming its related to software and not hardware.</p><p></p><p>Since you said this is only a recent thing and a few days ago you did an update for a driver related to Bluetooth, I would advise you to... undo this update if possible. Using outdated drivers is a bad idea as well because driver updates can patch old vulnerabilities/bugs but if the new driver is the cause then reverting should prevent the crash. Try disabling Bluetooth for now in that case, assuming you can do this properly/it will prevent the driver from being used afterwards.</p><p></p><p>If it turns out to not be related to the Bluetooth driver then investigation can be pretty troublesome depending on how much software you have installed. The error mentions ntoskrnl.exe (which is the Windows Kernel) but this does not actually mean the bug was caused by Microsoft itself. You see, the device drivers are actually put under ntoskrnl.exe (because unless a device driver is started via a bootkit through something like infection of a Master Boot Record, it will not "truly" be in ring 0 (Kernel-Mode), but actually ring 1 and 2 which is more privileged, and ring 3 is used for normal applications).</p><p></p><p>I know this sort of stuff sucks. My old laptop used to have an overheating problem and it would work but after an hour or two it'd be a game from a horror film on when it would "hang up" explorer.exe. It wasn't caused by software, it was hardware related due to me not treating the overheating issue sooner. Every-time it would happen, it would hang up explorer.exe and completely freeze until I hard-shut off the laptop, let it cool down for awhile and then turned it back on.</p><p></p><p>My advice would be to try reverting with Bluetooth/disable it for now and see what happens. Do you have any backup images you can use to revert to a previous time, or even a Windows Restore Point? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> If you do decide to just get a new system... Maybe try doing a format and OS re-installation just beforehand to see if that changes anything (and if it still happened then, then it is likely hardware related IMO)</p><p></p><p>I really hope you can get this fixed. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="Deleted member 65228, post: 684059"] Blue Screen Of Death is always caused by code running in kernel-mode. When hardware is related to the crash, the crash is still caused by code running in kernel-mode AFAIK (although hardware is out of my scope - problem caused because of the hardware issue -> cannot do something properly -> crash). I think it is probably caused by buggy code within a driver you have on your system which is of course active, as opposed to hardware. The developer probably made a mistake with the calculations when dealing with memory and this is likely the cause... Maybe it is to do with incorrect variable initialisation though; there can be many things which can lead to this cause. It seems the BugCheck code isn't documented in WDK (Windows Driver Kit) docs although I have never triggered it when developing... For example... Memory might be allocated with ExAllocatePool/WithTag and then used a wrong calculation when dealing with the memory so the header for the block was messed up (e.g. maybe when using memcpy with it to copy to the memory or anything similar). -> assuming its related to software and not hardware. Since you said this is only a recent thing and a few days ago you did an update for a driver related to Bluetooth, I would advise you to... undo this update if possible. Using outdated drivers is a bad idea as well because driver updates can patch old vulnerabilities/bugs but if the new driver is the cause then reverting should prevent the crash. Try disabling Bluetooth for now in that case, assuming you can do this properly/it will prevent the driver from being used afterwards. If it turns out to not be related to the Bluetooth driver then investigation can be pretty troublesome depending on how much software you have installed. The error mentions ntoskrnl.exe (which is the Windows Kernel) but this does not actually mean the bug was caused by Microsoft itself. You see, the device drivers are actually put under ntoskrnl.exe (because unless a device driver is started via a bootkit through something like infection of a Master Boot Record, it will not "truly" be in ring 0 (Kernel-Mode), but actually ring 1 and 2 which is more privileged, and ring 3 is used for normal applications). I know this sort of stuff sucks. My old laptop used to have an overheating problem and it would work but after an hour or two it'd be a game from a horror film on when it would "hang up" explorer.exe. It wasn't caused by software, it was hardware related due to me not treating the overheating issue sooner. Every-time it would happen, it would hang up explorer.exe and completely freeze until I hard-shut off the laptop, let it cool down for awhile and then turned it back on. My advice would be to try reverting with Bluetooth/disable it for now and see what happens. Do you have any backup images you can use to revert to a previous time, or even a Windows Restore Point? :) If you do decide to just get a new system... Maybe try doing a format and OS re-installation just beforehand to see if that changes anything (and if it still happened then, then it is likely hardware related IMO) I really hope you can get this fixed. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Top
