Wifi causing BSOD on Windows 7 64 bit

The Intel 5300 wifi card driver is causing Blue Screen of Death (BDOS) on my x200s Windows 64 bit ultimate.
A typical scneraio would be:
- Turn wifi on
- Connect to access point
- Within a few minutes, Internet activity will blue screen the laptop
Wifi card and motherboards were replaced.
After trying a bunch of stuff, I resigned to wipe the laptop and do a fresh operating system install. The result is still BSOD on wifi.
Wifi drivers are the latest from Lenovo (13.0.0.107)
Intel has a newer version (13.1.1.1) for the 5300 wifi card on the Intel web site. I am not sure it is compatible with Thinkpad.
Any advice would be appreciated, as the laptop is unusable with the wifi on.
Thank!

Similar Messages

Reader 9 causes BSOD on Windows XP Pro

We have a few systems here that are having real problems with Adobe Reader 9. When the users attempt to open a .pdf file, they get a BSOD, and the system reboots. Once the system comes back up, they are able to open the offending file with no problems.
Here are details of our systems:
Dell Optiplex 755
Windows XP Pro SP3
2GB Ram
32 Bit OS
I have found this occurs most often when opening pdf's that were created with earlier versions.
I'm sure I have left out some vital piece of information, so if you need clarification on something, please ask. Any suggestions would be greatly appreciated!

[While the original post was for Reader 9, I found this same problem with Acrobat 9 Pro, and found a solution.]
Problem: Opening one PDF file is fine, but once you open the second file -- BSOD.
Cause: There is still a problem with Adobe's 2D GPU Acceleration feature.
Per http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405218&sliceId=1, "If acceleration hardware is detected, then optimization is enabled for all files except the first one opened when Acrobat launches." That is why the first file opens OK, but the second causes BSOD. Adobe is either not detecting acceleration hardware correctly, or is not calling it correctly.
Temporary Solution:
1. In Acrobat or Adobe Reader, choose to Edit > Preferences.
2. Go to the Page Display panel.
3. Uncheck Use 2D GPU acceleration.
I tested my machine [Dell Optiplex 755, ATI Radion HD 2400 XT 8.420.0.0, Win XP Pro, Adobe 9 Pro] with "2D GPU acceleration" checked, attempted open of 4 PDFs from File Explorer -->first one opened, then BSOD, rebooted, unchecked "2D GPU", attempted the exact same operation --> all four opened in their windows and now I am happily typing on this page.
This is per http://kb.adobe.com/selfservice/viewContent.do?externalId=324073, which is a post from two years ago and relates to Adobe 8. So, Dell has been fielding calls on this for at least two years. Way to stick in there, Dell. Two years ago, Adobe knew the problem ("You are using an desktop ATI video card with driver version 8.291 or 8.301 and have the Acrobat Page Display Preference 'Use 2D GPU acceleration' enabled." was what they said back then, and recommended updating the video drivers. So, Dell stays with it, Adobe says to update your drivers. Well, I bought an entirely new Dell to get the latest drivers and it didn't help.
Permanent solution:
Adobe needs to get 2D GPU acceleration to really work (how about a line of code where you check whether it is going to work before you execute it?) or ship their product with that feature off by default.

3.0 causes BSOD in Windows 7 on Mac Pro

I just did my third reinstallation of windows 7 on my mac pro and I think I've narrowed the bsod problem to the 3.0 bootcamp drivers. Every time I go to install steam, which is really the only reason I use windows, It gives me the bsod. The bsod references something about HFS drives. Or maybe it's my graphics card. I did put in the GTX 285 from EVGA. Does anyone else have this issue? Anyone find a fix? Will 2.1 work?

been running windows 7 for 2 weeks
when using the graphics drivers that come with bootcamp3.0
i initially encountered video playback freezing the system
but after i download windows 7 drivers from nvidia, it seems ok now
perhaps you could try that first?
http://www.nvidia.com/object/win7winvista_32bit_190.62whql.html

Z61p ATI Mobility FireGL BSOD on Windows 7 64 bit

Am having many BSOD and 'windows reported and error'
... Have tried Lenovo 64 driver 8.361 per system update, tried 8.561 per Vista 64 / Win 7 on Lenovo Support and now trying ATI Beta 10.1 CCC pack.
All crash and burn
Recreating: ... Either try any of the Catalyst Control Centre 3D setting - trip down to DOA machine
or
work for a while and periodically when doing non 3D things such as trying to watch a DVD or web browsing ... Windows BSOD with dump ... 'Windows has recovered from and error ...'
Has anyone found a solution to this?
IBM pointed me to two Lenovo web pages about support for Windows 7 - basicaly the Z series ThinkPads are not listed ????
Any help would be welcome.
Rgs
Bruce

Give this a shot at your own risk, although some people on TPF have been praising it...
http://forums.mydigitallife.info/archive/index.php/t-13124.html
The only reason why I'm saying "at your own risk" is because I haven't tested it personally, because I don't have a machine running W7 with an appropriate GPU.
Good luck.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

BSOD in Windows XP after connecting a USB hard drive

Hi everyone!
I have a mid 2009 iMac i5. After plugging in an external hard drive I get a BSOD in Windows XP SP3.
I first installed Win XP using Bootcamp and later on I also installed Parallels 6.0
to avoid rebooting in order to get to Win XP. Windows running on Parallels displays BSOD as well
when a hard drive is plugged in.
Everything works fine under Mac OS X (latest version available).
Thank you in advance for any suggestions.
Lukasz

Fingers crossed we might be able to track down the cause of the problem by interrogating minidumps of the blue screens with Windows debugging tools.
So first we'd better check to see if your PC has been collecting minidumps of the crash.
Open My Computer, and see if you can find a directory called C:\Windows\Minidump. (That's where minidumps usually go on a PC, so long as the Systemroot hasn't been set to some other folder.)
If it's been collecting minidumps, there should be files in there with names like "Mini(number-numbers).dmp" or just "(numbers-numbers).dmp".
(If you have "Hide filename extensions for known file types" enabled on the PC, the ".dmp" extension may not appear on the dump files. The numbers in the file name will be different for each minidump, if minidumps are present.)
Are there any minidumps about on the PC? If so, we'll go digging in them.
1. Download and install the Windows debugging tools from here:
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
2. Go "Start > All Programs > Debugging Tools For Windows > Windbg". Once you open Windbg, you will presented with a blank screen.
3. Click on "File > Symbol File Path". Here you will enter the symbols path. Symbols are needed to effectively debug.The path will be:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
4. Enter in this path and click OK. Now, go to "File > Save Workspace" so that your symbols path is saved for future use.
5. Go to "File > Open Crash Dump" and load the file.
(An "Open Crash Dump" screen will appear ... doubleclick "My Computer", doubleclick "Local Disk", doubleclick "Windows", doubleclick "Minidump", and doubleclick on one of the minidumps in there that was generated at the same time as the Classic was plugged in.)
You will/should get a message to save base workspace information. Choose no.
Now you will get a debugging screen. It takes a little bit to run it, as the symbols have to be downloaded as they are needed.
After the "bugcheck analysis" part of the screen comes up, look for the component that seems to be causing the crash. (It'll say "Probably caused by" ...)
Let us know the precise name of the component. (Include any file name extensions like .dll or .sys.)
If you can, have a look at several of your crash dumps generated by USB-pluggings-in. Are all the crashes being caused by the same component? If not, could you let us know the names of the various components being cited in the various crash dumps?

Wifi not working with Windows Vista - BT in denial

I run a laptop repair centre in Dundee and have BT Business Broadband which was working fine until a few days ago.
Now, any vista machine refuses to connect to the wifi while XP and Windows 7 are unaffected.
I have hundreds of laptops in stock at any one time and this issue is affecting them every single machine installed with Vista. These same machines work fine when connected to another wifi service (virgin media).
I phoned to report this fault and have been told that it's not BTs problem and I'd have to pay to have someone come and look at it. I was put through to a supervisor who told me that it "was Bill Gate's fault"!!!!!
I've worked with Vista for the 7 or so years it's been out and know the operating system inside out.
This is NOT a fault with the machines, or Vista, this is definitely a router fault but the supervisor refuses to believe this.
I'm now trying to cancel my contract as I'm not receiving a full service.
This is absolutely unbelievable that such a major company can just brush me aside and deny there's any fault. They won't even entertain the idea of sending me another router to try!
Has anyone else had this problem?

After phoning the same number, this time I got someone very helpful who knew their job well.
Apparently there is a known issue affecting certain routers at the moment. This problem causes connection issues with Vista machines on wifi and the fix is to reduce the encryption from WPA to WEP.
This works perfectly.
The person then explained that they were expecting a firmware update to be released soon for the routers which should cure the problem properly.
Why in **bleep** did the person this morning not know that, and even worse, why didn't his supervisor that I demanded to talk to not know that either. He point blank refused to even consider the notion that the fault lay with BT!
Some staff need retrained not only on the technical aspect of their job but how to deal with customers as well....
Thanks for the help folks

Drivers cause BSOD {URGENT}

Good day
About 2 years ago I bought this laptop for a really good deal and i was impressed with the performance i got with it. Its quite a powerful and quality piece of tech.
There are some drawbacks...
In the two years ive had it ive formatted the laptop twice. Once to upgrade to windows 8.1, and now because windows got corrupted and it didnt want to use a restore point. Which is normal for windows, it doesnt last forever.
Drivers are a mess. Most i can gather is i'm suppose to download my laptop's drivers from here.
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-dv6-Entertainment-Notebook-PC-series/522...
There are 3 different wireless lan drivers, the chipset drivers cause BSOD's, i can install every single driver on the list and i still have about 4 unknown devices in my device manager.
Point is Im better off googling for the hardware ID's and scrubbing forums for my drivers.
Please could Someone supply me a link where i can download a complete Driver DVD image for my laptop model that works. I am more than willing to download a 1.4 gig torrent if it has proper work everytime drivers.
Infact i would even drive to hp head office if they could supply me with a hardcopy.
Help Please!
Before i break something.
Back on windows 7 btw

Hi @Pixelite ,
Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion dv6-7030ei Notebook and needing a recovery disk. Here is a link to show you how to and or order the Recovery Media you need.
FWI: The driver page shows all drivers that were installed on all HP Pavilion Notebooks.
I would uninstall all the drivers with a yellow mark or caution on it. Restart the Notebook and if they are still there right click on the device and install or update the drivers.
I hope this helps you out.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

ITuneHelper crashing with BSOD on Windows 7

iTunesHelper.exe in crashing sometimes with BSOD on Windows 7 64 bit.
here is part of WinCrashReport :
Crash Report For iTunesHelper.exe
Created by using WinCrashReport
http://www.nirsoft.net/utils/application_crash_report.html
General Exception Information:
Operating System: Windows 7 Home Premium (6.1.7601)
Report Time: 05/01/2013 08:57:33
Process Filename: C:\Program Files (x86)\iTunes\iTunesHelper.exe
Process ID: 4236
Thread ID: 5432
Process Description: iTunesHelper
Process Version: 11.0.1.12
Process Company: Apple Inc.
Product Name: iTunes
Product Version: 11.0.1.12
Crash Address: 75CCC41F
Crash Address (Relative): KERNELBASE.dll!RaiseException+0x58
Exception Code: 406D1388
Exception Description:
Exception Parameter (1): 00001000
Exception Parameter (2): 72FF8914
Exception Parameter (3): 00001538
Exception Parameter (4): 00000000
Crash Code Bytes:
C9 C2 10 00 CC CC CC CC CC 8B FF 55 8B EC 56 8B
75 08 83 FE F4 72 18 83 FE F6 77 13 8D 45 08 50
6A 00 56 E8 DD 02 00 00 85 C0 74 03 8B 75 08 56
FF 15 34 10 CC 75 5E 85 C0 7C 05 33 C0 40 EB 08
Strings in the stack:
033DF414 77E14880 -> TCF
033DF454 72C6DE28 -> KERNEL32.DLL
033DF680 033DFAF8 -> Ui2
033DF868 72FF8914 -> com.apple.CFSocket.private
Call Stack (Method 1):
033DFD54 72F4E24C CoreFoundation.dll!CFDataGetBytes+0x60
033DFD68 00000018
033DFE3C 5D00015C
Call Stack (Method 2):
033DF85C 75CCC41F KERNELBASE.dll!RaiseException+0x58
033DFA28 77D43C94 ntdll.dll!RtlImageNtHeader+0xb10
033DFA2C 77D43CC3 ntdll.dll!RtlImageNtHeader+0xb3f
033DFAF4 77D871D5 ntdll.dll!WinSqmSetIfMaxDWORD+0x31
033DFAFC 77D3E38C ntdll.dll!RtlInitUnicodeString+0x164
033DFB70 77D3E023 ntdll.dll!RtlFreeHeap+0x7e
033DFB88 77D3E0F2 ntdll.dll!RtlAllocateHeap+0xac
033DFB90 75ED11E0 kernel32.dll!TlsGetValue
033DFBB0 76EA2E4D WS2_32.dll!htons+0xc2
033DFBC0 76EA6AD6 WS2_32.dll!__WSAFDIsSet+0x4c
033DFBD4 77D2F89C ntdll.dll!NtWaitForSingleObject
033DFBE8 77D2F8B1 ntdll.dll!NtWaitForSingleObject+0x15
033DFBEC 75166F0F mswsock.dll+0x6f0f
033DFC2C 75166D30 mswsock.dll+0x6d30
033DFCAC 77D2FE36 ntdll.dll!NtDuplicateObject+0x12
033DFCC0 75164200 mswsock.dll+0x4200
033DFCE8 7516432A mswsock.dll+0x432a
033DFD00 76EA2F7D WS2_32.dll!WahReferenceContextByHandle+0x5d
033DFD08 75182F27 mswsock.dll!s_perror+0x1343
033DFD18 76EA6A28 WS2_32.dll!select+0x9f
033DFD58 72F4E24C CoreFoundation.dll!CFDataGetBytes+0x60
033DFD88 76EC3912 WS2_32.dll!WahWriteLSPEvent+0x2ad
033DFD98 72F7560B CoreFoundation.dll!CFSocketGetDefaultNameRegistryPortNumber+0x863
033DFDC0 77D438BE ntdll.dll!RtlImageNtHeader+0x73a
033DFDC8 77D4389A ntdll.dll!RtlImageNtHeader+0x716
033DFEB0 77D43492 ntdll.dll!RtlImageNtHeader+0x30e
033DFED0 75ED14DD kernel32.dll!HeapFree+0x14
033DFEE4 730D4C39 MSVCR80.dll!free+0xcd
033DFEF0 730D4C58 MSVCR80.dll!free+0xec
033DFF08 731613D8 MSVCR80.dll!__badioinfo+0x40
033DFF10 730D2C78 MSVCR80.dll!__set_flsgetvalue+0xd
033DFF24 72F97A05 CoreFoundation.dll!CFHashBytes+0x113
033DFF30 730D29BB MSVCR80.dll!_endthreadex+0x3b
033DFF58 730D8CED MSVCR80.dll!__dllonexit+0x9d
033DFF68 730D2A47 MSVCR80.dll!_endthreadex+0xc7
033DFF70 75ED33AA kernel32.dll!BaseThreadInitThunk+0x12
033DFF7C 77D49EF2 ntdll.dll!RtlInitializeExceptionChain+0x63
033DFFBC 77D49EC5 ntdll.dll!RtlInitializeExceptionChain+0x36
033DFFC0 730D29E1 MSVCR80.dll!_endthreadex+0x61

iTunesHelper.exe in crashing sometimes with BSOD on Windows 7 64 bit.
here is part of WinCrashReport :
Crash Report For iTunesHelper.exe
Created by using WinCrashReport
http://www.nirsoft.net/utils/application_crash_report.html
General Exception Information:
Operating System: Windows 7 Home Premium (6.1.7601)
Report Time: 05/01/2013 08:57:33
Process Filename: C:\Program Files (x86)\iTunes\iTunesHelper.exe
Process ID: 4236
Thread ID: 5432
Process Description: iTunesHelper
Process Version: 11.0.1.12
Process Company: Apple Inc.
Product Name: iTunes
Product Version: 11.0.1.12
Crash Address: 75CCC41F
Crash Address (Relative): KERNELBASE.dll!RaiseException+0x58
Exception Code: 406D1388
Exception Description:
Exception Parameter (1): 00001000
Exception Parameter (2): 72FF8914
Exception Parameter (3): 00001538
Exception Parameter (4): 00000000
Crash Code Bytes:
C9 C2 10 00 CC CC CC CC CC 8B FF 55 8B EC 56 8B
75 08 83 FE F4 72 18 83 FE F6 77 13 8D 45 08 50
6A 00 56 E8 DD 02 00 00 85 C0 74 03 8B 75 08 56
FF 15 34 10 CC 75 5E 85 C0 7C 05 33 C0 40 EB 08
Strings in the stack:
033DF414 77E14880 -> TCF
033DF454 72C6DE28 -> KERNEL32.DLL
033DF680 033DFAF8 -> Ui2
033DF868 72FF8914 -> com.apple.CFSocket.private
Call Stack (Method 1):
033DFD54 72F4E24C CoreFoundation.dll!CFDataGetBytes+0x60
033DFD68 00000018
033DFE3C 5D00015C
Call Stack (Method 2):
033DF85C 75CCC41F KERNELBASE.dll!RaiseException+0x58
033DFA28 77D43C94 ntdll.dll!RtlImageNtHeader+0xb10
033DFA2C 77D43CC3 ntdll.dll!RtlImageNtHeader+0xb3f
033DFAF4 77D871D5 ntdll.dll!WinSqmSetIfMaxDWORD+0x31
033DFAFC 77D3E38C ntdll.dll!RtlInitUnicodeString+0x164
033DFB70 77D3E023 ntdll.dll!RtlFreeHeap+0x7e
033DFB88 77D3E0F2 ntdll.dll!RtlAllocateHeap+0xac
033DFB90 75ED11E0 kernel32.dll!TlsGetValue
033DFBB0 76EA2E4D WS2_32.dll!htons+0xc2
033DFBC0 76EA6AD6 WS2_32.dll!__WSAFDIsSet+0x4c
033DFBD4 77D2F89C ntdll.dll!NtWaitForSingleObject
033DFBE8 77D2F8B1 ntdll.dll!NtWaitForSingleObject+0x15
033DFBEC 75166F0F mswsock.dll+0x6f0f
033DFC2C 75166D30 mswsock.dll+0x6d30
033DFCAC 77D2FE36 ntdll.dll!NtDuplicateObject+0x12
033DFCC0 75164200 mswsock.dll+0x4200
033DFCE8 7516432A mswsock.dll+0x432a
033DFD00 76EA2F7D WS2_32.dll!WahReferenceContextByHandle+0x5d
033DFD08 75182F27 mswsock.dll!s_perror+0x1343
033DFD18 76EA6A28 WS2_32.dll!select+0x9f
033DFD58 72F4E24C CoreFoundation.dll!CFDataGetBytes+0x60
033DFD88 76EC3912 WS2_32.dll!WahWriteLSPEvent+0x2ad
033DFD98 72F7560B CoreFoundation.dll!CFSocketGetDefaultNameRegistryPortNumber+0x863
033DFDC0 77D438BE ntdll.dll!RtlImageNtHeader+0x73a
033DFDC8 77D4389A ntdll.dll!RtlImageNtHeader+0x716
033DFEB0 77D43492 ntdll.dll!RtlImageNtHeader+0x30e
033DFED0 75ED14DD kernel32.dll!HeapFree+0x14
033DFEE4 730D4C39 MSVCR80.dll!free+0xcd
033DFEF0 730D4C58 MSVCR80.dll!free+0xec
033DFF08 731613D8 MSVCR80.dll!__badioinfo+0x40
033DFF10 730D2C78 MSVCR80.dll!__set_flsgetvalue+0xd
033DFF24 72F97A05 CoreFoundation.dll!CFHashBytes+0x113
033DFF30 730D29BB MSVCR80.dll!_endthreadex+0x3b
033DFF58 730D8CED MSVCR80.dll!__dllonexit+0x9d
033DFF68 730D2A47 MSVCR80.dll!_endthreadex+0xc7
033DFF70 75ED33AA kernel32.dll!BaseThreadInitThunk+0x12
033DFF7C 77D49EF2 ntdll.dll!RtlInitializeExceptionChain+0x63
033DFFBC 77D49EC5 ntdll.dll!RtlInitializeExceptionChain+0x36
033DFFC0 730D29E1 MSVCR80.dll!_endthreadex+0x61

BSOD in Windows 7 x64 Nvidia Graphics Driver problem Is there a solution

Help me!!! This looks familiar =)
I have just came out of the multiple BSOD in windows 7 and have been on the BSOD Microsoft Boat for about 2 weeks.
Stats:
Asus MotherBoard, amd fx 8core processor, nvidia graphics card, 650watt power supply
This is crap an has to stop, Is there any help.
NVLDDMKM.sys is obviosly the culprate ...

So I disabled the driver using the right mouse click on the computer icon in the start menu yeah the Icons are huge but as long as I dont get the BSOD I can live with that thankx
lol
Once again its on!!! lol
Please start by updating NVLDDMKM.sys driver. You can also report that to NVIDIA Technical Support.
If this does not help, proceed like that:
Update all possible drivers
Uninstall all unused programs
Run chkdsk /r /f and sfc /scannow
Perform a clean boot: http://support.microsoft.com/kb/929135
Disable temporary all security softwares you have
Run memtest86+ to check your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support for assistance
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer

Tried to use my two airport express to extend my wifi network on a windows pc but no success

Tried to use my two airport express to extend my wifi network on a windows pc but no success

My two airport express base stations are 802.11n and i am triying to use them extend my wireless network which is using a D link wirless router as supplied my my ISP connected to TalkTalk network.
Unless the D-Link wireless router has Ethernet ports for each of the 802.11n AirPort Express Base Stations (AXn) to connect to, they will NOT be able to extend the wireless range of the D-Link.
Instead, when directly connected and reconfigured for a roaming network, these base stations CAN extend the range.
Please check out this Apple Support article on how to use AirPorts to extend a wireless network.
The key is to have both AXns configured as follows:
As a bridge.
Each having a unique Base Station Name.
Both using the same Network Name (or SSID), wireless security type and password as the D-Link.
Each AXn to use a channel at least 3-5 channels apart both from each other and that of the D-Link.

ITunes 9.1 (64-bit) causing BSOD crashes with Windows 7

I installed iTunes 9.1 (64-bit) this evening and my computer running Windows 7 (64-bit) repeatedly experienced the blue screen of death (BSOD). The computer would restart in safe mode. Upon restart, the BSOD would occur again within a few minutes.
iTunes was successfully installed and was operable up until the blue screen.
I completed a system restore and my system is stable once again. However, certain iTunes files were removed and now iTunes will not function.
Does anyone have a link to an iTunes 9.0.3 for Windows 7 (64-bit)?
Has anyone experienced a similar problem and have a solution that allows 9.1 to work without crashing my machine?

FF,
I had the exact same problem. I upgraded iTunes to 9.1 and it caused a BSOD. I booted into Windows Safe Mode (Hit F8 as soon as you see the Windows start up screen) and disabled the itunes services. Rebooted and the system is now working. I'm not sure what the deal is with the iTunes 9.1 but it definately breaks Windows 7.

ITUNES downloads from store causing BSOD windows stop error- Please Help!

Hi everyone,
maybe someone can help me out or knows how to fix this problem.
Problem in detail:
This problem started since I updated to the latest version of itunes 7 to download video for my ipod video 30gb. Itunes worked perfect on my computer before updating as I used it with an ipod mini.
I was able to use my new IPOD 30gb fine and transfer all my music to it correctly.
The main problem occurrs when downloading anything from itunes store...1st noticed this when my podcasts were updating and downloading and then the system suddenly crashed with the windows blue screen error message and had to reboot. This happened multiple times so I disabled the automatic downloads of podcasts. Itunes then works fine when not downloading anything.
I then tried purchasing a TV show, whole series, and when it began downloading, the Exact same Error and Blue screen will occur--Very Frustrating.
I uninstalled ITUNES and Quicktime, and then reinstalled them via the latest download from itunes. The same errors still occur.
When windows reboots and sends error report to Microsoft, it states the error is due to a Driver error of which the specific driver is not known.
I have called apple/itunes support and spoke with them and they could not figure out the problem and said I should check with my computers cust service and/or microsoft as it was probably something on this end...I did this and they stated the problem must be something with itunes and especially since all other programs run fine on my system.
SO basically I am going in circles trying to figure this out so I am hoping someone here may know how to fix this problem.
Not only that, but I tried the same on my desktop as I figured I could at least download my podcasts and purchases to my desktop and then transfer to my ipod from there(as I am mainly using my labtop for my ipod) and updated my desktop to itunes 7 latest version,, and figured it would work on my desktop with same operating system----but it Caused the SAME error BSOD as my labtop and in same fashion....only when downloading from itunes.
ANy help is much appreciated as I got the ipod video mainly because of ITUNES video content and podcasts and if I cannot use these major functions on ITUNES than This Was a Complete Waste for me to get the Video IPOD.
Hope there is a way to fix
Thanks

I afraid can’t help much with this, but no one else
has answered. It does seem very odd that two
different computers have the same problem. It makes
you wonder about the content you were trying to
download. As a matter of interest was the
installation for both computers done from the same
download file?
When your computer dies, can you read the stop
message or does it disappear, if it does, go to
Control Panel>System>Advanced
Click Settings in Start Up and Recovery and make sure
that Automatically Restart is no checked.
You should be able to get a stop number from the blue
screen and you may also be able to identify the
filename of a driver, which could give a clue to the
problem.
The Microsoft Website has a certain amount of help on
specific stop messages, you can search for the number
of the stop message which will be something like
0x0000000A.
There is also some help on troubleshooting stop
messages here:
http://aumha.org/win5/kbestop.htm
Thanks for your reply.
As far as the content being downloaded from itunes---consisted of different podcasts and also on a separate occasion-the tv show Heroes complete season on ITUNES..So I would guess the error has nothing to do with the content being downloaded.
The ITUNES installation for both computers was from the same itunes download file on this website on apples itunes free download.
I did not write down the most recent stop numbers and no drivers seemed to be named on the blue screen from what I could tell, but I guess I could be missing something...
From a previous crash with the BSOD- the error message listed was this: STOP: 0x00000050 (0xbad0b158, 0x00000000, 0x8056ea22, 00000002)
not sure if this helps maybe figure out the cause of this or not.
Maybe this will help get to the bottom of this.
Thanks

BSOD with Windows 8.1 Pro 64 bit

I'm having a strange problem here, I had been experincing daily BSODs, so i figured perhaps my windows install got corrupted, and did a full format/Reinstall. I seem to still be getting BSODs however, so i dug into the dump files, and discovered, its saying Skype is responsible. I am running Skype Desktop 7.2 and I do NOT have a HP Fixed Webcam or any webcam, as i've seen as the common culprit around these fourms.
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff802ddb6102c, Address of the instruction which caused the bugcheck
Arg3: ffffd000221a9d90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!KxWaitForLockOwnerShipWithIrql+14
fffff802`ddb6102c 48890a mov qword ptr [rdx],rcx
CONTEXT: ffffd000221a9d90 -- (.cxr 0xffffd000221a9d90;r)
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd000221aa810
rdx=0000800000000000 rsi=ffffe001ce7ff080 rdi=ffffd000221aa810
rip=fffff802ddb6102c rsp=ffffd000221aa7c0 rbp=0000000000000001
r8=ffffd000221aa860 r9=0000000000000000 r10=fffff901400020f8
r11=fffff9014519c228 r12=0000000000000000 r13=0000000000000000
r14=0000000000010001 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KxWaitForLockOwnerShipWithIrql+0x14:
fffff802`ddb6102c 48890a mov qword ptr [rdx],rcx ds:002b:00008000`00000000=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd000221aa810
rdx=0000800000000000 rsi=ffffe001ce7ff080 rdi=ffffd000221aa810
rip=fffff802ddb6102c rsp=ffffd000221aa7c0 rbp=0000000000000001
r8=ffffd000221aa860 r9=0000000000000000 r10=fffff901400020f8
r11=fffff9014519c228 r12=0000000000000000 r13=0000000000000000
r14=0000000000010001 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KxWaitForLockOwnerShipWithIrql+0x14:
fffff802`ddb6102c 48890a mov qword ptr [rdx],rcx ds:002b:00008000`00000000=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: Skype.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
LAST_CONTROL_TRANSFER: from fffff802ddafe668 to fffff802ddb6102c
STACK_TEXT:
ffffd000`221aa7c0 fffff802`ddafe668 : ffffe001`cff817e0 fffff901`4519c005 00000000`00000001 fffff802`ddaf2e16 : nt!KxWaitForLockOwnerShipWithIrql+0x14
ffffd000`221aa7f0 fffff802`ddafd37b : 00000000`80000002 ffffe001`cff817e0 00000000`00000000 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x218
ffffd000`221aa860 fffff960`001f71fc : ffffe001`cff817e0 00000000`00000000 00000000`00000000 00000000`7f3ad000 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x1b
ffffd000`221aa890 fffff960`002c8f80 : 00000000`80000002 ffffe001`cff817e0 00000000`00000000 00000000`00000000 : win32k!EngAcquireSemaphore+0x1c
ffffd000`221aa8c0 fffff960`002c8f56 : 00000000`00000000 ffffd000`221aa9e0 00000000`00000000 fffff960`001f5e5d : win32k!GreAcquireHmgrSemaphore+0x10
ffffd000`221aa900 fffff960`001ffbce : 00000000`00000000 00000000`00000000 00000000`80000012 00000000`0000177c : win32k!MLOCKFAST::MLOCKFAST+0xe
ffffd000`221aa930 fffff960`002017f9 : 00000000`000021e4 00000000`00000000 00000000`5401177c 00000000`00000000 : win32k!HmgDecProcessHandleCount+0x1e
ffffd000`221aa960 fffff960`001d5487 : fffff901`402333a0 00000000`80000012 00000000`00000001 fffff901`00000001 : win32k!GreSetDCOwnerEx+0x413
ffffd000`221aaa00 fffff960`002000c6 : 00000000`00000000 ffffd000`221aab00 00000000`5401177c 00000000`7f3ad000 : win32k!ReleaseCacheDC+0x107
ffffd000`221aaa40 fffff802`ddbe31b3 : ffffe001`ce7ff080 ffffd000`00000014 00000000`7f3af000 00000000`00000000 : win32k!NtUserCallOneParam+0xe6
ffffd000`221aaa80 00000000`77ce59ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03e5e218 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ce59ea
FOLLOWUP_IP:
win32k!EngAcquireSemaphore+1c
fffff960`001f71fc 4883c420 add rsp,20h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!EngAcquireSemaphore+1c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54ee5a22
IMAGE_VERSION: 6.3.9600.17694
STACK_COMMAND: .cxr 0xffffd000221a9d90 ; kb
BUCKET_ID_FUNC_OFFSET: 1c
FAILURE_BUCKET_ID: 0x3B_win32k!EngAcquireSemaphore
BUCKET_ID: 0x3B_win32k!EngAcquireSemaphore
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x3b_win32k!engacquiresemaphore
FAILURE_ID_HASH: {91ce18ba-878a-ee79-a2df-29f0d12dd984}
Followup: MachineOwner
Now I don't pretend to understand what all that means, but it says skype specifically, so its the only clue i have right now.
Thanks for any help.

Please, run the DirectX diagnostics tool.
Go to Windows Start and in the Run box type dxdiag.exe and press the OK button. This will start the DirectX diagnostics program. Run this diagnostics and save the results to a file. Please, attach this file to your post.
Be aware that you will have to zip this file before attaching it here.

Windows crashing - random BSOD on Windows 7 64-bit

Hello
I tried reading this forum and tried IMO everything but computer still gets BSOD. I'm including Dump File. I don't know how to read it. Any advice?
http://sdrv.ms/1gwJEKq
What I did:
memtest86 - passed
ccleaner
regcleaner
antivirus scan
reinstalled drivers
chkdsk
I have mirrored drives on windows. It shows 'resynching'. Could it be failing and causing the problem?

Mindau
This one crash was Related to the
nvvad64v.sys NVIDIA Virtual Audio Driver from NVIDIA Corporation I would install the newest driver available.
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\013114-22495-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`03467000 PsLoadedModuleList = 0xfffff800`036a3e70
Debug session time: Fri Jan 31 05:39:43.583 2014 (UTC - 5:00)
System Uptime: 0 days 0:00:28.095
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck D1, {10, 2, 0, fffff880044f8689}
*** WARNING: Unable to verify timestamp for nvvad64v.sys
*** ERROR: Module load completed but symbols could not be loaded for nvvad64v.sys
Probably caused by : nvvad64v.sys ( nvvad64v+1689 )
Followup: MachineOwner
8: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880044f8689, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370e0e0
GetUlongFromAddress: unable to read from fffff8000370e198
0000000000000010 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
nvvad64v+1689
fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: audiodg.exe
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME: fffff8800eb894c0 -- (.trap 0xfffff8800eb894c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80179a6fd0
rdx=0000000000003fdc rsi=0000000000000000 rdi=0000000000000000
rip=fffff880044f8689 rsp=fffff8800eb89650 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffffa80179a6fd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvvad64v+0x1689:
fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h] ds:00000000`00000010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800034d5de9 to fffff800034d6880
STACK_TEXT:
fffff880`0eb89378 fffff800`034d5de9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0eb89380 fffff800`034d4a60 : 00000000`00000000 00000000`0000100c fffffa80`1611a260 fffff880`035e61c0 : nt!KiBugCheckDispatch+0x69
fffff880`0eb894c0 fffff880`044f8689 : 00000000`0031c8d3 fffffa80`179a4000 00000000`00000000 fffff800`03665888 : nt!KiPageFault+0x260
fffff880`0eb89650 00000000`0031c8d3 : fffffa80`179a4000 00000000`00000000 fffff800`03665888 00000000`00000028 : nvvad64v+0x1689
fffff880`0eb89658 fffffa80`179a4000 : 00000000`00000000 fffff800`03665888 00000000`00000028 00000000`00524fbc : 0x31c8d3
fffff880`0eb89660 00000000`00000000 : fffff800`03665888 00000000`00000028 00000000`00524fbc 00000000`00002fbc : 0xfffffa80`179a4000
STACK_COMMAND: kb
FOLLOWUP_IP:
nvvad64v+1689
fffff880`044f8689 488b4810 mov rcx,qword ptr [rax+10h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvvad64v+1689
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvvad64v
IMAGE_NAME: nvvad64v.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 529fb649
FAILURE_BUCKET_ID: X64_0xD1_nvvad64v+1689
BUCKET_ID: X64_0xD1_nvvad64v+1689
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xd1_nvvad64v+1689
FAILURE_ID_HASH: {58ea0214-7b27-7dc6-5a00-c215a7e166cc}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

A665-S5170 WiFi Not Working After Windows 7 32 Bit Install

I had to put a new hard drive in my A665-S5170. Since there were drivers listed for Windows 7 32 bit for this computer, I installed a copy of Windows 7 Ultimate 32 bit that I owned. After installing every driver listed, I have no wifi. Another forum I was reading suggested it was because someone with the identical problem had not installed a driver for their chipset, and there is no chipset driver listed, but there is one for the 64 bit version.
When I look at Device Manager, I see the "!" by "network controller."
Any suggestions?

Satellite A665-S5170
Downloads here.
It was apparently not intended to run 32-bit Windows on that model. But probably this driver works.
   Intel WiMax/WiFi for Windows 7 (32), 14.1.1.3.1
   wlan-intel-win7-32-141131.zip
..and there is no chipset driver listed
The chipset software is here.
   Intel Turbo Boost Technology Driver
-Jerry

Wifi causing BSOD on Windows 7 64 bit

Similar Messages

Maybe you are looking for