3 BSOD's in one hour, no logs to show for it though


  1. BBL
    Posts : 6
    Windows 7 Home Premium 64bit
       #1

    3 BSOD's in one hour, no logs to show for it though


    Hi all,

    I've had a problem with blue screening recently, and suddenly this afternoon I've blue screened three times in under an hour (just while browsing Firefox, not playing any games or anything). Unfortunately Windows is not recording a log/dump file in the c/windows/minidump folder for these. I am attaching a zip of information gathered from the "SF Diagnostic Tool" program, but please realize the BSOD errors contained in it are old.

    The recent blue screens have contained the messages "bad_pool_header" and "memory management". I cannot figure out why Windows won't log these new crashes though (I have "write an event to the system log" checked under startup and recovery options).

    I am going to try running Memtest86+ soon, but I'd really appreciate it if anyone has any other advice.
      My Computer


  2. Posts : 138
    Windows 7 Enterprise x64, Windows 8 Enterprise x64
       #2

    Update the following drivers:

    NewDeathAdder Mouse
    fffff880`05728000 fffff880`0572af00 danew Tue Mar 23 09:37:33 2010 (4BA87DCD)

    NVIDIA GeForce GTX 470
    fffff880`0f436000 fffff880`101f8000 nvlddmkm Tue May 15 09:35:36 2012 (4FB20748)
      My Computer


  3. BBL
    Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Updated mouse drivers, video card is still up to date though ("Your driver is up to date with version 301.42."). Will update this thread if the BSOD's continue. Thanks for the reply. :)
      My Computer


  4. BBL
    Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    Just got another BSOD immediately after logging into Windows (didn't even get a chance to see the desktop). Again, no log some reason, but the error message at the top read "PAGE_FAULT_IN_NONPAGED_AREA".
      My Computer


  5. Posts : 1,436
    Windows 8.1 Pro x64
       #5

    Hello,

    Sorry to butt in Tobias.

    Code:
    MaxSpeed:     3400
     
    CurrentSpeed: 3502
    Overclocks are very risky and could cause problems such as BSODs. I suggest you to reset everything back to default, and do not overclock during this troubleshooting process.

    If updating the NewDeathAdder Mouse driver did not work, then try uninstalling it temporarily.

    Also please post up the new crash files.

    -Justin
      My Computer


  6. BBL
    Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    I will try removing the overclock. However, as I mentioned, some reason Windows is not recording any of the new crash files. I have no idea how to go about fixing this.
      My Computer


  7. BBL
    Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    I'm not sure if you guys can help me out on this, but I cannot figure out how to remove the overclock from my machine. I used ASUS' "Auto Tuning"/"TurboV EVO" to overclock it originally (about 6 months ago), and I cannot find anything in the AI Suite II software to undo it. I tried poking around in the BIOS settings, where I could see that it was overclocked, and I disabled the Turbo feature in the BIOS, but it didn't underclock it and I cannot find anywhere else to do it.

    Edit: Think I figured it out
    Last edited by BBL; 16 Aug 2012 at 17:03.
      My Computer


  8. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #8

    bbl,

    Follow this procedure, precisely as written, you will get your dumps.

    MEMORY DUMPS - REQUIREMENTS


    Enable automatic management of the Paging file
    WIN + PAUSE/BREAK key combo |
    Advanced system settings (left-hand side) |
    Advanced tab, Performance section, Settings |
    Advanced tab, Virtual Memory section, Change |
    checkmark Automatically manage paging file size for all drives |
    OK | OK | OK



    STARTUP AND RECOVERY SETTINGS
    WIN + PAUSE/BREAK key combo |
    Advanced system settings (left-hand side) |
    Advanced
    tab, Startup and Recovery section, Settings |
    System Failure section | checkmark Write an Event to the system log
    | uncheck
    Automatically restart |


    Under Write debugging information, select Small memory dump |
    in the Small dump directory: box, enter %SystemRoot%\Minidump| OK

    If Overwrite any existing file is checked, then:
    Ø Under Write debugging information, select Kernel memory dump
    Ø Uncheck Overwrite any existing file
    Ø Under Write debugging information, select Small memory dump
    Ø OK button
    If you get a crazy message from Win 7 about your paging file being too small, then just ignore the message since we have already made sure that the paging file is set to be managed by Win 7.

    ENABLE THE WINDOWS ERROR REPORTING SERVICE
    WIN key | type SERVICES.MSC | ENTER |
    Scroll down to Windows Error Reporting Service |
    Rt-clk on Windows Error Reporting Service | Properties |
    General
    tab | for Startup type, choose Automatic |
    In Service status, Start button (unless grayed out) | OK


    ASSURE THAT CCLEANER IS NOT DELETING DUMPS
    CCLEANER | Cleaner icon | Windows tab | System category |
    Uncheck Memory Dumps
    · WINDOWS ERROR REPORTING SERVICE must NOT be disabled!
    · WIN | Services.msc | Enter
    · Under Name, locate Windows Error Reporting Service
    · If Status is not Started, then
    Right-click on Windows Error Reporting Service |choose START
    · If Startup Type is not Automatic, then
    Right-click on Windows Error Reporting Service |
    choose Properties | General tab |
    set Startup type to Automatic
    · Close Services.msc (I like to use ALT + F4)

    After a crash, the minidump file will be in %SystemRoot%\Minidump
    %SystemRoot% is generally C:\Windows

    ===========================================
    ===========================================

    Now let's see if you dotted all of the "i"s and crossed all of the "t"s.

    # STEP 1 ** RUN POWERSHELL AS ADMINISTRATOR
    WIN key | type POWERSHELL | do NOT hit ENTER |
    in the PROGRAMS list, right-click on WINDOWS POWERSHELL |
    choose "Run as administrator" |
    Click on the YES button (if such appears)

    # STEP 2 ** COPY AND PASTE
    COPY the script using CTRL+C,
    PASTE into Powershell
    ---Right-Click at the PowerShell Prompt
    ---(Ctrl+V does not work)

    WIN key = key with Microsoft logo on top
    =======================================

    And here is the script to run and then upload the minidumpsettings.txt file that shows up on your desktop.

    Script:
    # **************************************************************
    # Puts MiniDumpSettings.TXT in your user profile folder
    # WIN | type %userprofile%\ then click on MiniDumpSettings.TXT
    # to view the important minidump settings
    # WIN = key with Microsoft logo on top
    # **************************************************************
    gwmi Win32_OSRecoveryConfiguration 
    select minidumpdirectoryexpandedminidumpdirectoryoverwriteexistingdebugfilekerneldumponly,`
    debuginfotype, autoreboot, writedebuginfo, writetosystemlog | fl > 
    $env:userprofile\desktop\minidumpsettings.txt

    EXIT
    EXIT 
      My Computer


  9. BBL
    Posts : 6
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    Hey all,

    Somewhat to my surprise, removing the overclocking has completely stopped the blue screens (as of now). So thanks a ton for that suggestion, and for the others as well. If I run into issues again in the future I'll be sure to revisit this thread and follow the rest of the advice given.

    Thanks!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:18.
Find Us