BSOD randomly appears, mostly while playing games or browsing the net


  1. Posts : 1
    Windows 7 Professional x64
       #1

    BSOD randomly appears, mostly while playing games or browsing the net


    Sometimes crash my current browsing on internet browser (Google Chrome) too, and ask me for refresh/restore on "blue screen"(or purple?), but I dont know if it has something to do with it. OS has been reinstalled three days ago because of the viruses, but BSODs had appeared even before. I could not install any of the win7s x64 because of some error in the middle of the installation but win7s x86 installation works fine. Then I tried to pull out one of the RAMs and installation of win7 x64 completed successfully, but again I dont know if it has something to do with it. I hope it will help with diagnosing the BSOD problem. I really appreciate any help you can provide and sorry for my english.
      My Computer


  2. Posts : 3,056
    Windows 10
       #2

    Welcome to SF David1222 :) .
    I have a few things I want to clear up if I may.

    David1222 said:
    OS has been reinstalled three days ago because of the viruses
    How confident are you that the OS is currently clean?
    Were files saved from the previous installation and transferred onto the new install, or was the HDD
    completely wiped without backing up anything?

    I wish there were more bug checks to look at as it will help in establishing a pattern, if nothing else.
    Please manually check the minidump folder.
    Code:
    C:\Windows\minidump
    If dump files are present in that folder copy them to the Desktop, zip and upload in your next post.

    The single bug check uploaded is 0x19, the most common issue with those is drivers,
    looking at the stack we see the activity coming from fltmgr and fileinfo which are Filter Drivers
    being used, in this case, by BitDefender.

    Code:
    BugCheck 19, {3, fffffa80069956f0, fffffac0069956f0, fffffa80069956f0}
    
    *** WARNING: Unable to verify timestamp for gzflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for gzflt.sys
    Probably caused by : gzflt.sys ( gzflt+23700 )
    
    
    0xfffff8800bdb01c8 : 0xfffff88000f9c953 : FLTMGR!FltPerformSynchronousIo+0x2d3
    0xfffff8800bdb01d8 : 0xfffff80002ed4d3c : nt!IopFreeIrp+0x11c
    0xfffff8800bdb0248 : 0xfffff88000fa2ee7 : FLTMGR!ExAllocateFromPagedLookasideList+0x27
    0xfffff8800bdb0278 : 0xfffff88000fa54fb : FLTMGR!FltAllocateContext+0xdb
    *** WARNING: Unable to verify timestamp for avc3.sys
    *** ERROR: Module load completed but symbols could not be loaded for avc3.sys
    0xfffff8800bdb03d8 : 0xfffff880010efbb7 : fileinfo!FIStreamSetFileInfo+0x15b
    0xfffff8800bdb0448 : 0xfffff880010ef3c8 : fileinfo!FIStreamGetInfo+0x17c
    0xfffff8800bdb0498 : 0xfffff880010e840b : fileinfo!FIPfFileFSOpPostCallbackCleanup+0x197
    0xfffff8800bdb04a0 : 0xfffff88000faaa00 : FLTMGR!FltpOperationFlags
    0xfffff8800bdb04e0 : 0xfffff88000faaa00 : FLTMGR!FltpOperationFlags
    0xfffff8800bdb0520 : 0xfffff88000faaa00 : FLTMGR!FltpOperationFlags
    0xfffff8800bdb0528 : 0xfffff88000fa031a : FLTMGR!FltpCompleteCompletionNode+0x3a
    0xfffff8800bdb0558 : 0xfffff88000f9b242 : FLTMGR!FltpPerformPostCallbacks+0x392
    0xfffff8800bdb05f0 : 0xfffff88000faaa00 : FLTMGR!FltpOperationFlags
    0xfffff8800bdb0628 : 0xfffff88000f9a38b : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x39b
    0xfffff8800bdb0688 : 0xfffff88000f9b8ca : FLTMGR!FltpPassThroughInternal+0x4a
    0xfffff8800bdb06b8 : 0xfffff88000fb92b9 : FLTMGR!FltpCreate+0x2a9
    0xfffff8800bdb06f8 : 0xfffff88000f9b962 :  !du "$Volume"
    0xfffff8800bdb0758 : 0xfffff800031c3560 : nt!IopParseDevice
    0xfffff8800bdb0778 : 0xfffff800031c3560 : nt!IopParseDevice
    0xfffff8800bdb0868 : 0xfffff800031ba2c4 : nt!ObpLookupDirectoryEntry+0x274
    0xfffff8800bdb08c8 : 0xfffff800031b9784 : nt!ObpLookupObjectName+0x585
    0xfffff8800bdb0938 : 0xfffff800031b10a5 : nt!SeCreateAccessStateEx+0xa5
    0xfffff8800bdb09c8 : 0xfffff800031be45d : nt!ObOpenObjectByName+0x1cd
    0xfffff8800bdb0a78 : 0xfffff800031c6597 : nt!IopCreateFile+0x2b7
    0xfffff8800bdb0a90 : 0xfffff88000fb9401 : FLTMGR!FltpCreate+0x3f1
    0xfffff8800bdb0ab8 : 0xfffff800031df55c : nt!NtReadFile+0x4da
    0xfffff8800bdb0b18 : 0xfffff800031d0350 : nt!NtCreateFile+0x78


    I recommend scanning the system and test the HDD.

       Warning
    The Following Method Should NOT Be Performed On An SSD!
    Testing the HDD:

    1. Perform a Disk Check | Disk Check- Scroll down to OPTION TWO of the tutorial and use the /R switch in the CHKDSK command | chkdsk C: /R.
    2. Then Post the Disk Check results following | This Tutorial.
    3. Once back in Windows, download Crystal Disk Info and post a screenshot (multiple shots if you have more than one drive).
    4. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
    5. If SeaTools for DOS is unable to recognize your HDD:
    6. Visit HDDdiag and follow the instructions | Or follow the instructions below.

    If SeaTools For DOS does not recognize the drive;
    Boot into the BIOS using the *Fx key.
    Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
    It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
    Set it to IDE then save and exit usually by pressing the F10 key.
    Now boot into SeaTools and it should detect the drives.
    Start the Long Test and let it run.
    Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
    and change the SATA setting back to what it was in the first place.




    Please scan for possible infection and file corruption:


    (*Kaspersky Rescue CD from a USB thumbdrive)



    David1222 said:
    I could not install any of the win7s x64 because of some error in the middle of the installation but win7s x86 installation works fine. Then I tried to pull out one of the RAMs and installation of win7 x64 completed successfully
    Do you happen to remember what the error was?
    This to me is raises a red-flag concerning the RAM / Slot.

    Please Test the RAM.

    Testing the RAM:

    koolkat77 said:
    Test and Diagnose RAM Issues with Memtest86+:

       Tip

    • Pay close attention to part 3 of the tutorial "If you have errors"
    • Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

    When done with the testing procedure take a picture and upload it here.

    This will help you to determine where the issue is origination from (if any):
    Arc said:
    First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

    But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

    How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
    How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
    No code has to be inserted here. It is a RAM, a bad RAM.

    But if you have got a result like that:
    No code has to be inserted here. It is a motherboard issue. The particular slot is bad.
      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 02:33.
Find Us