Windows 2000 "blue screen of death" after a small number of gpib reads - related to gpibclsd.sys

Labview 6i gpib drivers 1.7
If I just keep just reading (I stripped the operations down to "reading" to track this down) from the GPIB instrument (HP3456A) in a FOR loop every 2 seconds
- somewhere after 10<100
reads Windows 2000 crashes with an error related to gpibclsd.sys Seems like some sort of buffer overflow.
This is a bit annoying, as I have just now finaly learned Labview and have it ready to do something for me.
I would say "close but no cigar"...

alas, I have done so.
I deleted the i.7 drivers and started the
installation of NI-488.2.2.1
The setup program hangs on launch but running the individual .msi's got the drivers installed. Although the board is present and working properly according to the device manager - MAX fails to detect the board. When the troubleshooter is run the board can not be sequentially verified - with an unknown hardware error.
I just notice Visual basic gpib access does not work either. I don't know whether its HW or SW at this point.
Thanks for the help though.

Similar Messages

Windows 7 - Blue screen of death after Boot Camp install

Hello! I have done some searches with no answers, so...
After installing Windows 7 from scratch I then install Boot Camp 3.0 which then leads to the Windows blue screen of death upon reboot. I then have to recover Windows to the previous state prior to installing Boot Camp.
Help!?

Most likely, Apple HFS read-only, which is AppleHFS.sys and AppleMNT.sys - rename those and see.
You might want to run chkdsk after all this to make sure there are no errors with the drive and file system.
Windows Explorer will not accept HFS+ filenames with special characters and will "green bar" and hang when it does, too.
The faulty HFS driver is a valid concern.
Rename AppleHFS.sys and AppleMNT.sys
By doing the following you will disable HFS mount / read mode on windows XP, Vista, 7.
Navigate to c:/windows/system32/drivers/AppleMNT.sys, rename the AppleMNT.sys file to something like AppleMNT_keep.sys or something of your likings.
The faulty HFS driver is a valid concern. It seems to happen on many systems.
You find it in Windows/system32/drivers/AppleHFS.sys
Renaming to AppleHFS_disabled.sys will avoid the blue screens until you have found another solution or Apple updates Bootcamp 3
After renaming both myself because they are no longer "*.sys" or something? they are gone. In my case AppleHFS prevented Windows Backup from running to end and was causing error "some files skipped" and while some might find reading convenient, I prefer Windows not have even read-only access.
You can probably do better with MacDrive, or probably Paragon's HFS driver, to read AND write if needed, to HFS from Windows.

Blue Screen of Death after GPIB Software Drivers 2.1 install, nipsbfw.sys, nipalk.sys

I get a blue screen of death after I upgraded the GPIS Software Drivers to 2.1. The screen complains about the following files: nipsbfw.sys and nipalk.sys.
I'll copy down the exact message and post it...

Hello fkwok �
First, make sure GPIB software driver 2.1 is the correct driver for your operating system and board by clicking here.
If you are using Windows 2000, this KnowledgeBase is extremely useful.
If these suggestions do not solve your problem, please post the exact message and I will look into the issue some more. Have a great day!
Becky B.
Applications Engineer
National Instruments
Becky Linton
National Instruments
Field Engineer
Office: 734-464-2463
Cell: 248-709-2822
Email: [email protected]

Qosmio F20 blue screen of death after shutdown

Hi there,
I get the blue screen of death after shutdown on my Qosmio F20 laptop.
Error is IRQ_NOT_LESS_OR_EQUAL.
I assume that it is somehow related to tv tuner card.
I have tried to restore system - no good. After restoration for some time it was OK. But then BSOD appeared again.
Sometimes it also appears when I connect USB HDDs or even when I insert DVD disk.
And for shure everytime I shut laptop down.
Has anybody got ideas?

Hi
Reading you last message I really dont know what you expect from this forum ?:|
We all here can provide only some suggestions and opinions.
Without any notebook tests and checks nobody will be able to provide a magic solution
I hope you understand this.
So back to the notebook issue.
There is a one way to find out if the issue could be related to the software or hardware.
You have to reinstall the notebook with the Toshiba recovery CD. If the same BSOD will appear after the installation from the recovery CD then the chance are that the hardware is faulty!
I think you should check this out.

Blue screen of death after installing Boot Camp on Windows 7

Hello and thanks for the help!
Brnad new user to Boot Camp here. After a new install of Windows 7, I install Boot Camp but then when rebooting Windows I get the blue screen of death. When letting Windows attempt a repair, it fails and I am forced to Recover Windows 7 to a state before I installed Boot Camp.
Help!?

Solution for this problem is simple. You have to apply Mac Book Air SMC Update 1.7 which you can do from Mac OS X with Software Update or you can download required update manually from Apple support site. If you don't use BootCamp and have installed Windows without it, you will have to boot Mac OS X from external drive just to apply required update. After you applied SMC update, you can boot to Windows and apply BootCamp update 3.2 and 3.3.
There is a known problem with Mac Book Air EFI Update 2.3, which you won't be able to apply and it will show in Software Update every time you check for updates. There is no solution for it yet.
You get BSOD if you have BootCamp 3.1 and Windows 7 SP1 installed and you have commited Windows update which will break applemtp.sys as your SMC firmware is too old. It applies to Windows 7 32 bit and 64 bit versions in BootCamp or native install.

Bootcamp Windows 7 Blue Screen of Death on MBPwR

Hello all, I've never needed to use this before but gosh darn it I need some advice, because I can't figure this out...
I'd rate myself a 9 out of 10 in "Windows PC" experience
And maybe a 6 out of 10 with Macs, I'm still new!
I just bought the new Mac Book Pro with Retina Screen in early July, I can't remember the exact date. But it hasn't been thirty days yet, so if you think that's my best bet to try and get an exchange here, let me know.
MC975LL/A
PROBLEM : Mac OSX Lion 10.7 works wonderfully, not a problem in the world, smooth as butter – the issue is Windows. I like to play some games and OSX doesn't play well with some Windows based games so I always install it on Bootcamp. Well, this has been a neverending issue on my new MBPwR because I can't seem to get it to work correctly.
      1. Here's how it started - I installed Windows 7 Ultimate x64 through Bootcamp, via my Superdrive and it ran well for a week or so. After installing a game and some other software (Steam) please take that as a coincidence as I did, I don't think Steam had anything to do with the crash, more likely it was something 'game' related, HDD, RAM, CPU, GPU? The computer started to get the "Blue Screen of Death" that Windows computers get, specifically: page_fault_in_nonpaged_area, I've never seen it before and I've owned a number of Windows computers over the years!
     2. Is this my fault, or something deeper? - I can't figure it out, is this a hardware problem or a software one? I reinstalled Windows 7 yesterday and attempted to try again. Just a chance my installation was messed or something, well it happened literally after five minutes of booting into Windows 7. After it happened the first time I used a memory check and a hard drive check software and both came up flawless. Some online on other boards although Windows based have suggested this error can be caused by the RAM and the CPU or the GPU, even... Is this true? As there is no way to test it, maybe exchanging this computer is the best option?
    3. As as a side note... - Has anyone else had a crawling slow boot into Windows 7? It takes my MBPwR almost five minutes of a top left-hand blinking cursor to actually boot to Windows 7.
So did I have some really, really bad luck here with a new computer? Or is this somehow software related? I can answer any questions if you have them so we can try and figure this out!
Thanks!

Did the Nvidia driver install okay? Some users had to reinsall just the driver from Apple Windows Software Support.
Did Windows DVD not find anything wrong?
Is Windows set to be default boot OS in the control panel for selecting the boot volume?
There probably is a leaning curve and bleeding edge sortof with any new logicboard and setup.
Apple has issued a firmware upgrade for some models - I thought Retina - the MacBook Air has a serious problem under Windows.
Mac will run hotter under Windows. Maybe an error message.
GPU-Z:
http://www.techpowerup.com/downloads/SysInfo/GPU-Z/
AIDA64 Extreme Edition
http://www.aida64.comhttp://www.aida64.com/product/aida64-extreme-edition/overview
CCleaner
http://www.piriform.com/ccleaner
How to view error message:
From Control Panel-> Admin. Tools-> Event Viewer-> Windows logs:
Check Application and System Folders for Red highlit messages. Note that you can right-click clear these log folders.
Memtest
This is a step by step guide with audio and video to explain how to use memtest to see if your memory is defect. Another thing to add is that some errors will not be found on the first pass, best to do at least 3 passes.

Blue Screen of Death After RAW Compatibility Update

My friend updated her 13" Black MacBook yesterday, specifically the "Digital Camera Raw Compatibility Update 2.3". After a reboot, she got the Apple "Blue Screen of Death", with no login window showing. Looking at system.log, there's a section that looks to be the culprit (this began after restarting due to the install of the update):
Nov 7 13:55:29 Philbert /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[31]: Login Window Application Started
Nov 7 13:55:30 Philbert /usr/sbin/ocspd[53]: starting
Nov 7 13:55:35 Philbert kernel[0]: display: Not usable
Nov 7 13:55:35 Philbert com.apple.launchd[1] (com.apple.WindowServer[50]): Exited abnormally: Hangup
Nov 7 13:55:35 Philbert com.apple.launchd[1] (com.apple.WindowServer): Throttling respawn: Will start in 6 seconds
Nov 7 13:55:42 Philbert com.apple.launchd[1] (com.apple.WindowServer[64]): Exited abnormally: Hangup
Nov 7 13:55:42 Philbert com.apple.launchd[1] (com.apple.WindowServer): Throttling respawn: Will start in 10 seconds
Nov 7 13:55:52 Philbert com.apple.launchd[1] (com.apple.WindowServer[67]): Exited abnormally: Hangup
Nov 7 13:55:52 Philbert com.apple.launchd[1] (com.apple.WindowServer): Throttling respawn: Will start in 10 seconds
Nov 7 13:56:02 Philbert com.apple.launchd[1] (com.apple.WindowServer[70]): Exited abnormally: Hangup
Here are some things I've observed/tried, many from sources via the Internet:
- I'm able to login in single-user mode
- I'm not able to login in Safe Mode (hangs on white screen with Apple logo)
- I've tried booting off the 10.5 install DVD and running Disk Utility - verify/repair disk, this comes back ok. However, if I try to verify/repair permissions, it runs for about 10 - 20 mins then freezes. I let the frozen process run overnight (10-12 hours) and no feedback. I can move the mouse, but I cannot select anything.
- When the laptop is booted and on the blue screen, I can connect to it via AFP
- I've tried manually changing the permissions of "/", by doing - chmod 775 /; chmod 1775 /;
- I've tried removing the com.apple.WindowServer.plist and com.apple.loginscreen.plist files in case they were corrupted by the update
- I tried running the "installer" command to re-install the update package from the command line. I run it with the "verbose" flags, I get no output and the process hangs.
Since I can connect via AFP I figure I'll be backing the data up and re-installing OS X. Pretty lame though, considering this failure was caused by running a Software Update. Anyone have a last minute suggestion for me before I go down that path?
I have the full system.log if anyone is curious!
Cheers!

i don't think this is a router issue...i believe it's a hardware issue...this error occured when computer is not getting sufficient memory, drivers are not installed correctly or due to invalid driver installation of any devices installed on the computer...to just isolate the problem try connecting computer directly to the modem and check are you are getting a same error message or not and let me know.

Blue screen of death after ram upgrade on a Toshiba Satellite C655 laptop

I ordered an upgrade for a Toshiba Satellite C655(PSC08U-02D037) running Windows 7 Home Premium 64bit. I've trying for a month to get this to work consistently. When I first installed it, it worked fine for the first few days, but then after that I kept getting an error that would pop up "Display has Stopped Responding And Recovered" and the screen would flicker turn to black for a second. It didn't happen a lot at first, but then it got progressively worse to the point that it would crash my browsers, and sometimes when I tried to play certain videos, I would get the blue screen of death, and then the computer would have to restart.
I updated my bios, graphics drivers, I checked to see if maybe I failed to install it properly and reinstalled it, no avail. Finally I just took the ram out, and then I stopped having these issues. Which leads me to believe that it may have something to do with the memory upgrade. I ran the scanner as suggested when I was looking to upgrade, and what was recommended was a ( System 2gb DDR3-1600 Sodimm 1.35v CL11 ) ram stick part number CT6316802, which is the one I ended up ordering. I'm not sure what else to do but assume that what I ordered is either defective or just doesn't work with my laptop.

Hi jinjoe,
I am sorry for the issues you are experiencing with your upgrade. How is this memory installed? Is it just one module or did you purchase two? Did you install it with any exisitng RAM? If you have two modules have you tried installing one module at a time? This would help us determine if the issue is with one defective memory module or both causing the issue.

Blue Screen of death after BEFW11S4 firmware update.

I just updated my firmware for my BEFW11S4 v.4 router. Now every 5-10 minutes when I am on the internet I will get a blue screen of death containing the error "DRIVER_IRQL_NOT_LESS_OR_EQUAL" I did some searching and really came with no soultion. I just system restored to about a week ago and it did not work. I'm running Windows XP. Any suggestions?
(Edited post for guideline compliance. Thanks!)
Message Edited by JOHNDOE_06 on 07-31-2007 08:16 AM

i don't think this is a router issue...i believe it's a hardware issue...this error occured when computer is not getting sufficient memory, drivers are not installed correctly or due to invalid driver installation of any devices installed on the computer...to just isolate the problem try connecting computer directly to the modem and check are you are getting a same error message or not and let me know.

Blue Screen Of Death after installing Ovi/PC Suite...

Windows Vista, 32-bit, Home Premium, Service Pack 2
Nokia 5530 XpressMusic
Problem: BSOD (Blue Screen of Death) occurs constantly.
I think the problem is the phone drivers (via cable). The program itself shouldn't be it.
I made a system recovery, which worked. And my computer was restored. But when I tried once again the same problem occurred.
So my question is: How can I use the phone with the computer without getting the BSOD?
Thank you

I have posed the question in the Customer Care Center Europe
The automatic answer was (translated from german):
Thanks for your question. The Customer Care will contact you in 48h. This was on the 12.01.11.
Since then no answer.
Hey customers, we should stop buying Nokia phones, because they ignore our problems.

Blue Screen of Death After Trying To Install Windows On Pavilion ze4900?

After my hard drive died in my Pavilion ze4900, I replaced it with another notebook hard drive I had laying around.I also tried installing Windows XP home from a Windows installation CD, the same OS the laptop had before the hard drive died. All went well until the laptop was done loading all the installation files, instead of giving me the option to either install Windows or repair Windows, the laptop ends up showing me a blue screen with the message: " A problem has been detected and windows has been shutdown to prevent damage to your computer." What can I do to resolve this issue? I have installed Windows XP on another computer using the same CD, so the CD hasn't gone corrupt and the replacement hard drive is barely used. Any help would be greatly appreciated!

, Hello and thanks for posting on the HP support forums. The first thing you will want to check is if there are any issues with the hard drive you put in. Run the BIOS diagnostics for the hard drive and the hard ware to make sure there are no issues. HP Notebook PCs - System Diagnostics (F2) And. HP Notebook PCs - Testing a Hard Disk from the BIOS Please let me know how things go. Thanks again for posting and have a great day.

Windows 7 Blue Screen of Death from Apple Wireless Keyboard?

I've installed Windows 7 with Boot Camp 3.0 drivers on my Mac mini, and I suppose overall, I'm enjoying it. However, I'm getting a blue screen that seems almost random. Keyword is almost.
I've got my Apple Wireless Keyboard and Mighty Mouse paired, and they're both working well, however, I do believe I am getting some blue screens from my wireless keyboard.
It seems, at random intervals (usually when I haven't touched the keyboard and mouse for awhile) I get an IRQL blue screen and no information about what's exactly causing it. For example, if I'm sitting in the other room listening to music for awhile, and I come back and press the "next" media button on my keyboard, it'll crash and give me the blue screen. However, I've also tried pressing another random button (shift) to "wake" the keyboard if it had fallen asleep, which also results in a blue screen. The blue screens ONLY show up when I give input via the wireless keyboard. Or, if I leave the computer on overnight to download a file or something, the screen will sleep (which it should) then I'll press a button on the keyboard, the screen will stay asleep, and the computer will restart. Which is just a hidden blue screen I'm assuming.
I've tried reinstalling Windows (Clean/fresh install of course), installing/uninstalling drivers, pairing and re-pairing. I've also removed unnecessary/non-Windows 7 drivers that were installed with Boot Camp.
Outside of this blue screen, I am quite impressed with Windows 7. I just can't figure out what's going on. Is there any place I can get a description of what's causing this crash? Does anyone know what's happening or know a solution to this?
Thanks in advance, if you need more details, please ask.

Experiencing exactly the same symptoms, bugcheck/bluescreen only when touching the Apple wireless keyboard after a period of inactivity.
I have an 20" iMac, just upgraded Leopard -> Snow Leopard latest minor version and updated to Boot Camp 3.1 hoping they provided a fix, but the driver at fault (keymagic.sys) doesn't look updated and the issue is still there
Hopefully someone from Apple dev support is reading this, here's all the info I could squeeze from the crash dump:
=============================================
* Bugcheck Analysis *
IRQLNOT_LESS_OREQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff80002e33440, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e33440, address which referenced memory
Debugging Details:
READ_ADDRESS: fffff80002e33440
CURRENT_IRQL: 2
FAULTING_IP:
nt!IoIsWdmVersionAvailable+0
fffff800`02e33440 80f906 cmp cl,6
CUSTOMERCRASHCOUNT: 1
DEFAULTBUCKETID: VISTADRIVERFAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002f2f0c0 -- (.trap 0xfffff88002f2f0c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f2f100 rbx=0000000000000000 rcx=0000000000000006
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e33440 rsp=fffff88002f2f258 rbp=fffff88002f2f2b0
r8=fffff80002a4f000 r9=0000000000000000 r10=fffffa80027f3010
r11=fffff88002f2f208 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!IoIsWdmVersionAvailable:
fffff800`02e33440 80f906 cmp cl,6
Resetting default scope
LASTCONTROLTRANSFER: from fffff80002ac0469 to fffff80002ac0f00
FAILEDINSTRUCTIONADDRESS:
nt!IoIsWdmVersionAvailable+0
fffff800`02e33440 80f906 cmp cl,6
STACK_TEXT:
fffff880`02f2ef78 fffff800`02ac0469 : 00000000`0000000a fffff800`02e33440 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`02f2ef80 fffff800`02abf0e0 : 00000000`00000000 fffffa80`03375d90 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f2f0c0 fffff800`02e33440 : fffff880`04a02e5d fffffa80`02a3add0 fffffa80`027e8b40 fffffa80`02a3add0 : nt!KiPageFault+0x260
fffff880`02f2f258 fffff880`04a02e5d : fffffa80`02a3add0 fffffa80`027e8b40 fffffa80`02a3add0 0000057f`fd5c5228 : nt!IoIsWdmVersionAvailable
fffff880`02f2f260 fffffa80`02a3add0 : fffffa80`027e8b40 fffffa80`02a3add0 0000057f`fd5c5228 fffff880`04a02dfc : KeyMagic+0x2e5d
fffff880`02f2f268 fffffa80`027e8b40 : fffffa80`02a3add0 0000057f`fd5c5228 fffff880`04a02dfc fffff880`00e5a2a7 : 0xfffffa80`02a3add0
fffff880`02f2f270 fffffa80`02a3add0 : 0000057f`fd5c5228 fffff880`04a02dfc fffff880`00e5a2a7 fffffa80`02a3add0 : 0xfffffa80`027e8b40
fffff880`02f2f278 0000057f`fd5c5228 : fffff880`04a02dfc fffff880`00e5a2a7 fffffa80`02a3add0 00000000`00000000 : 0xfffffa80`02a3add0
fffff880`02f2f280 fffff880`04a02dfc : fffff880`00e5a2a7 fffffa80`02a3add0 00000000`00000000 fffffa80`027fd9d0 : 0x57f`fd5c5228
fffff880`02f2f288 fffff880`00e5a2a7 : fffffa80`02a3add0 00000000`00000000 fffffa80`027fd9d0 00000000`00000010 : KeyMagic+0x2dfc
fffff880`02f2f290 fffff880`00e30c9b : fffffa80`027fd9d0 fffffa80`027fd9d0 fffffa80`027fd9e0 fffffa80`027fdc01 : Wdf01000!FxRequestBase::CompleteSubmitted+0x1f3
fffff880`02f2f310 fffff880`00e30dc4 : 00000000`00000002 fffff880`04bbcff7 00000000`00000000 fffff880`04bbcff7 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff880`02f2f380 fffff800`02aab935 : 0d780da4`0da40dd4 fffff880`02f2f420 0d440d78`0d780da4 fffff880`04bbeb52 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`02f2f3b0 fffff800`02ac3516 : fffffa80`027e8f2b 00000000`00000000 fffffa80`027fdc70 fffffa80`027e8b40 : nt!IopUnloadSafeCompletion+0x55
fffff880`02f2f3e0 fffff880`04b62323 : fffffa80`027e8b40 00000000`00000000 fffffa80`02655c10 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f2f4c0 fffff880`04ba24be : fffff880`02f2f590 fffffa80`027e8b40 00000000`00000000 fffffa80`0294f600 : bthport!BthCompleteRequestEx+0x5b
fffff880`02f2f4f0 fffff880`04b9c8d4 : 00000000`00000000 00000000`00000001 fffffa80`02a50c40 fffff880`02f2f6e0 : bthport!L2Cap_CompleteReadIrpList+0xc2
fffff880`02f2f540 fffff880`04b70732 : fffffa80`03349530 fffffa80`0294f5f0 fffff880`00410001 00000005`00000002 : bthport!L2CapInt_ProcessReadBip+0x430
fffff880`02f2f6d0 fffff880`04b70078 : fffffa80`0267f230 00000000`00000000 fffffa80`029b5402 fffffa80`02670000 : bthport!HCI_ProcessAclReadBip+0x642
fffff880`02f2f7a0 fffff880`04b988d9 : fffffa80`0267f230 fffffa80`03036702 fffffa80`026c0ab0 00000000`00000000 : bthport!HCI_ProcessAclRead+0x214
fffff880`02f2f810 fffff880`04b66201 : 00000000`00000000 00000000`00000000 00000000`00000056 fffffa80`026c0ab0 : bthport!HCI_ProcessMpBip+0x61
fffff880`02f2f880 fffff880`04b4d327 : fffffa80`0294f4f0 fffffa80`026c0ab0 00000000`00000000 fffff800`02ac59fa : bthport!BTHPORT_RecvMpBip+0x41
fffff880`02f2f8d0 fffff880`04b5399f : 00000000`00000000 fffffa80`00cd3910 fffff880`04b56388 fffffa80`00cda820 : BTHUSB!BthUsb_ReadTransferComplete+0xf7
fffff880`02f2f930 fffff880`04b53c31 : 00000000`00000003 fffff880`02f2f9f0 fffffa80`00ca2d00 fffffa80`00000012 : BTHUSB!UsbWrapWorkRoutine+0x17b
fffff880`02f2f9b0 fffff800`02ac3516 : fffffa80`00cd3bdb 00000000`00000000 00000000`00000000 00000000`00000000 : BTHUSB!UsbWrapInterruptReadComplete+0x1dd
fffff880`02f2fa40 fffff880`044135d9 : fffffa80`01e81050 fffffa80`00cda700 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f2fb20 fffff880`04413ab7 : fffffa80`028ef502 fffffa80`00cd3910 00000000`ffffffff fffffa80`01e81ea8 : USBPORT!USBPORTCoreiCompleteDoneTransfer+0xa15
fffff880`02f2fc00 fffff880`0441164f : fffffa80`01e81ea8 fffffa80`01e811a0 fffffa80`01e82040 00000000`00000000 : USBPORT!USBPORTCoreiIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f2fc60 fffff880`04402f89 : fffffa80`01e81050 00000000`00000000 fffffa80`01e81e02 fffffa80`01e81ea8 : USBPORT!USBPORTCore_UsbIocDpcWorker+0xf3
fffff880`02f2fca0 fffff800`02acc5dc : fffff880`02f07180 fffffa80`01e81ea8 fffffa80`01e81ec0 00000000`00000000 : USBPORT!USBPORTXdpcWorker+0x1d9
fffff880`02f2fcd0 fffff800`02ac96fa : fffff880`02f07180 fffff880`02f11f40 00000000`00000000 fffff880`04402db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f2fd80 00000000`00000000 : fffff880`02f30000 fffff880`02f2a000 fffff880`02f2fd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
KeyMagic+2e5d
fffff880`04a02e5d ?? ???
SYMBOLSTACKINDEX: 4
SYMBOL_NAME: KeyMagic+2e5d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: KeyMagic
IMAGE_NAME: KeyMagic.sys
DEBUGFLR_IMAGETIMESTAMP: 49c160ec
FAILUREBUCKETID: X640xA_CODE_AV_BAD_IPKeyMagic+2e5d
BUCKET_ID: X640xA_CODE_AV_BAD_IPKeyMagic+2e5d
Followup: MachineOwner
---------

Skype causes Blue Screen of Death after a while in...

Hello, I'm currently having a problem with my skype where it will cause my computer to BSOD after a while in a call, it's only happening during skype calls, not during other voice communication programs like steam's voice calling and the blue screen is more likely to happen when I'm running Firefox.
The Blue screen error I get is "Clock Interrupt was not receieved on a secondary processor within the alloted time interval."
Any help would be appreciated.
Solved!
Go to Solution.

The issue might be triggered by Skype and other software but definitely not due to Skype. It's a very broad multiple CPU timing's issue that can be caused by several things.
1. Problematic BIOS settings
2. Failing hardware/drivers
3. CPU/Fan/HW monitor control programs
4. Power management settings
As a temporary workaround you can try setting the processor affinity for Skype or set your Windows to boot off only 1 CPU using msconfig.
http://www.addictivetips.com/windows-tips/how-to-set-processor-affinity-to-an-application-in-windows...

Windows gives Blue screen of death when connect ipod

I have an ipod 20g and everytime i connect it to my 2.0 usb windows freezes gives me a blue screen and restarts

same problem here, also with a 20gb ipod. Mine also shuts the PC down on a disconnect of the ipod as well although this is less frequent.
I was using the USB2 ports on the front of my Dell but I've swithed them round now and am using a Firewire port on the back and touch wood it hasn't happened in the 2 days since I switched over.

Hp mini wa545ua#aba windows 7 blue screen of death and won't load operating system

I tryed to run my computer and the blue screen came up and it wouldn't load micosoft help

To enter the BIOS filip the power button and quickly tap the F10 key.
Select the Diagnostics section and run a memory test and a hard disk self test.
Post your results here.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Windows 2000 "blue screen of death" after a small number of gpib reads - related to gpibclsd.sys

Similar Messages

Maybe you are looking for