Re: Qosmio X500 - Monitor fails to turn on after waking from Sleep mode

Hello all,
I have a problem with my Qosmio X500-10T:
After placing it into Sleep mode, upon waking it up again (opening the lid, pressing a key, moving the mouse or pressing the power button) the screen fails to turn on (it could possibly be a black screen, although I doubt it as I cannot really see any traces of the LED backlight). The only way beyond this is rebooting by holding down the power button.
I appreciate any help.

I have a X500-10T, under 4 weeks old. Straight from the box it had the problems with going to sleep/hibernation and the only way to bringit back to life was to remove the battery and follow the reset procedue as instructed by Toshiba technicians. Currently the sleep and hibenation has been disabled, it was unuasble. I have a bluetooth mouse that also is a nightmare, it drops in and out of operation at any time, mostly if left untouched for a while. Some times a reboot brings it back to life whilst at other times it takes 30-40 minutes of switching on and off a number of settings, cant' realy workout what's going on. This unit was supplied with the latest BIOS ver 1.4 so not known any difference.
Technicians aslo did a full re-set bakt to factory defaults, this did not make any difference apard from giving me several hours of work in restalling all my programmes. I am worried as I only have just over 11 months warranty left. I have been advised not to use the fingure print identification system as any protected data will be un recoverable if it goes wrong, I would be interested if any other users have any concerns about this, the reminder to set this is driving me crazy, and apparently it can't be switched off when I asked.Has any one who had thee issues managed to get it sorted. The big question for me is it a BIOS problem, graphic card software issue or a Windows 7 issue.

Similar Messages

  • Qosmio x875-Q7290 BSOD After Waking from Sleep Mode

    When closing the laptop lid and reopening it, I am welcomed with a BSOD.
    On Sun 4/7/2013 6:45:08 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\040713-8923-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0xB8 (0xFFFFFA800D321060, 0xFFFFFA800D310A00, 0x0, 0x0)
    Error: ATTEMPTED_SWITCH_FROM_DPC
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Sun 4/7/2013 5:30:47 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\040713-11544-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
    Bugcheck code: 0xB8 (0xFFFFFA80126C0B50, 0xFFFFF80003664CC0, 0x0, 0x0)
    Error: ATTEMPTED_SWITCH_FROM_DPC
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    When restarting after this happens, I get a different BSOD when trying to load windows (attachments 3+4).
    I then have to go into an option on the laptop boot screen to repair. It says that it cannot find anything to repair and suddenly I am able to go into windows again. I started having this problem later in the evening on April 6th, 2013 I guess. I went to bed and just closed the lid and when I awoke in the morning, I opened it and is was a BSOD. I guess a major change was installed 9 'updated' drivers from the Driver Reviver Program.
    Solved!
    Go to Solution.
    Attachments:
    040713-8923-01.dmp ‏297 KB
    040713-11544-01.dmp ‏295 KB
    2013-04-07 14.47.30.jpg ‏101 KB
    2013-04-07 13.31.26.jpg ‏101 KB

    Thanks for nothin'  
    We don't get much activity here on the weekend.
    If you had got feedback, it would probably be that updating drivers from the device makers (or from Microsoft's Windows update) sometimes causes problems with laptops. It's because OEMs like Toshiba often tweak the chips and consequently the drivers.
    The bottom line is that it's safest to get the new stuff from Toshiba (here). Turns out that they (apparently) update only to fix bugs. So you are sometimes a little behind.
    -Jerry
    Attachments:
    Dumps.txt ‏2 KB

  • Monitor Blanks in and Out When Waking From Sleep

    Since getting my Mac Pro (with Apple installed RAM and NVIDIA GeForce 8800 GT), I've noticed that the screen does not immediately turn on when waking from sleep, as my older Macs did. Rather, it turns on for a split second, goes blank for two seconds, turns on again for a split second, goes off again for a second or more, and then comes on permanently.
    This behavior only occurs when waking from sleep; it does not occur when the monitor turns on from the active screen saver.
    Is this normal for the MAC Pro with an NVIDIA GeForce 8800 GT? I have a HP w2408h monitor with a DVI to HDMI cable. Everything else works fine, including all video behavior.
    Thank you.

    Hm. Bluetooth, interesting. Thanks for the idea.
    I just opened the lid to see about the BT setting and the display didn't go off-on. The BT is off, I'm pretty sure I did that when setting it up as I don't use BT for anything.
    I wasn't suspecting anything was seriously wrong, it's just that quick-on feature was highlighted as a selling point and I was curious about the glitch, if it was a setting I could change, for instance like you've highlighted. Annoying when things don't work as advertised.
    And if I show the machine off to colleagues and friends, that will be a bad first impression they will want explained.

  • I'm new to the MAC world. I turned my computer on from 'sleep' mode, and a window was up stating that the IOS disk was full; asked me to force quit, then it just froze. It's been 2 hours. Help! I'm worried about losing photos/videos of my children. Thx!

    I'm new to the MAC world. I turned my computer on from 'sleep' mode, and a window was up stating that the IOS disk was full; asked me to force quit, then it just froze. It's been 2 hours. Help! I'm worried about losing photos/videos of my children. Im not sure if there's something special I need to do once I turn it back on; in the meantime, its still on... which I'm afraid the picture on the screen will burn into the screen. Does that happen on iMac's? Thx!

    Try a hard reset. ( holding Power til it restarts)
    Once to your desktop. Click the Apple icon >> About this mac >> More info>> Storage
    Once you see what you have the most of. Try to see what you can delete.
    Open up any folder>>all files>> or buy an external to store more data.
    Once deleting make sure you empty your trash.
    If you are new and its a new computer, you might need to bring it to a store for further assistence.
    Coast Guard Mechanic w/ an Apple Problem

  • External Hard Drive Fail After Waking from Sleep

    Hi,
    I've been having this issue for over a year (since upgrading to Lion, and now still persists after upgrading to Mountain Lion), and I haven't been able to find the exact answer I need after searching through the posts here, and on the internet.
    I have a 2011 MBP, and after upgrading to Lion last year, I've noticed that my WD external hard drive for the Mac has issues to be recognized after the laptop wakes from sleep. The drive icons are still there on the desktop, and all the files are listed. However, I cannot open any of the files, and Time Machine backup automatically fails.I am able to eject the drives by dragging the icons into the trash can. However, nothing happens if I simply unplug the fire wire 800 cable and re-plug it into the computer after ejecting the drives. I need to reset the external drive by unplugging both the fire wire cable and the power supply, and replug everything.
    Aside from being a hampering process after waking from sleep, this is also very stressful on the drive itself, so I would like to fix this. Does anyone know the issue behind this or have a solution? Thanks in advance!

    Thanks for this, and apologies for delay in replying...in between seeing your post I backed up the ext hdd to another mac and used the disc utility to erase and repair and then re mounted the ext hdd. OK.  I have then tested the ext hdd being recognised when waking from sleep mode a few times and everything appears to be fine. If this doesn't work (long term) I will follow the instructions as you have suggested....
    I now have a new problem with my HP printer (Photosmart Plus) which is not being recognised by a new wireless router..Ok whilst the router is switch on and I have reconfigured the printer..but when the router is switched off overnight and then switched back on...I get a 'printer is not connected' message and have to go through the re configure routine all over. I am minded to think this is a router problem as the same issue is happening to my wifes Mac Book Pro (which is only a few weeks old)...any suggestions..

  • Mac Mini WiFi (airport) fails after waking from sleep

    I recently bought a Mac Mini (Mid 2010 model)...my first Apple computer since my dearly departed IIe.  I've been having repeated intermittent issues with the WiFi on this machine.
    Owning it for two weeks, then one day it woke from sleep, and decided it no longer knew the password to my wireless network.  With everything else in my house on wireless, I knew that the password had not been changed (I am using WPA2).  Every time I would retype the password, I would get either a 'Connection Timeout' error, or an 'Incorrect Password' error.  Every once in a while it would connect, but it would not get a valid IP.
    Restarted the system, and then it tells me there's 'No Airport Card Installed'
    Reset PMU/SMU/PRAM (etc) and the airport card comes back, but it STILL will not connect.
    I go into keychain, and delete the saved wireless password.
    I create a new 'location'.
    No go.
    So I made a trip with my machine to the Genius bar at my local apple store.  Miracle of miracles, it WORKS PERFECTLY from the moment they turn it on. Get it home, it continues to work perfectly.  This was Saturday.
    This morning, same problem starts again.  I was having similar issues with my iPad not connecting to the WiFi when waking from sleep, but this was fixed when I factory reset the iPad.  I've never experienced this issue with either of my iPod touches (3rd and 4th gen).  I'm not having any wireless problems with my PS3, Wii, Blu-ray player, Android phone, Nook, HP Printer, or Windows laptop. 
    My router is a D-link F5D8235-4 v2000, with firmware 2.01.09 (latest available)

    Hi, this has worked for a few...
    Make a New Location, Using network locations in Mac OS X ...
    http://support.apple.com/kb/HT2712
    10.7 & 10.8…
    System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
    10.5.x/10.6.x/10.7.x instructions...
    System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
    The interface that connects to the Internet should be dragged to the top of the list.
    10.4 instructions...
    Is that Interface dragged to the top of Network>Show:>Network Port Configurations.
    If using Wifi/Airport...
    Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.
    For 10.5/10.6/10.7/10.8, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...
    208.67.222.222
    208.67.220.220
    Click OK.

  • IMac always auto detects for external monitors after waking from sleep or from display off

    I've got a Dell 24" monitor (2408WFP) plugged into my mid 2011 iMac via DVI cord and thunderbolt attachment. Things work fine.
    When I need to leave my computer, I usually turn the displays off using the shortcut keys: CTRL + SHIFT + EJECT
    This works perfectly and both displays go black. However, when I return to my computer and reactivate the iMac, the iMac display will turn blue as if I have just plugged in a new monitor even the external monitor is still plugged in. It usually flashes blue twice before displaying the password prompt. I can usually just log back in as normal. I've never had this happen before using Snow Leopard. It's annoying but strange.
    However, even more strange is that sometimes when returning to the desktop, the iMac will do the auto detect display thing and then when I log back in, the external display just shows static as if there is no signal. I've checked the cable a million times and everything is as tight as tight can be and both ends are plugged in properly. Unplugging the displayport adapter from the iMac and then reattaching it restores the desktop on the secondary display although sometimes, it results in the secondary display showing a gray background picture instead of my normal picture. Replugging the secondary display seems to fix that too although sometimes it doesn't.
    Why is this happening?
    - Problem with the adapter?
    - Problem with the DVI cable I'm using?
    - Compatibility issues with my external monitor?
    I need to stress the point that this has never happened before with Snow Leopard.
    If I am the only one experiencing this then I suppose it may be an issue with the iMac or adapter or even the cable. But if anyone else can shed light on this problem, I'd really appreciate it.

    Hi Micheal,
    I've been experiencing the exact same issue with my new iMac I just bought.  I bought it refurb so I wasn't sure if it was a defect with the hardware or not.  Since I'm not the only one I will asume it's not for now.
    Setup:
    - iMac 27-inch 3.4GHz (Release May 2011)
    - Dell 2709W external monitor
    - Hooked in with mini display port to DVI adapter
    - Lion 10.7.3 all up to date to this day
    From what I've been able to gather the issue presents itself only when my Dell 2709W enters "Power Save Mode" after I do CTRL + SHIFT + EJECT or when the diplays simply goes to sleep by themselves.
    Although if I hit that combination and the displays goes to sleep but I don't wait long enough for my Dell monitor to actually "Power Save Mode" (wait like 2 sec) then touch the keyboard then the 2 displays (iMac and Dell) resumes from sleep without the issue presenting itself.
    I'm tempted to buy the mini-display port to HDMI just to see if the issue is still present with that adapter.  If I do I'll update my post with the outcome.
    If anyone else has any info to help with this issue it would be greatly appreciated.  It's very annoying when you resume from sleep and you find all of your windows that where opened on the external display before sleep squeezed into your main display (iMac).
    Thanks!

  • Mutiple monitor setup not working after waking from sleep

    Mac Mini 2011
    Mavericks (10.9.3)
    Monitor 1 Mini->HDMI Cable->Monitor
    Monitor 2 Mini->Mini Display Port to HDMI Adapter->HDMI Cable->Monitor
    Monitors are not the same size
    Thw adapter is PNY (PNY A-DM-HD-W01)
    Upgraded to Mavericks, second monitor works nicely. However, when waking the system up after it goes to sleep, the second monitor does not turn on. Further, the primary montior blinks every few seconds between the usual display and shrinking the windows to a smaller size. Unplugging the second monitor from the HDMI adapter cable stops the blinking, but connecting it again (even after waiting a few minutes) makes the blinking continue and the second monitor does not wake up. On reboot, all works fine again.

    Hello chacham,
    The article linked below provides some useful troubleshooting steps that can help resolve the issues you're experiencing with your display.
    Apple computers: Troubleshooting issues with video on internal or external displays
    http://support.apple.com/kb/HT1573
    Cheers,
    Allen

  • DNS Lokup fails after waking from sleep

    Since the recent update, whenever my computer wakes from sleep the DNS Lookup fails and I cannot connect to the internet for 30sec-1minute. I've never experienced this problem before. Any thoughts?

    FWIW, I never sleep my machines or their HDs, just their displays and never have an issue waking up the displays, usually run 24/7. Give that a shot.

  • Using Second Monitor Airport Does Not Reconnect Upon Waking from Sleep.

    Using: MBP; OSX v10.6.5; Airport v5.5.2; Menu Bar assigned to second monitor which is a ViewSonic plugged in via mini-display port to HDMI.
    When MBR goes to sleep and wakes upon mouse movement Airport does not re-establish the connection to my network.
    No closing of lid or manually putting MBP to sleep involved. Just leave lid open on MBP and walk away for an hour. Upon return, move mouse, everthing wakes except Airport which shows an exclamation mark in the menu bar for the Airport ICON.
    When using MBP display for the Menu Bar screen Airport wakes OK.
    What's with that behavior???

    I changed channels from AUTO to Ch 11. Was there a specific frequency you had in mind.
    I also closed the lid to the MBP, let things go to sleep, returned to the office, moved the mouse and the Airport came on line on its own.
    I figure there is programmatic problem within either the OS or the Airport coding that prevents Airport re-finding a network with both displays active but the Menu Bar on the secondary screen.

  • "Action Keys" mode turns itself back on after waking from sleep

    Hi gang,
    I've recently bought a Folio 13, and have disabled "Action Keys Mode" in the BIOS so that the function keys work as expected.
    However, if the machine goes into sleep mode, the function keys revert to their default behaviour (that is, I have to hold down "Fn" if I want to hit F5).
    Rebooting the notebook fixes the problem, as the BIOS setting has not changed.
    How can I *permanently* disable "Action Keys Mode" so that it stays disabled even when the notebook goes into sleep mode?
    Cheers,
    Matt

    I had this problem - you can update the BIOS and it will correct the issue. I received a BIOS update via HP Support.

  • System clock fails to update after waking from sleep

    I've noticed that my new PowerMac G5 Dual-Core 2GHz (running Mac OS X 10.4.3) doesn't update its system clock to the current time after waking from sleep.
    When I put it to sleep and then wake it some time later, the Clock in the upper right-hand corner doesn't update to the current time. It still ticks on (second for second) but remains out of sync.
    Opening the Date & Time preferences pane will restore the time to the correct setting.
    This problem only occurs with sleep and then wake-from-sleep. It doesn't happen when I shut down the machine and then restart it.
    Does anybody know if I've got a malfunctioning machine? It's only 1 day old...
    Or better still, how do I solve this problem?
    PowerMac G5 Dual-Core 2GHz   Mac OS X (10.4.3)  

    No, my Mac is not having trouble contacting the time server. I checked the console log and found no messages related to this.
    I am on a broadband always-on connection (recently switched from DSL to cable modem, and the problem occurred under both connections). However, my original post states that the computer loses time only when it is asleep, and I didn't think that my computer could contact the time server when it is asleep. It also loses time when it is off, which I neglected to mention previously. Am I mistaken in thinking that the computer communicates over the network only when it is awake? Since it keeps accurate time when awake (once I've reset it by opening the Date & Time control panel), it seems to me like it IS communicating with the time server without issue.
    [And I apologize for misinterpreting your question as a suggestion. I was trying to be polite by thanking you for taking an interest in my issue. I'll watch my semantics more carefully next time.]
    Cheers,
    Katy
    G5/dual core 2.3 Ghz   Mac OS X (10.4.4)   2.5G RAM

  • 10.5.2 Update - Second monitor "blinks" after wake from sleep

    Posting in the off chance that others have seen this behavior. This seems to be Leopard related, and did not start happening until after I installed the 10.5.2 update.
    After waking from sleep my second monitor will blink on and off for anywhere from 2 seconds to about 30 seconds at which time it functions properly. It does not do this on initial startup OR when booting from my tiger volume (backed up with superDuper before a clean install of Leopard). Unplugging the display and plugging it back in also stops the "blinking"; turning the monitor off and then on has no effect.
    My machine is a early (2007) model 2x2.66 dual-core with 3GB of (Apple) RAM and a GeForce 7300 GT. All firmware updates have been applied and software update reports no updates available.
    The displays are both Sceptre X9G-NagaV 19" flat-panels connected via DVI, though I see the same behavior when using my 20" apple cinema display as second head. (I know these are cheap monitors. Please refrain from telling me that the displays are at fault - it 's not a problem with the display, as this doesn't happen under Tiger. The monitors have performed admirably for over two years)

    Have you tried unplugging the second monitor, rebooting and letting it run without it for a little while, and then plugging it back in to see if it clears some persistent loading problem? My monitor has always gone out on me kinda randomly, but I think it's my GPU in my PMG5 that's losing power and resetting or something so it wouldnt be the same issue (I've gone through two so far with the same results).
    Alternatively, try changing some of the display settings, such as resolution, color, and such to see if the change corrects how it's loading the display.

  • External monitor flashes on and off randomly after wake from sleep

    I have a Mid-2009 13" MacBook Pro 2.26GHz hooked up to a Samsung SyncMaster 2033 External monitor via the MiniDisplayPort-DVI connector.
    After waking from sleep, the external monitor will go blank for a fraction of a second at random intervals (display on the MBP remains normal). The flickering clusters are about minutes apart, while flickers within a cluster (usually 2-3 flickers per cluster) is of order seconds apart. "Detect displays" will not make this go away. The only way I can make it go back to normal is to unplug-and re-plug the MiniDisplayPort connector on the MBP.
    Anyone else got a more elegant solution to this that does not involved wearing down the displayport?

    I tried this.  No change.  However, I did start playing with the Display settings.  Oddly enough, when I change the disfunctioning monitor to 720p it starts working again.  Does this mean anything to anyone? 

  • External monitor initially flashes on waking from sleep

    I recently upgraded to 10.4.8. My PowerBook is connected to an external monitor and now often flashes when I wake the machine from sleep. It takes a while too settle down but then works fine. If I wake from sleep without the external monitor, there are no problems. I had no problems using 10.1. Does anyone have a fix?
    G4 PowerBook (PowerBook6,1)   Mac OS X (10.4.8)   867 MHz

    I found the following article from Apple: TA20612. It reads as follows: 
    "The popping sound does not indicate any software issue or hardware failure. This is a normal part of hardware-software initialization after waking from sleep or during startup."
    I'm a bit skeptical. I think I would have noticed this on the old iMac. Since I haven't yet sold it, I'm going to try to arrange for some side-by-side testing. I'll update this thread when I have the results.

Maybe you are looking for