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

[deepblue13]

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.

 

[Vir Gnarus]

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.

 

[deepblue13]

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).

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 ?

 

[x BlueRobot]

Do you have a kernel debugger like WinDbg?

 

[deepblue13]

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.

 

[Vir Gnarus]

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.

 

[deepblue13]

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.

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!

 

[x BlueRobot]

That's good to know

 

[Vir Gnarus]

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.

 

[x BlueRobot]

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

 

[Vir Gnarus]

Doh! Thanks for catching those! Corrected.

 

[x BlueRobot]

Doh! Thanks for catching those! Corrected.

deep, if you are interested in debugging, then remember to read around the subject, there's plenty of free and useful information on the Internet

 

[deepblue13]

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.

Thanks for sharing Vir. Will definitely check it.

Doh! Thanks for catching those! Corrected.

deep, if you are interested in debugging, then remember to read around the subject, there's plenty of free and useful information on the Internet

Yes, I very much am! I want to be like you guys



Ok, I have a new problem. The bsod is no more after removing the driver, but my pc randomly freezes and I can't move my mouse or carry out any further tasks. I have to restart pressing down the shut down button.

I've checked using the Event viewer and it does have critical issues. The ones I suspect that have been causing this with matching dates and time and number of occurrences are: (Screenshots)

I'm clueless, what do I do next ?

I have such a long way to go

 

[x BlueRobot]

I would firstly try this -

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Vir Gnarus]

Preferably you do Option 1 in that article first. That's more likely to fix the problems if they exist rather than just verify there are some.

As for those events, I reeeeally can't see any of those causing the hard lockups. Only one of two things can actually cause these lockups: deadlock caused from drivers, or hardware malfunction.

Do an initial battery of hardware tests as below:

RAM: Memtest86+ - 7+ passes (1 pass = all tests 1x)
CPU: Prime95 - Torture Test; Blend; overnight (9+ hours)
Drives: Seatools - All basic tests aside from the Fix all, Long generic or the advanced ones. Also provide us a screenshot of CrystalDiskInfo output.

All of these are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load. If you can get the system to crash during high load logging, that's even better. Last, make sure that when running Prime95 that you check temps during first 30minutes or so to see if temps are stable. Prime95 runs very hot so be sure your cooling can handle it before letting it run extensively.

In addition to the hardware tests, also turn on Driver VerifierDriver Verifier. Do not select the following checks: Force Pending I/O Requests, IRP Logging, and Low Resource Sim. Select all other checks. Make sure to restart system after you finish setup. If you experience a boot loop afterwards, go into Safe Mode by pressing F8 prior to Windows logo and disable DV there. Provide us any new crashdumps."] [/URL]to help us see if we missed any drivers that's causing problems. Also, check Device Manager and see if there's anything left over from that bluetooth device. If it's still listed under devices, go to its Properties window then under Driver tab click Driver details and mention to us the list of drivers it displays. If there's any Unknown devices, alert us to those as well.

 

[deepblue13]

I'm on it.

RAM is fine. I mentioned earlier I ran 3 tests getting upto a max of 12 passes. All 3 tests were fine.

I'm shifting between using both my HD's, both with the same windows, one was copied using the image on the other. I'm currently using my old HD and it failed a surface test sometime back running a diagnostic.

I'm not having the bsod issue anymore using either of the Hardrives. Both have been hanging though and both have different events. The last 3 were events from the new HD & I'm posting another event from the old HD, which seems to be a driver issue.

I just ran Seatools (on old HD) excluding the tests mentioned & it has passed the rest, S.M.A.R.T - pass, Short Drive Test - pass, Short Generic - Pass.

CrystalDiskInfo is showing me a 'Caution'. I've uploaded a screenshot.

I also attempted SFC using a recovery but somehow, it didn't run. It would just execute the command, give me some info, and then I had to exit because the scan wouldn't start. I'll get the exact info of what it give and post it later. I used Method 1 in Option 1.

Should I run SFC running windows ?

I'll be back soon with more info and screenshots.

 

[deepblue13]

Windows has also been taking slightly longer to start.

More than 30 seconds. It's recent & takes around a full 2-3 mins.

 

[deepblue13]

Hwinfo

 

[Vir Gnarus]

Huh?! That's strange, where's the voltage sensor readings? There should be readings for the different rails (5v, 3.3v, 12v) from Hwinfo.

The warning with CrystalDiskInfo on the SMART readings is from a current pending sector, as in it found a messy sector on the drive that may be bad and has flagged it. Should it continue to cause issues it will label it bad and revert to using a backup sector instead. Since it's just one sector, I wouldn't put much concern into it. Most cases it'll actually go away once it discovers the sector is OK.

Have you done the Prime95 test yet? There's also the Intel Burn Test, which only takes around 45 minutes to run, but does things differently so use it in addition to the Prime95 test. Both tests - especially IBT - runs the CPU real hot, so make sure to watch those temps on HwInfo! If it stabilizes on a good temp for 30 minutes, it should be good from then on.

 

[deepblue13]

Ok. I lost windows after changing those iffy (on one of the thread links here) driver verifier settings.

It would not start again. Luckily I had a backup made (the same one I loaded on to my new HD), so I'm good (apart from losing a few recent bookmarks from a few days old). Just formatted my whole old HD using disk clean all from command prompt using the recovery, and now I've loaded windows backup on it & had to do a Total Uninstall of the usb bluetooth that was causing the bsod as it was part of the backup. So far everything is good.

Should I run tests again & post info after the format ? Or wait & see if it hangs again ?

Ok, I missed two readings at the end. I'm uploading them after the format but they don't look like the readings you're talking about (5v, 3.3v, 12v). These are all I'm getting from top to bottom (Same before & after formatting). I'm using version 4.24-2000. Do I need to change any settings ? I used the sensors only option as was advised.

Also, Crystaldisk now shows Good and the Caution is no more after the format. Screenshot attached.

No, I have yet to run Prime95 & the Intel Burn Test.