Screen freezing/blanking when coming out of sleep

Hi,
Wonder if someone can help.
I have a iMac (20-inch Mid 2007), that's been running fine up till about a year ago.
Now sometimes when you take it out of sleep, one of the following will happen:
- Screen will come on, then just go blank.
or
- Screen will come on, screen freezes but the cursor will still move around, but nothing will be selectable.
With both you can hear the hard drive and fans still spinning. The only way to bring it back is to completely power it off, and on. But sometimes after doing this, after signing in again, it my freeze or blank out again.
When the iMac is on, its normally ok, but if after bringing out of sleep you try and open things, it can then go blank or freeze as above. But when Its been on for 5 minutes its fine and runs fine for hours or even days if you leave it on.
It doesn't always happen, many times when you turn it on, its fine, just getting more and more...
I have upgraded to latest OS and recently upgraded the 250gb internal hard drive to 1TB drive, I cleaned the fans out while doing this, but again issues remain.
Can anyone suggest what could be causing this? I would be fixing it myself, as its out of warranty and more than capable of doing a full strip down.
Thanks
ShaiboyUK

anyone help?

Similar Messages

Macbook Air screen stayed black when coming out of sleep

I put my MBA on sleep earlier today. When I came back to wake it up, the screen stayed black (but somehow backlit). I had to close the top and open it back again in order to wake it properly. Anyone knows what happened? Should I worry about this? Maybe it's nothing and I'm overreacting, but I had so many issues with my last laptop (not an Apple product though) that I kinda became crazy about my computers.
My Macbook Air is two weeks old. It's a 11 inches running Maverick 10.9.5 and every software is updated.
Thanks!

Having something like that happen just once is no reason to be concerned. I’ve seen it happen - it isn’t common and it doesn’t necessarily mean anything is wrong. Being hyper sensitive about a new computer is normal, especially after experiencing the kind of disaster it sounds like you did with your previous computer.

Why does my MAC sometimes crash when coming out of sleep mode?

My mac freezea sometimes when coming out of sleep mode, and occasionally the screen will go black. At other times I will be using the MAC and it will just freeze. The only way to get out of it is to kill power and reboot. It seems to be happening more frequently.
It was suggested that I fix permissions and start in sleep mode. This has helped in the past, and I am going to do it again now. I also recently upgraded to 10.6.8, and after that the crashes were fewer, but now they are increasing again.
I am including a log of the recent crash a few minutes ago.
12/23/11 11:41:02 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:02 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:02 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:03 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:03 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:03 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:03 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:04 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:04 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:15 AM com.apple.launchd.peruser.501[94] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
12/23/11 11:41:23 AM com.apple.launchd.peruser.501[94] (com.apple.Kerberos.renew.plist[116]) Exited with exit code: 1
12/23/11 11:41:34 AM com.apple.WindowServer[71] Fri Dec 23 11:41:34 Macintosh.local WindowServer[71] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
12/23/11 11:41:50 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:50 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:50 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
12/23/11 11:41:50 AM com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory

Okay thanks, but I am a newbie who is not a very tech kind of a person. The only periphals I have are a kodak camera dock, a Canon 310 copier/fax/scanner and a pair of altec speakers. How do I determine if they all have drivers for my MAC? They all seem to work okay, if that is a sign, though the Kodak camera Dock is a bit slow. How also do I determine if they are Apple energy compatible? With each of these peripherals, do I simply disconnect them from my MAC one at a time to see if there improvement?

Recently having problem with flickering on monitor (viewsonic vg2436wm). When coming out of sleep mode. The screen goes gray, sometime out. Have to press power button to get screen on. Problem stops.

Recently having problem with flickering on monitor (viewsonic vg2436wm). When coming out of sleep mode. It will flicker, the screen goes gray, sometime out. Have to press power button to get screen on. Problem stops. Getting more frequent. After sometime problem stops. My system is a Mac Mini 2010, 2.4 intel core 2 duo, 2 GB, running OSX10.8.5

See if it's related to this...
The 2012 macs (and later apparently) not waking normally from sleep after hours being in sleep. (noted here ...
http://www.xlr8yourmac.com/archives/feb13/022813.html#2012macswontwake
"Why 2012 iMac/2012 Mac Mini won't Wake After Hours of Sleep (Hibernates/Powers Off)")
The sleepimage file still reappears even if never slept. Delete it (hibernate off, etc) - within minutes its back.
A note on that here - http://www.xlr8yourmac.com/feedback/Chameleon_SSD_Optimizer.html
About iMac sleep...
http://forums.macrumors.com/showthread.php?t=1529750
Try this: "sudo pmset autopoweroff 0" and "sudo pmset standby 0"
http://xlr8yourmac.com/archives/sep13/091313.html#10.8.5SleepEjectTip

Why does my Mac Pro open to a fuzzy screen when coming out of sleep mode?

Why does my Mac Pro open to a static-filled screen when coming out of sleep mode?

But does it then come fully awake? My MB Pro comes on with out of focus screen as if in a fog but once it comes awake it clears up, there is a progress bar at the bottom showing the progress from sleep

E9220y hangs when coming out of sleep mode

My new HP Elite e9220y hangs when coming out of sleep mode- When I 'touch a key' or move mouse, power switch on computer turns from yellow to blue, but monitor remains black. Have to force off, and restart. Adjusted power management to 'never' sleep but I was hoping for a more elegant solution.

Quote
Originally posted by southmike
but i would try the settings i used in my psu/sleep thread.
https://forum-en.msi.com/index.php?threadid=43603&sid=
it fixed my hang problems and even got my lights to sleep properly
Southmike, I'm glad I could help you out. When I tried using the settings you stated, it didn't help me resume from standby. However, I did finally get standby to work by first resetting the BIOS to default, and then setting the Power Management to:
ACPI Standby: S3
Call VGA BIOS (no idea what this is): Enable
USB Wakeup: Enable
Power Management/APM: Disable
And, I also disabled a few other things I dont use like onboard Audio and RAID and voila, now WinXP can go into standby and resume from it piece of cake.

MacBook freezing when coming out of sleep mode

Several times now my computer has completely frozen just after it comes out of sleep mode, and I've had to manually shut it down using the power button. Is anyone else having this problem?

I bought two Macbooks; 2.4 Ghz, one was directly purchased from Apple with 4GB RAM; the other one was standard equipped with 2GB, but shop swapped it to 4GB total.
The last Macbook has exactly same problem as you all describe. Most of the times when you open the lid, the Macbook doesn't wake up from sleep. Screen remains black, though keyboard backlit turns on.
Computer hangs completely; and need to perform hard-power-down. Indeed also power LED is not pulsating during sleep; or stops doing it after a while.
I've tried to reset the SMC as suggested in other threads, but it didn't help. Has anybody already gone to Apple about this and got this resolved? I'm not sure whether it's the memory upgrade of the shop, as the other Macbook that came with 4GB seems not have this problem anymore (I had it only once on the first day). Not sure whether RAM upgrade is problem, because while running the Macbook it works perfectly and is completely stable.

Screen goes black when coming out of screen saver. HP Pavilion,p7-1414 desktop, windows 8

the monitor shows the windows 8 screen with the apps, then the screen saver will come on. Then when I try to bring it out of the screen saver mode the screen goes black and nothing I do will get it to go back to the windows 8 screen. Then the mouse pointer will disappear. So I end up having to shut down the computer using the power button. If I have the screen set up for the old style windows 7 and it goes into the screen saver and I bring it back there's no problem.
fleamarketlady

Hello fleamarketlady,
Your computer goes black when it comes out of sleep mode some times.
Make sure that you are only using one cable to connect the monitor to the computer.
Open up command prompt and run the following command SFC /scannow.
This will scan the system files and correct any errors that it can.
Here is a link to command prompt.
When you go to open command prompt, right click and run as administrator.
If you are still having the problem you can perform a system refresh.
This will uninstall windows 8 and reinstall it without affecting your personal information.
Here is a link that will walk you through the steps for a refresh.
Let me know how everything goes.
Have a good day.

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?

Windows BDOS When Coming Out of Sleep

Hey guys, so I recently updated to Windows 8.1, and now when I come out of Sleep Mode, my computer gets a BSOD
I havent been able to figure out why yet though but heres the minidump of the crash report
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
Machine Name:
Kernel base = 0xfffff800`23087000 PsLoadedModuleList = 0xfffff800`23351350
Debug session time: Tue Oct 28 19:43:01.041 2014 (UTC - 4:00)
System Uptime: 0 days 6:39:11.844
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe000541e6060, ffffd00068a06930, ffffe00053c7f880}
Probably caused by : pci.sys
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000541e6060, Physical Device Object of the stack
Arg3: ffffd00068a06930, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe00053c7f880, The blocked IRP
Debugging Details:
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4
MODULE_NAME: pci
FAULTING_MODULE: fffff8014cb89000 pci
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFD00068A0DFB0
STACK_TEXT:
ffffd000`68a068f8 fffff800`23283586 : 00000000`0000009f 00000000`00000003 ffffe000`541e6060 ffffd000`68a06930 : nt!KeBugCheckEx
ffffd000`68a06900 fffff800`232834a6 : ffffe000`545b9f00 ffffe000`535c8060 ffffe000`545b9f40 fffff800`230cd190 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`68a06960 fffff800`230c9760 : 00000000`00000000 ffffd000`68a06ab0 ffffe000`545b9f38 fffff800`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`68a069b0 fffff800`231de7ea : ffffd000`63b99180 ffffd000`63b99180 ffffd000`63ba53c0 ffffe000`550b9880 : nt!KiRetireDpcList+0x4f0
ffffd000`68a06c60 00000000`00000000 : ffffd000`68a07000 ffffd000`68a01000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_iaStorA_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_iaStorA_IMAGE_pci.sys
Followup: MachineOwner
Any help would be appreciated. Thanks guys

IMB
This was Related to iaStorA.sys Intel Matrix Storage Manager driver from Intel Corp. I would remove the current one and install the newest available driver (do not reboot)
If you continue to crash I would remove Symantec.
Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\102814-45187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
Machine Name:
Kernel base = 0xfffff800`23087000 PsLoadedModuleList = 0xfffff800`23351350
Debug session time: Tue Oct 28 19:43:01.041 2014 (UTC - 4:00)
System Uptime: 0 days 6:39:11.844
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe000541e6060, ffffd00068a06930, ffffe00053c7f880}
Probably caused by : pci.sys
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000541e6060, Physical Device Object of the stack
Arg3: ffffd00068a06930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00053c7f880, The blocked IRP
Debugging Details:
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4
MODULE_NAME: pci
FAULTING_MODULE: fffff8014cb89000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
DPC_STACK_BASE: FFFFD00068A0DFB0
STACK_TEXT:
ffffd000`68a068f8 fffff800`23283586 : 00000000`0000009f 00000000`00000003 ffffe000`541e6060 ffffd000`68a06930 : nt!KeBugCheckEx
ffffd000`68a06900 fffff800`232834a6 : ffffe000`545b9f00 ffffe000`535c8060 ffffe000`545b9f40 fffff800`230cd190 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`68a06960 fffff800`230c9760 : 00000000`00000000 ffffd000`68a06ab0 ffffe000`545b9f38 fffff800`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`68a069b0 fffff800`231de7ea : ffffd000`63b99180 ffffd000`63b99180 ffffd000`63ba53c0 ffffe000`550b9880 : nt!KiRetireDpcList+0x4f0
ffffd000`68a06c60 00000000`00000000 : ffffd000`68a07000 ffffd000`68a01000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.17238
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_iaStorA_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_POWER_DOWN_iaStorA_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_iastora_image_pci.sys
FAILURE_ID_HASH: {7d15649d-af9d-aeb2-1222-6fa8a2b3c912}
Followup: MachineOwner
2: kd> !irp ffffe00053c7f880
Irp is active with 4 stacks 3 is current (= 0xffffe00053c7f9e0)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 16, 0] 0 0 ffffe000541e6060 00000000 fffff8014ce0a4c8-00000000
\Driver\pci storport!RaidAdapterPowerUpDeviceCompletion
Args: 00000000 00000000 00000000 00000002
>[ 16, 2] 0 e1 ffffe00055200050 00000000 fffff800231a4fd8-ffffe000545b9f00 Success Error Cancel pending
Unable to load image \SystemRoot\System32\drivers\iaStorA.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
\Driver\iaStorA nt!PopRequestCompletion
Args: 00041100 00000001 00000001 00000002
[ 0, 0] 0 0 00000000 00000000 00000000-ffffe000545b9f00
Args: 00000000 00000000 00000000 00000000
Wanikiya and Dyami--Team Zigzag

IMac doesnt always reconnect when coming out of sleep mode

I have newly converted from pc to mac. I have a new iMac 20" with the Intel Core 2 Duo processor and the new Airport Extreme Base Station. The only problem I seem to have is when my system comes out of sleep mode, it does not always reconnect to the base station. The only option I can see is to turn off the airport on my computer then turn it back on. Is there some other setting or another fix for this? Thanks!
iMac Mac OS X (10.4.9)

Hi Applehave posted a fix for this. I had the same problem on my Macbook.
Go to System prefs>network
Choose Airport in the show field
Under the airport tab choose by default,join preferred network
Any wireless connection listed using WPA or WPA2 security remove using the - option.
change the By default, join option back to Automatic
Re-connect to your router this will add it back into the list and you will reconnect automatically after sleep.
It fixed my problem

Only 1 of my 2 Thunderbolt displays restarts when coming out of sleep mode now that I have installed Mavericks

My setup:
Early 2011 Macbook pro
2 Thunderbolt monitors: one monitor connected to the macbook pro, the second monitor connected to the back of the first monitor
Everything worked great until I installed Mavericks. Since installing Mavericks, when my laptop comes out of sleep mode only the monitor that is connected to the macbook wakes up. The second monitor does not wake up.
In order to get the second monitor to wake up I have to either unplug the thunderbolt connection from the back of the first monitor and plug it in again or unplug the first monitor's thunderbolt connection from the macbook and then plug it in again.
I've tried changing the order of the monitors that are connected to the macbook and rebooting the machine as well. Nothing works. Help?

Okay thanks, but I am a newbie who is not a very tech kind of a person. The only periphals I have are a kodak camera dock, a Canon 310 copier/fax/scanner and a pair of altec speakers. How do I determine if they all have drivers for my MAC? They all seem to work okay, if that is a sign, though the Kodak camera Dock is a bit slow. How also do I determine if they are Apple energy compatible? With each of these peripherals, do I simply disconnect them from my MAC one at a time to see if there improvement?

Z77A-GD65 - Intel Network Adapter disabled when coming out of sleep mode

Just put together a new system with a Z77A-GD65 motherboard, Core i7 3770, and Corsair Vengeance RAM.
Installed the Windows 8 RTM (final release) version, which installs flawlessly and works fine. (Yes, I have an early license to Win8).
Here's the problem. If the system goes to sleep, when it comes back out of sleep mode, the Intel Network Adapter stops working. (Hence, all network and internet connectivity is off). This is evident by the Network Status icon in the explorer task tray showing a red "X". Any attempt to run the troubleshooter results in the message "The Intel 82579LM Gigabit Network Connection adapters is experiencing driver or hardware problems". Screenshots and log files can be found on my Skydrive here: h t t p : //sdrv.ms/NVBatL
The driver version of the NIC, is what Windows installed during setup, is from Intel, version 12.0.150.0 dated 2/29/2012. (It was installed with Windows 8 by default).
Rebooting the machine fixes the problem. For now, setting the Windows power settings to never sleep is my current workaround. I tried downloading and installing some software and driver packages from Intel that I thought might update the driver, but it did not work.
I am assuming this issue will not be present if I put on Windows 7, but that's what I was really hoping to avoid. Suggestions? Newer Intel driver available?

Quote
I don't know why you think this workaround "defeats the the object of having power saving features". That might be a fair point if this was a laptop relying on battery charge. But "sleep" doesn't mean "zero power". It means just enough power to keep the memory alive and some LEDs blinking.
In the case of a desktop build, keeping the LAN adapter awake is a non-issue. Several hundred watts of power are being consumed when the PC is on. When it goes to sleep, that power usage drops down just a handful of watts. If the workaround means having to dedicate an extra watt of power to the LAN adapter, then so be it.
I am not trying to discourage what you did. I have found many a work around to niggly bugs over the years. All I am trying to state is that this bug should be fixed, i.e. the LAN should wake up together with the PC. At the moment it works for you, which is great, and you reported it. Nothing more you can do.
As for the power saving. Yes of course we are talking about negligible consumption here, but the principle is that all these new machines have to comply with EuP2013 which dictates a maximum power usage for the total system when being in a sleep state. This can obviously not be achieved when one has to keep components powered because of a bug.
I would be interested to know what ME firmware version you have on your machine. I myself have had irritating intermittent issues with the Intel LAN on the same board as you in terms of the LAN remaining dead after start up whenever I change HW or do firmware updates. It then takes a restart to get the LAN active again.
Intel has released two IME updates over the last month and there is a recent update for the Ethernet controller as well. I updated both and am monitoring. Since the update I have not had any further issues, but its still early days and I am reluctant to say it solved the issue.

Hi fan speed when coming out of sleep

Hello Everyone,
I've had my iMAC Core Duo for a week now and I've noticed that when I power up the iMAC from shutdown the fans are almost completely silent. After I put the iMAC to sleep for a while 1 hour or so and wake it up the fans kick into high speed and don't slow down at all (lots of noise). I've tried reseting the SMU (unplug the mac, wait 30 seconds and plug it back in while holding down the power button.), no luck. I also tried reseting the NVRAM and deleting the powermanagement.plist. No luck. Anyone else having the same issue? If so have you found a fix or work around?
Thanks,
Rem

Looks like I've been able to narrow this down. I have a second monitor attached to the iMAC in extended desktop mode. If I remove the mini DVI connector to the second monitor and put the iMAC to sleep and wake it up a while later the fans start up go fast and within a few seconds slow right down to an level barely audible. Put the Mini DVI back in put it to sleep bring it out of sleep and the fans kick in full and stay on. Anyone else having this issue?

Network Issues When Coming Out of Sleep

I purchased a 13-inch Macbook Pro about a month ago. I'm running OSX 10.6.4.
Last night I started experiencing issues. Whenever I close my laptop, it goes to sleep fine. However, when I open it to begin using it again, it's unable to find my wireless network. It searches for a while, and then tells me my Airport is off. When I go to turn it on, the button will either not do anything, or the laptop will lock up and I'll need to hold down power to get it off, back on, then working again.
Usually after a restart everything is fine again, however I have experienced a few random lock ups since this all began.
Thanks for your time! Any help would be awesome.

Welcome to Apple Discussions
Not sure if this is what's causing the issue but checking/adjusting this won't hurt.
Open System Preferences/Network and select your normal/home location
In the left hand column make sure Airport is at the top of the list and delete the other items listed that aren't used (you can drag items around to change order and use - to remove)
Then click the Advanced button and in the window that pops open click the Airport Tab
In Preferred Networks delete everything but your home network name
Click "Remember networks this computer has joined"
Uncheck "Disconnect when logging out"
Click OK to close that window
Click Apply bottom left then close the panel
Fingers crossed it should now see and join your home network on waking, sometimes it can take 30 seconds or so for me ...

Screen freezing/blanking when coming out of sleep

Similar Messages

Maybe you are looking for