BSOD while scanning through music on iTunes 10.5, bugcheck 0x00000050

[pikalax]

I am running Windows 7 Home Premium x64 SP1. The system came with RTM Windows 7 and was upgraded to SP1 after activation. The system itself is only three weeks old and still covered under the 30-day limited warranty. This is the second BSOD on this system; thread for the first is located here.

Here are the event viewer details for the bugcheck:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffffa80fffff597, 0x0000000000000000, 0xfffff80002cc9abd, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101711-30903-01.

10/17/11 5:06:38 PM

Both crashes occurred in connection with the Bluetooth dongle. Drivers installed currently were obtained automatically by Windows upon initially inserting the device. I have just installed the drivers provided by the dongle manufacturer, IOGear. If my system crashes again, would you recommend that I remove the dongle and permanently uninstall the drivers?

I am attaching the requested files as well as an event log containing every information, warning, and error relating to BTSHUB, which may very well be the devil behind these BSODs.

 

[zigzag3143]

I am running Windows 7 Home Premium x64 SP1. The system came with RTM Windows 7 and was upgraded to SP1 after activation. The system itself is only three weeks old and still covered under the 30-day limited warranty. This is the second BSOD on this system; thread for the first is located here.

Here are the event viewer details for the bugcheck:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffffa80fffff597, 0x0000000000000000, 0xfffff80002cc9abd, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101711-30903-01.

10/17/11 5:06:38 PM

Both crashes occurred in connection with the Bluetooth dongle. Drivers installed currently were obtained automatically by Windows upon initially inserting the device. I have just installed the drivers provided by the dongle manufacturer, IOGear. If my system crashes again, would you recommend that I remove the dongle and permanently uninstall the drivers?

I am attaching the requested files as well as an event log containing every information, warning, and error relating to BTSHUB, which may very well be the devil behind these BSODs.

These were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[pikalax]

I do not have a blank CD at my disposal. And my computer blue-screened again while I was out. I strongly believe that the problem device was the Bluetooth, and so I have unplugged the Bluetooth dongle and am planning on smashing it fifty times with a sledgehammer. ... No, not really, but I am going to do what I can to reflect this on IOGear's reputation.

EDIT: The offending system utility appears to be ntoskrnl.exe. My most recent .NET update was KB2572078 on October 12, a security update. Should I roll back that update?

 

[zigzag3143]

I do not have a blank CD at my disposal. And my computer blue-screened again while I was out. I strongly believe that the problem device was the Bluetooth, and so I have unplugged the Bluetooth dongle and am planning on smashing it fifty times with a sledgehammer. ... No, not really, but I am going to do what I can to reflect this on IOGear's reputation.

EDIT: The offending system utility appears to be ntoskrnl.exe. My most recent .NET update was KB2572078 on October 12, a security update. Should I roll back that update?

Ntoskrnl.exe is not a utility it is a core operating system file and definitely not to blame. You have probably been using Blue screen view to diagnose.

If it works in safe mode but not a normal boot it probably is a driver, and not necessarily an old one. ONly way to tell is to supply us with information from the two tests.