The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    G73JH went into BSOD and Repair Mode upon startup

    Discussion in 'ASUS Gaming Notebook Forum' started by darkwonders, Mar 28, 2011.

  1. darkwonders

    darkwonders Notebook Guru

    Reputations:
    0
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    15
    Yesterday, my laptop worked fine. I upgraded to 11.4 Catalyst to see if it made an improvement. I ended up playing Rift the entire afternoon into the late night. Upon shutting down my computer, I got some random error messages of things being forced to shut down. I thought nothing of it at the time as it has happened in the past.

    Now when I went to turn it on this morning, it flashed a bsod and then restarted. Since the screen never stayed long, I didn't get a chance to look at it. It then booted into Repair mode. After failing to be able to use the repair mode (it kept on showing me the bsod) I held the power button down and rebooted it again. This time it seems to have let me into Windows with no problem.

    I probably didn't fix the problem, so I'm worried that it'll come back again.
    Any idea how to fix it?

    I have BIOS 213 and v93 vBios with modded overdrive option.

    Before I installed 11.4, I uninstalled 11.2 and ran ATI Crap Cleaner and Driver Sweeper to get rid of any files left over from the uninstall. I figured that would be enough to rid me from problems in installing 11.4.
     
  2. ALLurGroceries

    ALLurGroceries  Vegan Vermin Super Moderator

    Reputations:
    15,730
    Messages:
    7,146
    Likes Received:
    2,343
    Trophy Points:
    331
  3. darkwonders

    darkwonders Notebook Guru

    Reputations:
    0
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    15
    Thanks. I'll have to do this after work. I'll get back to this thread with the cause of my BSOD.

    Hmmm... strange. There seems to be no critical errors this morning in the Event Viewer. Though scrolling back there's a lot of errors for ACPI, Service Control Manager, Application Error, and Bonjour Service.

    Are those anything important?
     
  4. ALLurGroceries

    ALLurGroceries  Vegan Vermin Super Moderator

    Reputations:
    15,730
    Messages:
    7,146
    Likes Received:
    2,343
    Trophy Points:
    331
    Sometimes you won't get the bsod in your event log, you should disable automatic reboot: Automatic Restart Windows 7 - How To Disable the Automatic Restart on System Failure in Windows 7

    Then the next time you can write down the stop code that you get if it BSODs during startup.

    In terms of the errors, I have no idea if they are related to your BSOD, if they started showing up recently and weren't there before it could be a hint.

    Otherwise, it's probably just a trashed ATI driver installation (somehow) so see what happens and maybe reinstall them again or move to older catalyst drivers.
     
  5. darkwonders

    darkwonders Notebook Guru

    Reputations:
    0
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    15
    Well I did a CHKDSK and repair thing this afternoon. Everything loaded fine since then. I'll disable that feature and see if I can catch the BSOD again.

    Those program errors have been happening for as long as I have had the laptop apparently. They aren't recent.

    The only critical errors on the Event Viewer is when my laptop hard froze and I had to hold the power button down to reboot.

    I'll keep my ATI driver where it's at right now. If I run into the issue again, I'll reinstall it. Not sure how the installation could go wrong. I completely removed all ATI driver software before I upgraded as to make sure there's no conflicting files lying around.

    For some reason every 10 minutes or so, the event viewer logs 2 errors. And to make matters worse, it happened 4 times in a row just a few minutes ago.
    1)The Windows Search service terminated unexpectedly
    2)

    Faulting application name: SearchIndexer.exe, version: 7.0.7600.16385, time stamp: 0x4a5bd212
    Faulting module name: TQUERY.DLL, version: 7.0.7600.16385, time stamp: 0x4a5be07e
    Exception code: 0xc0000005
    Fault offset: 0x000000000007b247
    Faulting process id: 0x1c90
    Faulting application start time: 0x01cbed93814fa869
    Faulting application path: C:\Windows\system32\SearchIndexer.exe
    Faulting module path: C:\Windows\system32\TQUERY.DLL
    Report Id: bf564b23-5986-11e0-b566-20cf306497eb

    I'm not sure how to fix either of these error. And there seems to be no visual indication for these errors.