Tracking down a blue screen cause

Discussion in 'Windows OS and Software' started by raz1337, Aug 23, 2010.

Thread Status:
Not open for further replies.
  1. raz1337

    raz1337 Notebook Evangelist

    Reputations:
    20
    Messages:
    303
    Likes Received:
    0
    Trophy Points:
    30
    I'm on an Asus G51VX-X3A running Windows 7 Home Premium. Recently I had video issues that led me to reinstalling Windows. The G51 comes with an OS and Driver CD. I had lost the driver CD, so after I installed the OS, I got everything off Asus, and everything was pretty. I got rid of all the unknown devices in device manager. Now, a few weeks into it, I'm getting random blue screens.

    One happened while watching videos in Firefox. Another happened in the middle of Starcraft 2. Another happened this morning during a class while we were working on an assignment on a website.

    The information on the screen flashes too fast to see what it is. Is the blue screen logged somewhere so we can try to track down the culprit?
     
  2. thundernet

    thundernet Notebook Deity

    Reputations:
    609
    Messages:
    1,285
    Likes Received:
    0
    Trophy Points:
    55
    Have you looked at the Event Viewer?There must be a log with the blue screen occurances.
     
  3. PatchySan

    PatchySan Om Noms Kit Kat

    Reputations:
    3,970
    Messages:
    2,248
    Likes Received:
    221
    Trophy Points:
    81
    You can also try the Reliability Monitor to check if it's logged down. Just type it on the Start Orb Search Bar and find out the culprit.

    Otherwise if the BSOD flashes too quickly and restart then you can do this. Right-click on Computer then click Properties. On the left bar choose "Advanced System Settings" then on Startup & Recovery click "Settings". Under System Failure uncheck "Automatically Restart". This is so when the BSOD appear again it will hang on the screen instead of restarting so you can take note of the failing driver. You will need to hard reset once you acquire this information.
     
  4. woofer00

    woofer00 Wanderer

    Reputations:
    726
    Messages:
    1,086
    Likes Received:
    0
    Trophy Points:
    55
    You can try using WhoCrashed to figure it out. At the least, minidumps are usually enabled by default in Win7, so you can backtrack to the cause. WhoCrashed has a somewhat easier interface than other error code viewers, without oversimplifying the output.
     
  5. newsposter

    newsposter Notebook Virtuoso

    Reputations:
    801
    Messages:
    3,881
    Likes Received:
    0
    Trophy Points:
    105
    Nirsoft has a BlueScreenView/minidump reader that does a very good job.

    of course, you have to have your machine configured to actually generate the crash files. If you've disabled this, you're kind of stuck. No diag info, no crash diagnosis possible.

    Read this:

    How to configure Windows to create MiniDump files on BSOD
     
  6. woofer00

    woofer00 Wanderer

    Reputations:
    726
    Messages:
    1,086
    Likes Received:
    0
    Trophy Points:
    55
    WhoCrashed requires proper WinDbg and proper config to work right, so it's not novice level for sure, but I like the output better than BlueScreenView. BlueScreenView listed everything that was loaded/running, but made isolating single issues down to a certain device or driver a bit of a pain. You could at least get the why but never the what.
     
  7. raz1337

    raz1337 Notebook Evangelist

    Reputations:
    20
    Messages:
    303
    Likes Received:
    0
    Trophy Points:
    30
    Oh, it was set to a kernel dump. I changed it to small memory dump. I'll wait for it to happen again then.
     
  8. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,589
    Messages:
    10,824
    Likes Received:
    358
    Trophy Points:
    501
    best thing i found to use is Who Crashed

    run it now and it should still give you the last bsod and run it after all bsod to see if its the same error.
     
  9. coolguy

    coolguy Notebook Prophet

    Reputations:
    805
    Messages:
    4,685
    Likes Received:
    12
    Trophy Points:
    106
    Bluescreenview is good. You can also install the latest Windows debugging tools, which includes WinDbg, to get more information about the memory/ kernel dumps.
     
  10. raz1337

    raz1337 Notebook Evangelist

    Reputations:
    20
    Messages:
    303
    Likes Received:
    0
    Trophy Points:
    30
    The only thing I can do now is wait for it to happen again. I haven't seen it in a week.
     
Loading...
Thread Status:
Not open for further replies.

Share This Page