Bugcheck blue screen

Page 1 of 2 12 LastLast

  1. Posts : 1,870
    MS Windows 7 Professional 64-bit SP1
       #1

    Bugcheck blue screen


    Can someone have a look over this for me, its bluescreened twice now while gamming.

    Specs or filled out below, if you need any more info just ask.

    Thanks in advance
      My Computer


  2. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #2

    Hello Anthony, it's not everyday we see active SF'ers here at our sub-forum!

    BSOD Analyse

    Concerns
    • Running processes
      • Audiodg.exe's information is not available (n/a), which makes me wonder. I see you're using Realtek, so I'd recommend you to do a clean install of it, using the tutorial I'll post.

    • Direct-X was mentioned in the dump, though there weren't any Graphic driver references which is quite rare. To be on the safe side, download Direct-X below and afterwards follow the tutorial below on doing a secure clean install on your Graphic driver.


    Realtek Clean-install

    i) Make your way to Realtek - Downloads
    ii) Uninstall the Realtek driver you currently have and all its extensions
    iii) Download Driver Sweeper
    iv) Get to safe mode (without network) and search for Driver Sweeper in your
    v) Select all the Network Realtek components and analyse them
    vi) Clean them, head into Windows without internet and install the driver you downloaded previously
    Nvidia Clean-install

    i) Make your way to Nvidia Drivers - Download NVIDIA Drivers and download the latest driver for your card, save it to your desktop for instance.
    ii) Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet)
    iii) Download Driver Sweeper
    iv) Get to safe mode (without network) and search for Driver Sweeper in your
    v) Select all the Nvidia components and analyse them
    vi) Clean them, head into Windows without internet and install the driver you downloaded previously.

    Memory // RAM // Test


    Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.

       Warning
    Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

    To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

    Memtest86+ - Advanced Memory Diagnostic Tool
    Summary

    Code:
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041201, The subtype of the bugcheck.
    Arg2: fffff68000036198
    Arg3: df200000cb62e867
    Arg4: fffffa80094e34e0
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88004820cf7, The address that the exception occurred at
    Arg3: fffff880071fe568, Exception Record Address
    Arg4: fffff880071fddc0, Context Record Address
    Device Manager // Last troubleshoot

    Click Start | Search for 'devmgmt.msc' | Expand all the dropdowns
    | Look for

    Report if there's any.

    Best Regards,
    Frederik.
    Last edited by FredeGail; 08 Jul 2012 at 13:39.
      My Computer


  3. Posts : 1,870
    MS Windows 7 Professional 64-bit SP1
    Thread Starter
       #3

    Well that's weired in my quest to fix the issue, I just updated all those files, before I posted here. DirectX Realtek Audio driver and my nvidia gfx driver....

    Oh Well, I will do a Clean Install of those drivers etc, see what happens.

    Thanks very much for your time Frederik

    Take Care
      My Computer


  4. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #4

    You're welcome Anthony!

    Take your time and return when you have your results.

    Best Regards,
    Frederik.
      My Computer


  5. Posts : 1,870
    MS Windows 7 Professional 64-bit SP1
    Thread Starter
       #5

    Thanks Frede, Just an update. I have done a clean install of the OS and still getting the errors, I have narrowed it down to either the memory or the SSD.

    Time to test the hardware which I was trying to avoid

    Thanks again for your time Frede, I owe you one
      My Computer


  6. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #6

    Oh alright. Did you get any errors on the Memtest86+?
    Also make sure that your SSD firmware is up-to-date. It's usually causing BSODs.

    Best Regards,
    Frederik.
      My Computer


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

    Anthony,

    Have you tried booting into SAFE MODE? Yes/No

    Your problem is not necessarily hardware.

    Be sure and once again:
    Blue Screen of Death (BSOD) Posting Instructions
      My Computer


  8. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #8

    You might be able to enter safe mode as karlsnooks said. 3rd party driver might bug your Windows. It's definitely worth trying a scan with Malwarebytes to ensure that either worms, or malware ain't causing your computer to crash.

    malwarebytes.org

    Thank you for updating us!

    Best Regards,
    Frederik.
      My Computer


  9. Posts : 1,870
    MS Windows 7 Professional 64-bit SP1
    Thread Starter
       #9

    Thanks guys for your input, I just pulled a stick of 4gb of memory and so far so good, everything seems to be a bit more responsive, Just played a game without a hictch!! Will keep testing though. I will test again with that 4gb I just pulled, just to be sure it is that stick of ram.

    Thanks again guys
      My Computer


  10. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #10

    You're certainly welcome Anthony!

    Good call on the troubleshooting step you did, sometimes it might only be one single stick.

    Best Regards,
    Frederik.
      My Computer


 
Page 1 of 2 12 LastLast

  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 01:24.
Find Us