locked
Windows 7 64-bit Blue Screen of Death RRS feed

  • Question

  • I am absolutely clueless about computers.

    Here is what happened just now. I've been getting Bluescreens for just a little over 3-4weeks and i have to say its getting increasingly more frustrating. After about a week or so it became so frequent that i just performed a complete wipe and restored my system to factory settings. Initially i believe this solved the problem... for about 4 days =@

    I then decided to once again completely restore my computer... Within 2 hours I've had two bluescreens :@

    It appears to happen when I am on Youtube /Or an MMORPG. Both of which i have been simultaneously running for over a year with absolutely no problems.

    I have looked at a bunch of other topics, and It seems apparently Antiviruses can be the problem? Thinking back my first bluescreen was around the same time i upgraded my Avast security system to V8. And since the first system wipe, i have switched to AVG2013.  -  If this is the case, I would very much appreciate it if you could also recommend a new antivirus, along with a solution!

    Technical details:

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.768.3
      Locale ID:    2057

    Additional information about the problem:
      BCCode:    51
      BCP1:    0000000000000001
      BCP2:    FFFFF8A000023150
      BCP3:    0000000000DDF000
      BCP4:    0000000000000374
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    768_1

    Files that help describe the problem:
      C:\Windows\Minidump\040413-25755-01.dmp
      C:\Users\Mo\AppData\Local\Temp\WER-61698-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt



    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.768.3
      Locale ID:    2057

    Additional information about the problem:
      BCCode:    4e
      BCP1:    0000000000000099
      BCP2:    00000000001CC60D
      BCP3:    0000000000000000
      BCP4:    00000000001CCA4D
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    768_1

    Files that help describe the problem:
      C:\Windows\Minidump\040413-50325-01.dmp
      C:\Users\Mo\AppData\Local\Temp\WER-64054-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt


    • Edited by Dualerz Thursday, April 4, 2013 8:23 AM
    Thursday, April 4, 2013 8:21 AM

Answers

  • Dualerz

    My pleasure.  I started doing BSOD's because I was getting them so often I had to learn how to stop them

    This one crash was Related to AVGIDSDriver.sys IDS Application Activity Monitor Driver. from AVG Technologies.

    I would remove and replace with Microsoft Security Essentials

    AVG  can be a contributing cause of BSOD'S.
    Please remove and replace with Microsoft Security Essentials at least to test.

    BugCheck 93, {0, fffff8a0000017c0, 0, 1}

    *** WARNING: Unable to verify timestamp for avgidsdrivera.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
    Probably caused by : avgidsdrivera.sys ( avgidsdrivera+1944d )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    INVALID_KERNEL_HANDLE (93)
    This message occurs if kernel code attempts to close or reference a handle
    that is not a valid handle.  Only invalid or protected handles passed to NtClose
    will cause this bugcheck, unless bad handle detection is enabled.
    Arguments:
    Arg1: 0000000000000000, The handle that was referenced
    Arg2: fffff8a0000017c0,
    Arg3: 0000000000000000
    Arg4: 0000000000000001, The error occurred referencing an invalid kernel handle and
        bad handle detection was enabled.

    Debugging Details:
    ------------------


    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    • Marked as answer by Leo Huang Friday, April 12, 2013 9:03 AM
    Saturday, April 6, 2013 7:09 AM

All replies

  • Pretty sure you guys will need the Skydrive thingy so here it is!

    https://skydrive.live.com/redir?resid=23DDF6A02F722F2F!107&authkey=!AO_liMBejSqXZDA

    https://skydrive.live.com/redir?resid=23DDF6A02F722F2F!108&authkey=!AGo4bMfa21MIpLU

    Thursday, April 4, 2013 8:32 AM
  • And we have another!

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.768.3
      Locale ID:    2057

    Additional information about the problem:
      BCCode:    4e
      BCP1:    0000000000000099
      BCP2:    0000000000156DCD
      BCP3:    0000000000000002
      BCP4:    0000000000156DC7
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    768_1

    Files that help describe the problem:
      C:\Windows\Minidump\040413-42806-01.dmp
      C:\Users\Mo\AppData\Local\Temp\WER-67532-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    https://skydrive.live.com/redir?resid=23DDF6A02F722F2F!109&authkey=!AOUbCpguS-veOx0

    Thursday, April 4, 2013 10:13 AM
  • Dualerz

     These crashes were caused by memory corruption (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem.  

    *Dont forget to upload any further DMP files (especially those when verifier is running)

    *If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!   If you dont know what this means you probably arent


    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org 
    *Boot from the CD, and leave it running for at least 5 or 6 passes.
    *Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
    *Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.
    If a known good stick fails in a motherboard slot it is probably the slot.


    2-Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

    *But sometimes it'll crash and won't tell you the driver.
    *Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
    *I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
    *Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Here is the procedure:

    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    *Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.
    *Reboot the system and wait for it to crash to the Blue Screen.
    *Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
    *If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    *If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    *Further Reading
    http://support.microsoft.com/kb/244617

    Be sure to make a system restore point (or a backup) just in case.


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    Thursday, April 4, 2013 3:59 PM
  • option 1 revealed nothing at all,

    So i proceeded to step 2, and about 18hours later it crashed but i have no clue how it was meant to communicate what driver was busted if any.  Was i not allowed to put my laptop into sleep mode? And should i just start all over again?

    Friday, April 5, 2013 4:06 PM
  • It crashed because it was supposed to.  Upload the DMP and we may be able to tell you why

    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    Saturday, April 6, 2013 2:22 AM
  • removed

    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com


    • Edited by ZigZag3143x Saturday, April 6, 2013 5:45 AM
    Saturday, April 6, 2013 5:44 AM
  • Here ya go

    https://skydrive.live.com/redir?resid=23DDF6A02F722F2F!110&authkey=!AOan835HrJFsb3o

    Btw Thanks a lot for the help, it truly is appreciated =)

    Saturday, April 6, 2013 6:30 AM
  • Dualerz

    My pleasure.  I started doing BSOD's because I was getting them so often I had to learn how to stop them

    This one crash was Related to AVGIDSDriver.sys IDS Application Activity Monitor Driver. from AVG Technologies.

    I would remove and replace with Microsoft Security Essentials

    AVG  can be a contributing cause of BSOD'S.
    Please remove and replace with Microsoft Security Essentials at least to test.

    BugCheck 93, {0, fffff8a0000017c0, 0, 1}

    *** WARNING: Unable to verify timestamp for avgidsdrivera.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
    Probably caused by : avgidsdrivera.sys ( avgidsdrivera+1944d )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    INVALID_KERNEL_HANDLE (93)
    This message occurs if kernel code attempts to close or reference a handle
    that is not a valid handle.  Only invalid or protected handles passed to NtClose
    will cause this bugcheck, unless bad handle detection is enabled.
    Arguments:
    Arg1: 0000000000000000, The handle that was referenced
    Arg2: fffff8a0000017c0,
    Arg3: 0000000000000000
    Arg4: 0000000000000001, The error occurred referencing an invalid kernel handle and
        bad handle detection was enabled.

    Debugging Details:
    ------------------


    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    • Marked as answer by Leo Huang Friday, April 12, 2013 9:03 AM
    Saturday, April 6, 2013 7:09 AM