BSOD 0x0000003b ntoskrnl.exe+75b80 mostly on Shutdown

Page 1 of 3 123 LastLast

  1. Posts : 14
    Windows 7 Home Premium 64bit.
       #1

    BSOD 0x0000003b ntoskrnl.exe+75b80 mostly on Shutdown


    Hi. I've been getting the error mostly when I shut down.

    Attached along is the SF file. I've done 3 memtest86+ tests, one with 5 passes, second with 8 passes & third with 12 passes. So the memory is good.

    Also, I have a brand new WD HD. The same problem was taking place when I was using the old HD. I made a windows backup and used the image after installing the new HD. I'm pretty sure the HD is fine too. To me it looks like a system/software issue.

    Also the Windows Resource Protection in the SFC system scan found corrupt files 'but was unable to fix some of them'. I have a screenshot included. Don't know where to go next.

    Not sure what's causing the error. It would be great if anybody can identify the issue and also explain how it was found.

    Thanks.
    Last edited by deepblue13; 18 Sep 2013 at 15:11.
      My Computer


  2. Posts : 1,314
    Windows 7 64-bit
       #2

    To fix files with SFC it often means needing to go into SFC through the recovery environment on the Windows CD as instructed here.

    Anyways, I checked the crashdumps and they all point to some btprot.sys driver being responsible. From the Driver Reference DB I use it lists it here as part of some iAnywhere bluetooth USB driver, so it sounds as if it's for some USB bluetooth dongle. The date for the driver is quite old at 2008 (pre-Windows 7), and the reference DB lists the driver and product as being EOL at 2010. I'm not sure what product this driver belongs too, but it needs to be removed and replaced with a more recent one that is Windows 7 compatible.
      My Computer


  3. Posts : 14
    Windows 7 Home Premium 64bit.
    Thread Starter
       #3

    Thanks Vir, very much possible since I have been using a usb bluetooth and it had the software installed. I've done a Total Uninstall with all drivers removed and I'll run for some time to check if anything reoccurs (so far so good on restart).

    Vir Gnarus said:
    Anyways, I checked the crashdumps and they all point to some btprot.sys driver being responsible.
    I'm new to this so is it ok to ask how crashdumps point to a certain driver ? Does the crash address point to it ? How do you figure it out ?
      My Computer

  4.    #4

    Do you have a kernel debugger like WinDbg?
      My Computer


  5. Posts : 14
    Windows 7 Home Premium 64bit.
    Thread Starter
       #5

    x BlueRobot said:
    Do you have a kernel debugger like WinDbg?
    No. I got to the page but lost it. I don't know how it works. I think on the link it was for Win8 or something.
      My Computer


  6. Posts : 1,314
    Windows 7 64-bit
       #6

    The debuggers in the Win8.1 Preview WDK can be installed for Windows 7, it's only just updated to incorporate stuff for the new Windows 8 environment as well.

    Whenever you get it to open up properly and load symbols, the !analyze -v command does basic analysis to start off with, and fortunately in your case it's very consistent and accurate in that the btprot.sys driver always gets tagged as the culprit, because it was a 3rd-party driver that happened to be related to each incident. For other scenarios, it will take a good bit more prowess than what !analyze -v can do, since it can only go so far and assume what is causing things, so it's up to manual analysis to continue the search.
      My Computer


  7. Posts : 14
    Windows 7 Home Premium 64bit.
    Thread Starter
       #7

    Vir Gnarus said:
    The debuggers in the Win8.1 Preview WDK can be installed for Windows 7, it's only just updated to incorporate stuff for the new Windows 8 environment as well.
    Ok, got it.

    Vir Gnarus said:
    Whenever you get it to open up properly and load symbols, the !analyze -v command does basic analysis to start off with, and fortunately in your case it's very consistent and accurate in that the btprot.sys driver always gets tagged as the culprit, because it was a 3rd-party driver that happened to be related to each incident. For other scenarios, it will take a good bit more prowess than what !analyze -v can do, since it can only go so far and assume what is causing things, so it's up to manual analysis to continue the search.
    Oh WinDbg. I was lost for a moment there (since I have yet to download).

    Ok, I'll try next time. So far it seems to have solved the problem. I've been using my pc and haven't had any problems since I removed it.

    If there's anything more, I'll get back & reply here. I'll also mark the thread as solved in the coming days if everything is good.

    Thanks again!
      My Computer

  8.    #8

    That's good to know :)
      My Computer


  9. Posts : 1,314
    Windows 7 64-bit
       #9

    If you have further interest in this kind of troubleshooting and understanding deep Windows internals, you can start off with something I conjured up in my spare time here. The links section is the most helpful part of it, directing to many, many resources that can help get you started. My favorite is the online show "Defrag Tools" (also linked there) which starts from the very beginning of how to setup Windbg to deep troubleshooting knowledge like how DPCs work.

    EDIT: Corrected.
    Last edited by Vir Gnarus; 20 Sep 2013 at 08:57.
      My Computer

  10.    #10

    Vir Gnarus said:
    If you have further interest in this kind of troubleshooting and understanding deep Windows internals, you can start off with something I conjured up in my spare time here. The links section is the most helpful part of it, directing to many, many resources that can help get you started. My favorite is the online show "Debug Tools" (also linked there) which starts from the very beginning of how to setup Windbg to deep troubleshooting knowledge like how DPCs work.
    Your link points to the homepage of this website, and it's Defrag Tools
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:00.
Find Us