Strange pop up - blue screen of death?

Twice this week, while logged into Me.com, my screen gets a shadow over it like it's powering down and I get a pop-up that says I need to restart my computer. I can get no response from my mouse, etc. and have done hard boots to restart. I am concerned this is a virus or something else wrong, similar to the blue screen of death on a PC???
Has anyone else seen this? Any idea what is causing it? The pop up has the warning in 3 other languages below the one in English. Not recognizable and no error codes or anything to even identify.
Help????

Sounds like a kernel panic
[read here|http://www.dslreports.com/faq/4970]
[Apple docs: What's a kernel panic? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=106227]
[Topic : kmosx: Kernel Panics? Don't panic too!|http://discussions.apple.com/thread.jspa?threadID=121923]
[X-Lab: Resolving Kernel Panics|http://www.thexlab.com/faqs/kernelpanics.html]

Similar Messages

PSC 2355 Blue Screen of Death - Error:0x889ff020

I'd sure like to resolve this issue and get my favorite printer/scanner/copier running again.
The printer used to be attached to an HP laptop with Windows XP SP3. I moved it over to my HP desktop Windows 7 computer to do some scanning. It worked fine. Then when I moved it back to the Windows XP computer, it worked fine. The XP computer and this PSC 2355 which now has issues sat for several months without being used. When I turned on the XP laptop and printer, the small display screen on the printer was strange and garbled looking. I uninstalled the printer software on the XP laptop, restarted, and downloaded the appropriate drivers and software from HP. When I installed the fresh copy of the software and followed all the installation instructions, the printer worked for awhile. Then the next day, it went back to the garbled looking small display screen, and then it gave me the Blue Screen of Death.
I wondered if the BSOD was showing up because it's one of the printers involved in the lawsuit over the printer cartridges causing lots of pop-ups and apparently other issues. So to "reset" the printer, I popped out the ink cartridges and reinstalled them. That didn't work.
Can this printer be saved, or is it fit for the scrap heap?

P.S. I tried swapping out the power cord that attaches to the transformer and goes into the outlet yesterday. The printer sat at the blue screen of death. In frustration I left the room for about an hour, when I came back and hit the On button, the printer acted normal and worked. I turned the power off last night with the button.
Today I went to turn it on, the swapped out power cord was still plugged into the transformer and the wall, but it doesn't work now. The power light blinked green for a little bit, then went out. Now the HP invent screen is displayed and the power light is off. Hitting the power button on the printer doesn't do anything - the HP invent screen on the printer stays illuminated. Could the problem be the power button itself? Could the problem be the transformer and/or cable running from the transformer into the printer? I think the problem is most likely with the power, but I'm running out of ideas.

Error 13 = Blue Screen of Death?

Thought I'd try this board and see if anyone knows anything about 'error 13' and Panther.
I have been plagued by this error message which pops up whenever I try to print from either of my printers or burn a CD. This all happened after I tried to load a demo version of Adobe Illustrator CS2.
Over the last day I have tried the following:
* deleted the apple.com.print preferences
* reset the PRAM
* unplugged, unpowered and restarted the printers and their USB connections
* deleted the printers from the print setup utility and tried to reinstall them (but there too I get the 'error 13' message. Printers won't load but they do show up as if they loaded. Just won't work, that's all.
* tried logging in as a new user, and then the printer message is "Not enough RAM" to print.
* repaired the disk permissions from the CD
Generally I've done everything I can think of... except to reload the OS, which I hesitate to do because I have to first load Jaguar, then the Panther update, then the other updates. Last time I tried that things didn't quite work out.
I do have an external backup drive, which also got corrupted as I tried loading the Adobe Illustrator CS2 on that disk too. Dumb I know...
So... anyone know what 'error 13' means?
Is 'error 13' the Mac equivalent of the Windows Blue Screen of Death?
Thanks for any input...

Hello Pawel,
I have looked over the service request you mentioned about acquiring 2 PCIe-6537 at 20MHz sampling rate on all 32 lines. In order to narrow down this issue, I think it would be best to try only acquire from both cards without doing any triggerring etc. Also when performing this test, I would only want to acquire from 8 channels on both cards to see if this reproduces it. If this works, we can slowly add more elements to narrow down what the issue is and make us more effective to solve the problem.
I also wanted to ask if you have tried this setup on another machine and if it worked.
Along with this, have you tried to create two Digital Tasks in MAX and try to acquire for the same amount of time to see if the issue reoccurs here? This would tell us if this problem is connected to the driver/computer or LabVIEW.
Jim St
National Instruments
RF Product Support Engineer

Windows Vista Crashing When Ipod is Plugged In. Blue Screen of Death?

A week ago, my computer suddenly started to reboot whenever I plugged my 5th generation 80 gig Ipod in to sync. A blue screen will pop up, and automatically restart.
I do not believe this is the blue screen of death that appeared 2 months ago. I have upgraded to Itunes 8.0.1 when it was first released, and I had no problems until a week ago. I haven't heard of anyone receiving the blue screen of death since the update to Itunes 8 was released.
I have also lost all of my music from my Ipod, so I am anxious to figure this out.
Here is what the blue screen (certain passages paraphrased, the specifics were copied directly):
A problem has been detected and windows has shut down to prevent damage to your computer.
BADPOOLHEADER
If this is the firs time you've seen this stop error screen, restart yoru computer. If this screen appears again, follow these steps:
Make sure all hardware and software is properly installed
If it continues, disable/remove any newly installed hardware and software. Disable BIOS memory options such as caching or shawoding. If you need to use safe mode to remove or disable components, restart your computer, press F8 for Advanced Sartup options, then select safe mode.
Technical information:
*STOR: 0x00000019 (0x00000020, 0xB7C4CE50, 0Xb7C4CE68, 0x0A030203)
/end blue screen
Any help you have would be greatly appreciated!

Have you tried the troubleshooting advice in this article?
http://support.apple.com/kb/TS1502
Was a file name mentioned in the stop message? usually something.sys That can be a clue to the problem is the Apple advice doesn't help.

Blue Screen of Death When Plugging in Ipod Touch 4g

Hello,
Im reciving blue screen of death when I plug in my ipod touch 4g. I have updated itunes, Drivers, This happens every time and I suspect it happens when my computer says found new hardware reconizing the ipod as a camera because once I pluged my ipod in and it didn't pop up found camera hardware and it worked. So does anyone know how to fix this or disable my comp from reconizing the ipod as a camera? Thanks in advance
p.s im using XP service pack 3

have u tried pluging an other usb (eg mp3 or mem stick) it to ur compuer? is it doing it with these?
if its only doing this with ur ipod try the following
1 go to start menu and in the search box type in usb
look for device manager
2. open the disk drives and plug in ipod touch and removeable disk should show up
3, try usb drives updates
because the ipod has a camera most older computers running xp think its a camera,
if u have and usb mem stick copy ur itunes folder on to it and copy it to a computer running vista or windows 7 and c it its doing it on one of them, if its doing it on one them there may be other hardware isues with ur ipod touch

Blue Screen Of Death in AE

Recently I rebuilt my PC to handle after effects a little better. I am running CS3 on windows XP 64 bit, however once I start working on a project for less than 30 minutes my system locks up and brings up the blue screen of death. It gives me a "Page_Fault_in_Nonpaged_Area" error. I ran several memory tests (all passed) and even messed with the page filing with no luck.
The strange part is that when I switch over to my dual boot (windows vista 32bit), after effects works fine. Just not as fast. I reformatted twice with no prevail. I am really out of options here. If anyone can please offer some help i would really appreciate it. THANKS
Specs
Graphics Card: Radeon HD 3870
Processor: Intel Core 2 Quad Q9450
Ram: 2 X 2GB = 4GB
Motherboard: Gigabyte S-series Ep45-Ds3R

Well, not sure, what actually the error is. If it's a "Could not allocate memory for textures", you could try to increase the RAM usage for OpenGL in AE's preferences (Advanced button on the OpenGL page). However, AE is pretty stubborn in recognizing this, so it may not do anything. For most other errors, you will have to deal with the graphics card driver's settings on a manual basis, meaning you will have to create a custom setup. That is however beyond what this forum can provide, as it would require to know the exact current setup and driver options... What you definitely can do is check the overall video RAM allocation, meaning how much of it is already used in the initial config. This will give you a clue about how much is left for applications. I'd also completely turn off antialiasing. As I remember it, most ATI cards have the bad habit of having it enabled by default. This might also free up resources. The rest is in the dark. There certainly are ways to toy around with the front and back buffers and drawing delays, but as I said - without actually seeing what's going on, this is not going anywhere. And don't worry about your RAM and page file swelling - this is normal behavior and should not touch upon your other issues. Remember: Each and every frame you render, if only for previewing, will be stored in your RAM as long as this is possible. Windows in turn will park more memory pages in the swap file to compensate, hence the simultanous growth of both graphs.
Mylenium

Blue Screen Of Death on iPhone plugin: NOT caused by Logitech or HP

Hi,
Like many posters who have posted throughout 2009, my Windows XP computer crashes consistently every time I plug in my new iPhone. I am currently totally unable to use iTunes to connect to the iPhone.
I have spent more than 8 hours trying ALL the causes listed on Apple's website. It is NOT those. I do not have a Logitech Camera or an HP Scanner or anything else listed there. Below you can see a complete list of what I have and what I have tried.
It is very clear from other posts that Apple's usbaapl.sys driver still has bugs/conflicts that Apple has not yet identified. Let's get to work figuring out what the problem is!
I would appreciate any suggestions or pointers from other members, but please do review the details below before you post.
I am technical and would be happy to provide further info or try suggested registry changes, drivers, etc.
Details:
Every time I plug in my iPhone 3G, my Windows XP Desktop computer Blue-Screens in the Apple-provided usbaapl.sys driver (which is installed by the iTunes Apple Mobile Device Support installer component) within seconds, whilst Windows Plug and Play is loading the "Apple Mobile Devices" driver. Windows plug-and-play never makes it to the "imaging device" device. It crashes within 0-5 seconds of plugging in the device.
The same iPhone can successfully work with iTunes on my friend's Windows XP system, so the problem is not with my iPhone; it is with the Apple iTunes software.
There is some problem with interaction between iTunes on my Windows XP computer and my iPhone.
I have iTunes 8.2.1.6 with Windows XP sp3.
I have already tried ALL of the suggestions at:
http://support.apple.com/kb/TS2280
http://support.apple.com/kb/TS1502
In particular
- I do not have a Logitech camera, either built-in or plug-in.
- I unplugged AND uninstalled all the drivers for
- my printer (which is a Canon i560)
- my scanner (which is Canon CanoScan LIDE 25)
- my USB hub/card reader (IOGEAR GUH284R)
- my webcam (Creative Webcam Pro)
- I actually unplugged ALL USB devices first, including the mouse and the USB hub, rebooted, and it still blue-screens when plugging in the iPhone directly to the computer's USB port.
- I used to have an HP PrecisionScan Pro, and so I also uninstalled all drivers for all old hardware (not just the HP scanner), and rebooted. Still blue-screens when plugging in the iPhone.
- I have tried all USB ports of the computer, including directly plugging into them without any USB hub. Still blue-screens.
- I completely uninstalled iTunes, QuickTime, and Apple Mobile Device Support, rebooted, verified that usbaaap.sys was gone from system32/drivers, then reinstalled iTunes 8.2.1.6 -- still blue-screens
- When I re-installed iTunes, I had disabled my computer's firewall and anti-virus as an Apple tech had suggested, but this didn't help -- still blue-screens.
- I also tried the hack, suggested on the internet, of installing Apple Mobile Device Support from iTunes 7.7.1 on top of iTunes/QuickTime version 8.2.1.6. I verified that I was in fact getting a different usbaapl.sys but -- still blue screens.
- I verified that if I delete the usbaapl.sys driver, plugging in the iPhone does not blue-screen (though of course I cannot use it either). The blue screen of death that appears also contains the word usbaapl.sys. The crash is definitely in that driver. I understand that Apple and Logitech say the "real problem" is in another driver, but as mentioned above, I have eliminated everything on the list in Apple's support suggestion, and I still blue-screen. I even blue-screen with Apple's version 7.7.1 usbaapl.sys driver.
- I verified that my PC has the latest chipset drivers and USB 2.0 drivers. My PC has a 2.8 GHz P4 processor with an ABIT BD7II-RAID motherboard. It has an Intel 845E chipset with Intel 82801DB (ICH4) I/O USB controller. I have never had any other problems like this with any other USB device on this computer. My problem is unique to iPhone.
- I saw on the internet that in 2007 there was an iTunes blue-screen crash that resulted if the iPhone had any Photos on it. So I deleted all the photos on my iPhone. Still blue-screens.

lsemprini wrote:
Yes, as mentioned in the OP, it says usbaapl.sys on the blue screen, and removing the driver avoids the bluescreen (but of course also prevents the iPhone from working with iTunes). Interestingly, when removing the usbaapl.sys driver, the imaging side of the device actually works with my computer (i.e., I can get the Photos stored, which comes via an alternate driver interface). The problem is REALLY isolated just to the Apple iTunes interlink code in usbaapl.sys.
I'd like to emphasize and clarify this point a little more as I think it may be the key symptom for separating my problem (and that of other posters, I'd imagine) from the "standard Logitech conflict" problem:
With the bug I am reporting, I plug in the iPhone, and Windows pops up a plug-and-play bubble for "Apple Mobile Device USB Driver," which is usbaapl.sys (you can verify this with 100% certainty by searching for usbaapl in regedit). The blue screen occurs for me during this phase (sometimes an instant after the bubble pops up)!
If I disable usbaapl.sys by removing the driver, Windows gets past "Apple Mobile Device USB Driver" (happily failing to report any error even though it has not loaded the driver, sigh) and goes on to an "imaging" device (I think it might have said "iPhone camera" or "Imaging Device;" I can check again if it's important), which succeeds to load, and I can access pictures stored on the iPhone using the standard Windows Scanner and Camera Wizard tool, which I think uses the WIA API.
So my bug differs from the "standard Logitech conflict" in that it has NO relation to whether or not I have Photos on the iPhone, and if I disable the buggy usbaapl.sys driver, I AM able to access photos on the PC.
In most of the bug reports I saw for the "standard Logitech conflict" problem, users only experienced crashes when the camera had one or more Photos on it, and it appears (though other bug reports are not clear) that the system crashes just after Windows attempts to load the "imaging" driver for the iPhone. My guess is that those users got through "Apple Mobile Device USB Driver" with no problem and crashed on the "imaging" driver.
Can someone at apple please post an engineering bug on this issue?
That way we can get a list of technical questions from the engineers that need answering so that we can really stomp this bug for good. I can also volunteer to try out debugging versions of the drivers and collect log files, if needed. I am a systems software engr with Windoze experience so I can probably help expedite the debugging process.
I want to get this fixed and I'm sure many posters do also!

Satellite A105-S4284 gets Blue Screen of Death when coming out of standby

MySatellite A105-S4284 runnings Windows XP gets a BSOD after coming out of standby or hibernation. With standby, I'll see the login screen where I enter my password, and then it may show the desktop background or even the open app (Outlook or Word, typically) for a second, afterwhich the BSOC appears. For weeks I was getting a black screen sporadically after standby. Researched the problem and saw recommendations to update BIOS. So I updated the BIOS to the latest version, and then I started getting blue screens of death rather than a black screen. Thought the problem was McAfee, because I'd get crashes right after McAfee became active in the background, sometimes without going into standby. Cancelled McAfee, took it off with the cleaner, used Avast instead, and that seemed to help. But then BSODs came back. I uninstalled non-essential software, clearned registry with CC Cleaner, freed up more HD space and defragged, ran SpyBot, etc - but I still get the BSOD almost every time I go into standby or hibernate.
The stop messages on the BSOD don't show a driver. and all begin with 0x0000007E (0x000000C5, ... and then differ after that. One recent one followed with 0x804E13D5, 0xAA6B9B8C, 0xAA6B9888). Does that mean anything?
I've installed Microsoft's debugging tools to look at the dumps after a BSOD. Here is output for two recent crashes. Doesn't point to a driver. NTKRMLMP.exe is what crashes - do I need to replace that from the I386 folder somehow? I did have my Matsu**bleep**a DVD-CD drive suddenly quit a time or two until the computer was restarted. Should I reinstall the DVD driver? Or the graphics driver? Worried that I might break something by doing that.
Loading Dump File [C:\WINDOWS\Minidump\Mini030809-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sun Mar 8 16:05:07.187 2009 (GMT-5)
System Uptime: 0 days 4:22:53.890
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
BugCheck 1000007E, {c0000005, 804e13d5, a9860b8c, a9860888}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+7a9 )
Followup: MachineOwner<snip>
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. <SNIP>
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804e13d5, The address that the exception occurred at
Arg3: a9860b8c, Exception Record Address
Arg4: a9860888, Context Record Address
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!IopfCallDriver+2d
804e13d5 ff548638        call    dword ptr [esi+eax*4+38h]
EXCEPTION_RECORD: a9860b8c -- (.exr 0xffffffffa9860b8c)
ExceptionAddress: 804e13d5 (nt!IopfCallDriver+0x0000002d)
   ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000070
Attempt to read from address 00000070
CONTEXT: a9860888 -- (.cxr 0xffffffffa9860888)
eax=0000000e ebx=00000001 ecx=87546020 edx=853fe1a0 esi=00000000 edi=f772471c
eip=804e13d5 esp=a9860c54 ebp=a9860ca0 iopl=0         nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000             efl=00010292
nt!IopfCallDriver+0x2d:
804e13d5 ff548638        call    dword ptr [esi+eax*4+38h] ds:0023:00000070=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000070
READ_ADDRESS: 00000070
FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+7a9
805517b9 e9e4feffff      jmp     nt!ExAllocatePoolWithTag+0x7bf (805516a2)
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 804e13d9 to 804e13d5
STACK_TEXT:
a9860c6c 804e13d9 8753d018 853fe1a0 00000000 nt!IopfCallDriver+0x2d
a9860ccc 805517b9 00000000 00000002 00000000 nt!IopfCallDriver+0x31
a9860dac 80575723 a9f4533c 00000000 00000000 nt!ExAllocatePoolWithTag+0x7a9
a9860ddc 804ec6d9 f7720ce2 a9f4533c 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!ExAllocatePoolWithTag+7a9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48a4044a
STACK_COMMAND: .cxr 0xffffffffa9860888 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+7a9
BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+7a9
Followup: MachineOwner
0: kd> lmvm nt
start    end        module name
804d7000 806ff000   nt       # (pdb symbols)          c:\symbols\ntkrnlmp.pdb\B883868B88CB415A92EC010CF6A115A52\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\symbols\ntkrnlmp.exe\48A4044A228000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Thu Aug 14 05:09:14 2008 (48A4044A)
    CheckSum:         0021B760
    ImageSize:        00228000
    File version:     5.1.2600.5657
    Product version: 5.1.2600.5657
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0401.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   5.1.2600.5657
    FileVersion:      5.1.2600.5657 (xpsp_sp3_gdr.080814-1236)

In safe mode it is not possible to standby. That is disabled. Tried to make it possible with Toshiba's power control service, but it is not available.
In a new account, the BSOD still occurs. I created a new account, logged out of my account, and went to the new one. Tried standby. It came out of standby for a second and then had the blue screen of death.
In checking the event manager, I seen errors shortly before crashes sometimes that involve the CD.
So I went to Toshiba.com and downloaded the DVD RAM driver and ran it, reinstalling the driver, and then restarted. I also saw that there was C-Dilla driver in my drivers. I uninstalled the SafeCast program that I think is associated with C-Dilla, moved the C-Dilla driver out of the drivers to a distant folder, unchecked C-Dilla in MSCONFIG so it won't load (it was still there after removing SafeCast), and then reinstarted. So with a new DVD Ram driver and neutering, I hope, of C-Dilla, I tried things again and the system appeared to be crash free - better than it had been. But then a crash occurred - BSOD - and upon restart, the CD locked up, and crashed again.
After restarting, there was a new dialog that popped up after Windows launched indicating that there had been an error with SONIC DLA. Before the crash, there was an event n the event viewer:
My last error comes from the Plug and Play Manager:
The device 'MAT**bleep**A DVD-RAM UJ-841S' (IDE\CdRomMAT**bleep**A_DVD-RAM_UJ-841S________________1.60____\5&226f6cf2&0&0.0.0) disappeared from the system without first being prepared for removal.
Hmmm. So things are still vulnerable. Any ideas? Buy new CD drive? Or new computer?

Blue Screen of Death when syncing with iTunes. Please HELP!

I have noticed a few others experiencing this problem as well.
http://www.everythingiphone.com/forum/windows-pc-and-iphone/blue-screen-error-wh en-i-plug-the-phone-into-my-xp-laptop-3038.html
Aside from the (don't use windows XP comments), does anyone have any information on this? I have emailed Apple a couple times but have gotten no answer back yet.
What is happening is that when I plug in my iphone to itunes a "Digital Still Camera" pops up in the system tray and then blue screen of death appears. Some people have said that all you have to do is delete all your photos and it will sync, but does anyone have any other suggestions without having to delete all my photos anytime I want to sync?
Thanks for the help in advance.

The first response was correct, the computer (xps 1210) used a logitech camera driver that I did not recognize so I deleted it. The software was still active and crashed the computer. Fix was reinstall logitech software and driver. Updating the driver would have probably worked. Thank you!

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 - solution

I think I found a problem to the infamous Blue Screen of Death problem that many of us XP users (particularly Dell laptop users) are having...the problem that happens when you take a photo on your iPhone, plug it in, and it gets recognized as a "Digital Still Camera" and then boom! BSOD. Sound familiar?
Go to Start > Control Panel > Add or Remove Programs
Find the Logitech Camera Driver and uninstall it.
This did the trick for me. Finally -- I had tried all kinds of other things. After I did this, the iPhone still got recognized as a "Digital Still Camera," but no BSOD. What happened instead was that another balloon popped up that said "Your hardware is installed and ready to be used." It then synced with iTunes as usual.
The next time I took a picture on my iPhone and plugged it in, it brought up a list of Camera/Photo programs (Canon Capture, Picasa, etc.) for me to choose from, but again, no problems with syncing to iTunes.
Hope this helps. This work for anyone else?
Dell Inspiron 9300 Windows XP SP2

I had all of the same problems as you describe and my Dell also has a Logitech Camera built into it.
My solution was to upgrade the Logitech driver to the latest version from Dell support (Drivers & Downloads). The latest driver is v10.5.1.1125 dated 02/08/07.
After upgrading the driver, when I docked my iPhone, I got the "Digital Still Camera" and thankfully, NO BSOD, but like you, received "Your hardware is installed and ready to be used." In Device Manager under Imaging devices, I now see "Apple iPhone #18" (don't know what the 18 stands for).
See driver detail list below:
C:\WINDOWS\system32\DRIVERS\LVMVDrv.sys
C:\WINDOWS\system32\dirvers\usbscan.sys
C:\WINDOWS\system32\ptpusb.dll
C:\WINDOWS\system32\ptpusd.dll
Provider: Logitech Inc.
File version: 10.5.1.1125
iTunes sync'd up and also there was a prompt list of camera/photo programs to choose from, and being a user of Kodak EasyShare software, I choose this and checked the box "Always use this program." EasyShare was then launched and allowed me to configure for sync/transfer with this software, which I selected.
I can now take pictures on my iPhone, place in dock, sync with iTunes, sync/transfer photos to Kodak EasyShare, and have photos removed from iPhone by EasyShare after the sync/transfer is complete.
Finally, I think, this issue is resolved for me.
Dell M2010 Windows XP Pro

Blue Screen of Death Hangups.. any advice??

Hi, I've recently setup a system with the below configuration, and am getting the blue screen of death at various stages during the intial windows install. These occur at various times, sometimes I get to the copying files stage, sometimes not, but never to any GUI stage. POST seems fine, and the D-bracket gives the all clear, my best guess is a faulty RAM chip, but I would appreciate some advice before going out to purchase replacement parts. (Limited funds)
Current plan was to start with a new RAM chip, though I've read since purchasing that these Corsair chips don't overclock so well, so may consider another brand. Then perhaps a small IDE HDD, though I've managed to get through the formatting stage, and even file copy on occasion, so this seems a little unlikely.
Error codes if they help have been 0x0000004e and 0x0000007e (also an IRQ_LESS_NOT_EQUAL - 0x0000001e (I think?))

I have an MSI NEO2 with very similiar problems I've been having a real hard time troubleshooting. It BSODs often times during boot-up. I went through the obvious things, like RAM, PSU, CPU over heating, etc by substition. Nothing helped. I even swapped hard drives, no dice. So I figure it has to be motherboard. I've updated the firmware to the latest rev. Reset BIOS defaults to fail safe and optimized, still same problem. The really strange thing it only does it during boot. If I can get the OS to load, it's stable. I can run benchmarks, play a game of Doom3, surf the web for hours, no problems. Restart, BSOD. Sometimes it gets so bad I give up and can't use the machine. I have a duel boot system with XP Pro and XP 64-bit. Both OS's have this issue, but the XP Pro more so for some reason. I even tried a dfferent hard drive with an OS which has been stable in another machine for over a year, same problem. I was starting the process of pulling the motherboard for RMA when I realized I still had the firewire port attached via pin connectors, not a plugin. Figuring I could have crossed a data line to a power line or something stupid, I decided it needed more testing before paying shipping for an RMA. I also defraged the hard drive with the 32 bit OS which was badly fragmented for a brand new install for some reason. This seemed to help a lot, but it still BSODs sometimes during boot. I'm just really puzzled. MEMTEST runs fine on the system which also checks L1 and L2 cache on the processor which I thought might be an issue. I would really like to know what is causing this. Even if it is the motherboard, I should be able to figure out what area of the board is having the problem. And if it is a flakey motherboard, while only BSOD during boot? One other note of interest, I uinstalled the nvidia drivers (latest as of 5/6/05) and reinstalled drivers which were supplied with the motherboard. Although I have only rebooted a few times since doing this, it hasn't BSODed since.
Questions I would like to have answered...
Q: Are the latest drivers from NVIDIA ok to use with this MSI board?
Q: Does New Egg sell refurbished junk?
Q: Are MSI motherboard high quality or just a bunch of hype?
Q: Has anyone ever heard of a machine that only BSODs during boot but passes all hardware tests with flying colors?

Blue screen of Death? Tried various things..

Hi..my wife's iBook G4 froze on her yesterday. She then powered of by holding down the power button. Then, she started up again, only to find the Blue screen of Death. When I got home, this is what I found too. I tried to boot from the install disc by holding down the C button but it doesn't give me any options, as it just goes to the blue screen again while I'm holding down the C button. I then connected my MacBook Pro via firewire and mounted her iBook on my desktop..no problem. So I pulled all necessary files off that she wanted and did a Disk Repair on her computer via my MBP. I verified the disc and no problems showed so does that mean there are no repairs to do? I found it strange that it would book fine on my desktop but only give her a blue screen? I also tried to reset PRAM and that didn't do anything. It seemed weird though that even by holding down the C button with disc install 1 inside, that it wouldn't boot from disc either...
The other problem is we bought the iBook brand new 4-5 years ago, but in Korea. So the Hardware Repair disk is in Korean and I can't understand anything. The OTHER problem is that we're in a part of the world where there are no Apple dealers! So no place to take it in to...
Any help?
Thanks!

skills,
I found that if I press down on the computer to the left of the trackpad just 1.5" below the option key, it makes a funny sound, but gets to log in screen.
Hey skills,
Well careful where you press. That pressing to the left of the trackpad was an old recommendation for the G3 iBooks.
What's there in the G4 1Books and that strange noise you hear is the hard drive.
What's in question here is the Graphics Processor Unit or GPU. It's a single chip and since Macs are Graphical User Interface machines these instructions run thru the GPU. Either the GPU is bad or the soldering is coming loose (BGA). When you put pressure on the GPU the problem corrects itself and pretty much confirms that it's a BGA problem.
In the G4 the GPU is pretty much under the option - apple keys depending on the model and size. The GPU sits under a huge heat spreader so pressure is better applied from beneath the GPU. Sometimes it's better if the bottom comes off.
If it is the GPU the logic board will have to come out and be sent off for "reballing". In this procedure there is a definite possibility that the chip will not survive the "operation" and die on the table. There are two places that I'm aware of in the US that does this. I've done a bunch of them. Most get donated to schools in the inner city.
Richard

Ipod crashes windows (blue screen of death)

Hi all. A bit of background info:
A couple of months ago the hard drive crashed on my friends computer. They had to reinstall their OS. Thankfully they had made backups of most everything and were able to get most things reinstalled successfully.
Now they are using a 15g ipod connected through a firewire port on an HP laptop. They do not have a USB adaptor, so gotta go with the FW.
Anyway, when they connect the ipod the computer completely crashes to the blue screen of death and does the physical memory dump. There is an error message, something along the lines of a driver issue.
I know this is vague information, but any pointers on how to proceed in troubleshooting this would be greatly appreciated, thanks
Frost

hi Frostine!
Anyway, when they connect the ipod the computer completely crashes to the blue screen of death and does the physical memory dump. There is an error message, something along the lines of a driver issue.
we can sometimes narrow this down a bit by checking on the numerical and text codes showing up with the blue screen. (ie 0x[zeros/letters/numbers] CAPSANDUNDERSCORES)
here's a reference on the sorts of things i'm checking on:
Troubleshooting Windows Stop Messages
can you get that information for us from their PC?
(if the screen is specifying the file that Windows is crashing on, that would be helpful to know too.)
love, b

Blue Screen of Death When opening iTunes.

I am at a loss. For the past six months I have been trying to figure out why my computer has a blue screen of death and then restarts "nearly" everytime i open iTunes. The "nearly" is what's driving me nuts because every once in a while it will open ONCE and then start crashing again. I don't even do anything to help it open it just miraculously works every now and then. It even craches the comp when starting iTunes in safe mode. The blue screen error says "Page Fault in non-paged area". iTunes worked fine for months before this randomly started happening. I have tried every solution I have seen, even ones that weren't for my problem. So far I have:
Manually uninstalled iTunes and QT and reinstalled the standalone QT then iTunes.
Disabled itunes helper and ipod service before starting.
Disabling all other services and start-up items.
Installed current bios and drivers (as far as I can tell)
Installed current windows installer.
Updated microsoft products including .net
Updated Java runtime environment
Replaced ram
I have a pentium 4 1.6ghz with soyo mobo and a RAID card(mirrior) set-up. 1 gig of pc133 ram. I can ul the minidump if needed.
I figured out how to load my podcasts on my ipod manually but I want to get a video ipod so I need itunes. PLEASE HELP!!
Windows XP

there's a few more things worth checking on. but let's also capture a minidump of the crash and send it to someone who can interpret minidumps.
To set up your machine to capture a minidump, right click on "My Computer", select "Properties", select the "Advanced" tab, select the "Startup and Recovery" Settings button, select "small memory dump" from the popup. When it crashes, look for the MiniDump file. It's usually in the folder "C:\WINDOWS\Minidump" and is called something like Mini<number>-<number>.dmp.
send it to this email address
in the email, put the URL to this discussion thread, so that whoever gets it has some context. Also give as much information about the context of the crash (in the email) as you can.
love, b

Strange pop up - blue screen of death?

Similar Messages

Maybe you are looking for