Reply to thread

Message

<blockquote data-quote="Deleted member 65228" data-source="post: 684089">Yep <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />(ntoskrnl.exe base address (because the drivers are under ntoksrnl.exe) + the address from log of the crash) = where the crash probably occurred -&gt; usable to potentially identify the driver responsibleIt isn&#039;t indefinite though, it won&#039;t be 100% accurate all the time.[USER=60798]@Weebarra[/USER] needs to revert or disable that Bluetooth driver and see if it still happens after that if she&#039;s up for it (maybe she won&#039;t want to do that). If she does want to and can though and the issue still persists, then more options need to be considered for investigation and remedial <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Only needs to become complicated if it must <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />If she cannot disable it properly or revert, and her system is already crashing... She can try doing something like finding the service responsible for the Bluetooth driver, stopping it and then deleting it. She can alter the Properties in case it is set for Boot Start instead of on-demand (also this is enforced via registry so if such settings cannot be changed normally, should work via Registry).But just make sure any important stuff is backed up because messing with stuff like this can cause more problems...</blockquote>

[QUOTE="Deleted member 65228, post: 684089"] Yep :) (ntoskrnl.exe base address (because the drivers are under ntoksrnl.exe) + the address from log of the crash) = where the crash probably occurred -> usable to potentially identify the driver responsible It isn't indefinite though, it won't be 100% accurate all the time. [USER=60798]@Weebarra[/USER] needs to revert or disable that Bluetooth driver and see if it still happens after that if she's up for it (maybe she won't want to do that). If she does want to and can though and the issue still persists, then more options need to be considered for investigation and remedial :) Only needs to become complicated if it must :) If she cannot disable it properly or revert, and her system is already crashing... She can try doing something like finding the service responsible for the Bluetooth driver, stopping it and then deleting it. She can alter the Properties in case it is set for Boot Start instead of on-demand (also this is enforced via registry so if such settings cannot be changed normally, should work via Registry). But just make sure any important stuff is backed up because messing with stuff like this can cause more problems... [/QUOTE]

Verification