Auto shutdown the DB

I have the Linux version Oracle 10g run a bit long over 1 years, but in this 2 weeks , DB run few day(may 5-10 days) will auto shutdown.
Have any log file can check back is what problem to shutdown?
Which log file can help to track it / Log file Path is ?
Thx a lot.

Look in alert log, then follow up with any trace logs that the alert logs refer you to.
Find out if there is any scheduled job that is supposed to do or has normally always been doing a shutdown and restart of the database, but for some reason, can no longer startup the database after the scheduled shutdown.
For instance, if you normally do a weekly shutdown to do a cold backup, check if the shutdown part is always successful and the startup part has been failing.
The same thing happened for the Web Server at one of my new clients. The weekly shutdown and startup for a full system backup has been working for years, but all of a sudden malfunctioned. Every Monday, Apache is down. it was later traced to the script scheduled in weekly cron job. The script was referencing a module that no longer works with a latest OS patch. After it was fixed, it works ok.

Similar Messages

  • WDS unattend.xml shutdown the system after installing the image instead of reboot.

    I have a large number of machines that I want to install Windows 7 by using WDS unattend.xml. 
    unattend.xml works absolutely fine but I want WINPE to shutdown the system at the end of image installation and before OOBE. 
    Could you please let me know, how can I automate this process, so Winpe shutdown instead of rebooting after image deployment and before oobe.
    Do I have to put this command x:\windows\system32\wpeutil.exe shutdown somewhere in unattend.xml or elsewhere else. 
    I would appreciate if you could please answer this question.
    Here my unattend.xml it works fine, but reboots the system instead of shutdown. 
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
    <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SetupUILanguage>
    <UILanguage>en-US</UILanguage>
    </SetupUILanguage>
    <InputLocale>0809:00000809</InputLocale>
    <SystemLocale>en-GB</SystemLocale>
    <UserLocale>en-GB</UserLocale>
    </component>
    <component name="Microsoft-Windows-Setup" processorArchitecture="x64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <DiskConfiguration>
    <Disk wcm:action="add">
    <CreatePartitions>
    <CreatePartition wcm:action="add">
    <Order>1</Order>
    <Type>Primary</Type>
    <Extend>true</Extend>
    </CreatePartition>
    </CreatePartitions>
    <ModifyPartitions>
    <ModifyPartition wcm:action="add">
    <Order>1</Order>
    <Active>true</Active>
    <Extend>false</Extend>
    <Format>NTFS</Format>
    <Label>Windows</Label>
    <Letter>C</Letter>
    <PartitionID>1</PartitionID>
    </ModifyPartition>
    </ModifyPartitions>
    <DiskID>0</DiskID>
    <WillWipeDisk>true</WillWipeDisk>
    </Disk>
    </DiskConfiguration>
    <WindowsDeploymentServices>
    <ImageSelection>
    <InstallTo>
    <DiskID>0</DiskID>
    <PartitionID>1</PartitionID>
    </InstallTo>
    <InstallImage>
    <ImageGroup>xxxxxxxxxxx</ImageGroup>
    <ImageName>xxxxxxxxxxxx</ImageName>
    <Filename>xxxxxxxxxxxxx</Filename>
    </InstallImage>
    </ImageSelection>
    <Login>
    <Credentials>
    <Domain>xxxxxxx</Domain>
    <Password>xxxxxxx</Password>
    <Username>xxxxxx</Username>
    </Credentials>
    </Login>
    </WindowsDeploymentServices>
    <restart>Shutdown</restart>
    </component>
    </settings>
    <cpi:offlineImage cpi:source="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
    I have also tried to use the command line like this, see below. 
    </WindowsDeploymentServices>
    <CommandLine>
    x:\windows\system32\wpeutil.exe shutdown
    </CommandLine>
    WinPE does not even start with above mentioend wpeutil.exe shutdown command, it throws an error and reboots. 
    I would really appreciate if someone can help me figure it out, how can I auto shutdown the system instead of reboot after WDS / WINPE installs the image.
    Thanks in advance

    1. When the error message appears, open up a command window with SHIFT + F11
    2. open the REGEDIT
    3. navigate to hklm\system\setup
    4. change CmdLine to blank (no value entered) (was oobe\windeploy.exe)
    5. change CreateNewQueueOnFirstBoot to 0 (was 1)
    6. change OOBEInProgress to 0 (was 1) (i am guessing that might be AUDITInProgress
    if that was your sysprep choice)
    7. change SetupPhase to 0 (was 4)
    8. change SetupShutdownRequired to 0 (was 1)
    9. change SetupType to 0 (was 2)
    10. change SystemSetupInProgress to 0 (was1)
    11. exit REGEDIT and reboot

  • How im suppose to fix the auto shutdown problem in my iphone 3gs after updating to ios 5.1.1 this problem has made me a mobile ****** in my house and an loser in thing care so if any solution to this problem let me know

    how im suppose to fix the auto shutdown problem in my iphone 3gs after updating to ios 5.1.1 this problem has made me a mobile ****** in my house and an loser in thing care so if any solution to this problem let me know

    What "auto shutdown problem" are you talking about?

  • After running Appstore, the iphone cannot auto shutdown after the predefined time

    After running Appstore, the iphone cannot auto shutdown after the predefined time.

    Pressing the Home button only quits the selected application only. Doing so with Safari available will quit Safari, but this does not reset the iPhone.
    The only way to Reset an iPhone is by pressing and holding the Home button and the Sleep/Wake button simultaneously until you see the Apple logo and then release.
    No apple stores in the area but my sister and mom are going to an area where there is one so I guess I'll give it to them to take along and see if they can swap it out for another or fix it.
    You must make an appointment at an Apple Store, so unless you are able to do so and unless you are able to go with them (especially if an exchange might be involved), I suggest giving AppleCare a call instead.

  • UPS Auto-Shutdown not the same as a 'Cold' Shutdown?

    Hello folks,
    I've an APC UPS system that interfaces great with my iMac. In case of power outages, I configure it to shutdown the computer automatically when it has been on UPS power for a certain amount of time.
    I've never had a serious power outage before, but it happened the other day. The UPS automatically shutdown the iMac after the specified amount of time. Now I was wondering if this kind of shutdown is similar to a 'cold' shutdown and therefore harmful to my iMac? If so, what's to be done when I startup and login the next time?
    Thanks.
    Stephen.

    I would be careful with the assumptions. Three seconds is an awfully fast shutdown time. If the power down had not been graceful, is is possible that the OP would only have had a few seconds added to the boot time. It sounded from the post like it did not gracefully shut down.
    How do you know it works if you don't try it? Why not configure the UPS to shut down after 5 minutes, put the Mac to sleep, and pull the plug on the UPS. If it is indeed configured and working correctly you have nothing to worry about.
    I have been through hundreds of UPSs in my career. They fail often. I test all of mine once a month when I vacuum out my machines.
    Luck-
    -DaddyPaycheck

  • Mythtv, auto shutdown no longer working, scheduler.cpp ?

    Following a recent update the automatic shutdown of my backend is no longer working (well, at least not reliably).
    I have 3 scripts set up in the relevant sections of the mythtv-setup to check if myth is ok to shut down, set the new wakeup time and perform the actual shutdown. These scripts still work alright, but the backend is not initiating the shutdown any more in some cases.
    Lots of trial and error makes me think that this is somehow related to scheduler.cpp, but I am not sure if this is the case or how to fix it.
    I think I have established a pattern:
    Scenario 1:
    - Boot backend
    - do nothing else (e.g. start remote frontend or mythfrontend on the backend)
    - automatic shutdown does not work
    Scenario 2:
    - Boot backend
    - start remote frontend
    - shut down frontend
    - automatic shutdown does not work
    - restart backend service (without reboot)
    - automatic shutdown works
    I also notice that in scenario 2 (when automatic shutdown works) there are a whole heap of these kind of messages right until shutdown occurs:
    2013-04-29 19:18:07.592125 N [660/738] Expire autoexpire.cpp:641 (SendDeleteMessages) - Expiring 156 MB for 1073 at 2013-04-13T11:50:20Z => Hulk
    2013-04-29 19:18:07.632899 E [660/660] CoreContext mainserver.cpp:2610 (DoHandleDeleteRecording) - ERROR when trying to delete file: myth://192.168.1.103:65103:6543/1070_20120126203445.mpg. File doesn't exist. Database metadata will not be removed.
    2013-04-29 19:18:07.889638 E [660/660] CoreContext mainserver.cpp:2610 (DoHandleDeleteRecording) - ERROR when trying to delete file: myth://192.168.1.103:65103:6543/1022_20120206192600.mpg. File doesn't exist. Database metadata will not be removed.
    In scenario 2 (successful) I see the following in the log just before the above auto expire stuff:
    Scheduler scheduler.cpp:2307 (HandleRunSchedulerStartup) - Scheduler: Seem to be woken up by USER
    then a whole heap of auto expiry stuff and finally:
    Scheduler scheduler.cpp:2862 (CheckShutdownServer) - CheckShutdownServer returned - OK to shutdown
    2013-04-29 19:19:55.276775 N [660/735] Scheduler scheduler.cpp:2947 (ShutdownServer) - Running the command to set the next scheduled wakeup time :-
    sudo /home/laffi/scripts/MythSetWakeup 1367229120
    2013-04-29 19:19:55.372582 N [660/735] Scheduler scheduler.cpp:2974 (ShutdownServer) - Running the command to shutdown this computer :-
    sudo /home/laffi/scripts/MythShutdown
    In scenario 1 (unsuccessfull shutdown) I also get
    Scheduler scheduler.cpp:2307 (HandleRunSchedulerStartup) - Scheduler: Seem to be woken up by USER
    and then autoexpiry, but then, once a frontend connects:
    ProcessRequest mainserver.cpp:1385 (HandleAnnounce) - adding: frontend as a client (events: 0)
    I don't get autoexpiry of files and no shutdown, both of which I believe are initiated by scheduler.cpp
    I also noticed the following in the logs when auto shutdown does not work:
    2013-04-29 15:40:36.046359 I [648/848] ProcessRequest mainserver.cpp:1385 (HandleAnnounce) - adding: mythbackend as a client (events: 1)
    which does not seem to appear in the logs when auto shutdown works.
    Any ideas ? I have found very little (next to none) regarding scheduler.cpp when searching.

    The other side of the VPN is a TMG server hosted at our main office.  I can connect to it off site, and others were connected to it remotely as well, but for some reason users at that remote site can no longer connect to the VPN.
    I talked to my ISP wondering if there was something that was blocked due to the change from dhcp to static IP addresses, but they don't see anything.

  • One application "failed to quit" on auto shutdown

    This has been happening daily now for perhaps a month, and it's got me stumped. I can't identify any pattern or anything.
    I have my system scheduled to shutdown overnight and start up in the morning, and have had this same setting for years. What's happening lately is that the unattended shutdown apparently times out and I get a message saying logout failed "because the application [X] failed to quit." Now the really weird bits -
    'X' is almost literally a different application every day, and it's rarely if ever attributable to an unsaved document. I think it's happened at least once with every single one of the applications I regularly have running. Sometimes it's an application I've used in the course of the day, and other times it's one I haven't touched. But it happens every day.
    if I manually select the shutdown menu command at any time, including after finding that the auto shutdown has again failed, the shutdown runs smoothly with no application failing to quit.
    I've run 'repair disk' in Disk Utility and also Disk Warrior and applejack several times each, as well as a weekly scheduled batch of maintenance tasks (using Cocktail). None of these operations has changed the behaviour come shutdown time.
    Has anyone else seen this?  Solutions anyone?  Thanks.

    I'm 'bumping' this one.
    Still happening very consistently, and becoming a real problem. Since originally posting I've run all the disk operations many times over, as well as one or two system updates at least. Nothing has changed, it just happens like this every night.
    The only thing I can offer as a (sort of) pattern is that the application that's most often the one reported as preventing logout is HistoryHound. And it would appear to be one of the first ones the system tries to quit in its shutdown, since most of the apps are still running. However it does still vary - it happens on a different app sometimes, and it happens on some app when HH wasn't even running. So not sure that's much of a clue - unless perhaps certain apps are taking longer to quit than the system expects (or something??? - scratching for clues here ...... )
    Can anyone help? Please ....

  • Safari Auto Shutdown in Yosemite

    Hi All,
    Ever since I upgraded to Yosemite, my safari will auto shutdown itself. There is not telling when it will auto shutdown but usually if I left it open overnight or during the day. I'm not sure if its considered a crash because usually a crash window will prompt telling you the app has crashed. I have at least 80GB free space and my iMac is only a year old therefore it can't be hardware problem. I would have other apps like iTunes and iPhoto or Mail opened and they stay open throughout.
    Anyone has the solution for this?
    Thank you!

    Hi Patrick,
    Thanks for the info. Just tired it and left over night and still Safari disappeared when I check in the morning.

  • Hi there, I'm having my iPhoto (8.1.2 version) making auto-shutdown with no reason Does anybody know what shall I do with it? Regards, Miguel Sim

    Hi there,
    On my iMac from 2009 - 3,06 Ghz Core 2 Duo with Mac OS X lion 10.7.5 (11G63) I'm having the iPhoto (8.1.2 version) making auto-shutdown with no reason;
    Does anybody know what shall I do with it ???
    Regards,
    Miguel Sim.

    Hello again,
    Process:         iPhoto [2771]
    Path:            /Applications/iPhoto.app/Contents/MacOS/iPhoto
    Identifier:      com.apple.iPhoto
    Version:         8.1.2 (8.1.2)
    Build Info:      iPhotoProject-4240000~8
    Code Type:       X86 (Native)
    Parent Process:  launchd [141]
    Date/Time:       2013-11-14 18:53:17.814 +0000
    OS Version:      Mac OS X 10.7.5 (11G63)
    Report Version:  9
    Interval Since Last Report:          106324 sec
    Crashes Since Last Report:           2
    Per-App Interval Since Last Report:  634 sec
    Per-App Crashes Since Last Report:   2
    Anonymous UUID:                      637A60DB-E15A-441E-BAAB-F21EF18FA1B6
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: 0x000000000000000a, 0x000000000cfbc000
    VM Regions Near 0xcfbc000:
        JS JIT generated code  000000000cfb4000-000000000cfbc000 [   32K] rwx/rwx SM=PRV 
    --> mapped file            000000000cfbc000-000000000cfcc000 [   64K] r--/rwx SM=COW  /Users/USER/Pictures/*/*.jpg
        TC malloc              000000000cfcc000-000000000d0cc000 [ 1024K] rw-/rwx SM=PRV 
    Application Specific Information:
    objc[2771]: garbage collection is OFF
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_c.dylib             0x9144ebe1 memmove$VARIANT$sse3x + 35
    1   com.apple.ImageIO.framework   0x99396ca0 _CGImageSourceBindToPlugin + 300
    2   com.apple.ImageIO.framework   0x99396b63 CGImageSourceGetType + 55
    3   com.apple.CoreGraphics        0x939bdc4c CGImageCreateWithJPEGDataProvider2 + 166
    4   com.apple.CoreGraphics        0x939bddc4 CGImageCreateWithJPEGDataProvider + 47
    5   com.apple.iPhoto              0x001aa38e 0x1000 + 1741710
    6   com.apple.iPhoto              0x0043d5a6 0x1000 + 4441510
    7   com.apple.iPhoto              0x00448902 0x1000 + 4487426
    8   com.apple.AppKit              0x9494f79d -[NSView _drawRect:clip:] + 3929
    9   com.apple.AppKit              0x9494d7bc -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 2650
    10  com.apple.AppKit              0x9494e193 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 5169
    11  com.apple.AppKit              0x9494e193 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 5169
    12  com.apple.AppKit              0x9494e193 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 5169
    13  com.apple.AppKit              0x94947caa -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 4817
    14  com.apple.AppKit              0x94940bd9 -[NSView displayIfNeeded] + 1365
    15  com.apple.AppKit              0x94945872 -[NSClipView _immediateScrollToPoint:] + 6543
    16  com.apple.AppKit              0x94943e2e -[NSClipView scrollToPoint:] + 234
    17  com.apple.AppKit              0x94a34137 -[NSScrollView scrollClipView:toPoint:] + 279
    18  com.apple.AppKit              0x94a33efb -[NSClipView _scrollTo:animateScroll:flashScrollerKnobs:] + 1533
    19  com.apple.AppKit              0x94a3711c -[NSClipView _scrollTo:animate:] + 62
    20  com.apple.AppKit              0x94a370d4 -[NSClipView _scrollTo:] + 48
    21  com.apple.AppKit              0x94a3709b -[NSClipView _scrollPoint:fromView:] + 107
    22  com.apple.AppKit              0x94a37029 -[NSView(NSPrivate) _scrollPoint:fromView:] + 50
    23  com.apple.AppKit              0x94a36fef -[NSView scrollPoint:] + 65
    24  com.apple.iPhoto              0x001c08e4 0x1000 + 1833188
    25  com.apple.iPhoto              0x001bff5b 0x1000 + 1830747
    26  com.apple.AppKit              0x949d1508 -[NSWindow sendEvent:] + 9384
    27  com.apple.AppKit              0x94969f77 -[NSApplication sendEvent:] + 4788
    28  com.apple.iPhoto              0x00229973 0x1000 + 2263411
    29  com.apple.AppKit              0x948fbb21 -[NSApplication run] + 1007
    30  com.apple.AppKit              0x94b8cac5 NSApplicationMain + 1054
    31  com.apple.iPhoto              0x00124b80 0x1000 + 1194880
    32  com.apple.iPhoto              0x00003172 0x1000 + 8562
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib        0x9982ab5e __select_nocancel + 10
    1   libdispatch.dylib             0x9c80bcbd _dispatch_mgr_invoke + 642
    2   libdispatch.dylib             0x9c80a853 _dispatch_mgr_thread + 53
    Thread 2:: Dispatch queue: CFPreferences Background Sync Queue
    0   libsystem_kernel.dylib        0x9982a71e __open_nocancel + 10
    1   libsystem_c.dylib             0x914c643d _gettemp + 554
    2   libsystem_c.dylib             0x914c65df mkstemp + 32
    3   com.apple.CoreFoundation      0x9685fc06 -[CFXPreferencesPropertyListSourceSynchronizer writePlistToDisk] + 1366
    4   com.apple.CoreFoundation      0x968243a3 -[CFXPreferencesPropertyListSourceSynchronizer synchronizeAlreadyFlocked] + 595
    5   com.apple.CoreFoundation      0x968240fa -[CFXPreferencesPropertyListSourceSynchronizer synchronize] + 522
    6   com.apple.CoreFoundation      0x9686750a __-[CFXPreferencesPropertyListSource synchronizeInBackgroundWithCompletionBlock:]_block_invoke_1 + 122
    7   libdispatch.dylib             0x9c809fbd _dispatch_call_block_and_release + 15
    8   libdispatch.dylib             0x9c80b943 _dispatch_queue_drain + 224
    9   libdispatch.dylib             0x9c80b7e8 _dispatch_queue_invoke + 47
    10  libdispatch.dylib             0x9c80aff0 _dispatch_worker_thread2 + 187
    11  libsystem_c.dylib             0x91478b24 _pthread_wqthread + 346
    12  libsystem_c.dylib             0x9147a6fe start_wqthread + 30
    Regards,
    Miguel Sim

  • Should an auto-shutdown because of critical battery change kernel_task usage at all?

    I only ask because when my MacBook Pro 13" (Early 2011) 10.7.2, shutdown because of low battery, I put it on charge. The next day when I booted it up again it started running super-mega slow. The only reason I can find for this is kernel_task at 330mb, and about 300 % CPU.
    It runs fine in Safe Mode.
    The whole auto-shutdown is the only change I made between normal speed and claw-my-own-eyes-out speed.

    Fixed:
    Plugged in power supply and rebooted, now it works fine.

  • Auto-Shutdown when ATV3 Sleeps?

    Hey Guys,
    Hopefully I've got the right place.
    I'm wanting to know if there is a way I can set my computer to auto-shutdown when the apple TV3 is put to sleep?
    Running Windows XP
    I can set a task to schedule a shut-down at a specific time, but this wont always be the best option as partner can stay up lat and watch it.
    Guess I'm just wondering if there's some advanced script or anything that will pick-up on itunes when its in sleep mode, and then set computer for shutdown?
    And maybe just another thing to note, the drop down box below for product doesn't even have ATV3 listed haha
    Tks
    Steve

    >I'm talking about a setting on my computer to shut itelsef down
    All computers can already be set to do that.
    >Setting the computer to shutdown on idle is an on-going argument I guess as well
    Argument about what?  This is a standard feature on any computer and has been for over a decade.  If you would like to take adavanage of it then set it to do that.
    >Is streaming considered the computer being in idle mode?
    No, the computer is actively running to server content and is receiving constant WAKE_ON_LAN requests.
    >Becuase it's just sitting there not doing anything
    Not true.  It is serving the content which is a VERY active process.

  • Auto shutdown feature

    hi all i'm a newbie here...
    i wanna ask you which bios menu will enable us to disable the auto shutdown? i keep failing occt though the temps were only 65C! my motherboard is MSI 890FXAGD70

    Quote from: Jack t.N. on 30-July-10, 16:39:46
    That was a thermal shutdown then.  This is a safety mechanism to prevent CPU damage due to overheating. Trust me, you do not want to turn that off...
    Better work on your cooling solution. 
    you know what? i believed it too because its an alarm to warn us right? but say, what is the menu for doing that? just curious

  • Satellite M-500 Auto shutdown

    My Satellite M-500 will auto shut-down at most of the time while loading the windows 7.
    If I'm lucky, my windows 7 will able to load into desktop but after a while, it's will auto shutdown again.
    I've re-format my hard disk and re-install the windows 7 operating system but the problem is still not solved.
    But one thing that I now wondering is, I've swap the hard disk to my company laptop, both of the laptop will working well. No auto shut-down any more.
    Please advice.
    Thank you.

    It sounds like it could be a hardware issue.
    If you can't solve your issue and no one in the community can help, contact support to speak with a tech support agent at (800) 457-7777.
    - Peter

  • Implementing Auto Shutdown feature in J2ME midlet

    I am trying to figure out all possibilities to implement an auto shutdown feature in an application which uses only high level UI components (Lists and Forms), if the application remains idle for a specified time say 60 seconds.
    Any suggestions how one could achieve this.
    Thanks.

    No, its not necessary that everytime user does something and some code is executed, for instance if the user is navigating UP or Down a List and is only pressing UP/DOWN navigation keys in such a case no code is executed. What to do in such a case??
    Thanks.

  • Macbook pro auto shutdown

    my work need win7 system,so i get a win7 ultimate
    recently i find out when i run some applications for 3~4 hours in win7 system,my macbook pro auto shutdown...even the power adapter is on,the battery still run out.
    this never happened in my macbook pro before when i use leopard or XP system

    Thanks for taking so much time in helping me.
    Just an update:
    2 loops/passes done - no errors.
    Called up Digital Hub and talked to the technician, he says there are 3 possible problems:
    1. Battery (which is still inside the laptop) may cause some disturbances with the electric current
    2. Software related - most likely re-formatting may be needed
    3. Video card may have failed, which means complete change of the logic board ----> worst case
    I'm crossing my fingers that it's either of the first two.

Maybe you are looking for