BSOD Windows 7 Professional 64bit


  1. Posts : 2
    Windows 7 Professional 64-bit
       #1

    BSOD Windows 7 Professional 64bit


    Hi everyone!

    In the last month I've been getting BSOD a couple of times a week. I've updated my drivers hoping it would solve the problem but it hasn't.

    My computer just crashed again and Windows was already set to create a kernel memory dump so I'm uploading it, just tell me if I need to create a complete memory dump, I can upload it next time it crashes.

    I'm hoping someone can tell me why it's crashing!
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Hi -

    Welcome to SevenForums.
    Code:
    Start Menu\Programs\Avira    Public:Start Menu\Programs\Avira    Public
    Start Menu\Programs\Avira\Avira Desktop    Public:Start Menu\Programs\Avira\Avira Desktop    Public
    Avira contributes in BSOD's. Please remove it using its removal tool from here: Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

    We recommended Microsoft Security Essentials from a strict BSOD perspective. Is most compatible & provides best stability compared to other Antivirus App/Internet Security Software.

       Warning
    Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

    Run a full scan with both (separately) once downloaded, installed and updated.

    Make scans with the following as well:

    -Kaspersky TDSSKiller

    -ESET online scanner

    Perform a System File Check to check the integrity of all protected Windows 7 :
    1. Click on the start
    2. Type CMD on Search
    3. Left click and Run as Administrator
    4. Type
      Code:
      SFC /scannow

    Full tutorial:

    Check your hard drive(s) for errors by running chkdsk


    Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

    If the above does not bring stability test your Hard drive and RAM:
    Upload a screenshot of your hard disk using CrystalDiskInfo:


    Make a hard drive test from the hard drive manufacturers website:

    Hard drive test both short and long with:

    DOS version of Seatools:

    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.


       Note
    Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.

    If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:

    You need to update the BIOS:
    Your BIOS dates from 2008. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.
    Code:
    BIOS Version/Date    Award Software International, Inc. F1, 18.8.2008.
    Let us know the results and further BSOD reports.

    BSOD Analyse

    Code:
    **************************Fri Mar  8 15:47:33.496 2013 (UTC + 6:00)**************************
    Loading Dump File [C:\Users\Yusra\Downloads\haPPy00\SF_08-03-2013\030813-15600-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    System Uptime: 0 days 0:00:49.104
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiRemoveWorkingSetPages+388 )
    BugCheck 50, {fffff69a1697a2c8, 0, fffff80002c563d0, 5}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, 
    Antivirus,  Device driver, NTFS corruption, BIOS
    Arguments:
    Arg1: fffff69a1697a2c8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002c563d0, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    BUGCHECK_STR: 0x50
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: avguard.exe
    FAILURE_BUCKET_ID: X64_0x50_nt!MiRemoveWorkingSetPages+388
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2800
    
      BIOS Version           F1
      BIOS Release Date   08/18/2008
      Manufacturer          Gigabyte Technology Co., Ltd.
      Product Name         EP45-DS3LR
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Mar  1 02:36:34.314 2013 (UTC + 6:00)**************************
    Loading Dump File [C:\Users\Yusra\Downloads\haPPy00\SF_08-03-2013\022813-15709-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    System Uptime: 0 days 9:29:27.797
    GetPointerFromAddress: unable to read from fffff80002f0b100
    GetUlongFromAddress: unable to read from fffff80002f0b1c0
    Probably caused by : ntkrnlmp.exe ( nt!IopPostProcessIrp+4d )
    BugCheck 19, {20, fffffa800566e620, fffffa800566e670, 4050002}
    BugCheck Info: BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Usual causes:  Device driver
    Arguments:
    Arg1: 0000000000000020, a pool block header size is corrupt.
    Arg2: fffffa800566e620, The pool entry we were looking for within the page.
    Arg3: fffffa800566e670, The next pool entry.
    Arg4: 0000000004050002, (reserved)
    BUGCHECK_STR: 0x19_20
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: firefox.exe
    FAILURE_BUCKET_ID: X64_0x19_20_nt!IopPostProcessIrp+4d
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2800
    
      BIOS Version           F1
      BIOS Release Date   08/18/2008
      Manufacturer          Gigabyte Technology Co., Ltd.
      Product Name         EP45-DS3LR
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Feb 20 21:07:05.306 2013 (UTC + 6:00)**************************
    Loading Dump File [C:\Users\Yusra\Downloads\haPPy00\SF_08-03-2013\022013-16317-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    System Uptime: 0 days 0:00:14.929
    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
    BugCheck 1E, {ffffffffc0000005, fffff80002ce4240, 0, ffffffffffffffff}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002ce4240, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    BUGCHECK_STR: 0x1E_c0000005_R
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: nvvsvc.exe
    FAILURE_BUCKET_ID: X64_0x19_20_nt!IopPostProcessIrp+4d
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2800
    
      BIOS Version           F1
      BIOS Release Date   08/18/2008
      Manufacturer          Gigabyte Technology Co., Ltd.
      Product Name         EP45-DS3LR
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Feb 20 22:57:42.796 2013 (UTC + 6:00)**************************
    Loading Dump File [C:\Users\Yusra\Downloads\haPPy00\SF_08-03-2013\022013-15678-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    System Uptime: 0 days 0:00:28.419
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )
    BugCheck 1A, {41284, 66a2001, 5dd3, fffff70001080000}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Usual causes:  Device driver, memory, kernel
    Arguments:
    Arg1: 0000000000041284, A PTE or the working set list is corrupt.
    Arg2: 00000000066a2001
    Arg3: 0000000000005dd3
    Arg4: fffff70001080000
    BUGCHECK_STR: 0x1a_41284
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: avguard.exe
    FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2800
    
      BIOS Version           F1
      BIOS Release Date   08/18/2008
      Manufacturer          Gigabyte Technology Co., Ltd.
      Product Name         EP45-DS3LR
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Feb 17 21:27:17.524 2013 (UTC + 6:00)**************************
    Loading Dump File [C:\Users\Yusra\Downloads\haPPy00\SF_08-03-2013\021713-13182-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    System Uptime: 0 days 0:05:23.132
    Probably caused by : Ntfs.sys ( Ntfs!NtfsQueryDirectory+1c79 )
    BugCheck 24, {1904fb, fffff8800c2618d8, fffff8800c261130, fffff880014d7d83}
    BugCheck Info: NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
    Arguments:
    Arg1: 00000000001904fb
    Arg2: fffff8800c2618d8
    Arg3: fffff8800c261130
    Arg4: fffff880014d7d83
    BUGCHECK_STR: 0x24
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: update.exe
    FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsQueryDirectory+1c79
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2800
    
      BIOS Version           F1
      BIOS Release Date   08/18/2008
      Manufacturer          Gigabyte Technology Co., Ltd.
      Product Name         EP45-DS3LR
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Feb  3 00:24:06.212 2013 (UTC + 6:00)**************************
    Loading Dump File [C:\Users\Yusra\Downloads\haPPy00\SF_08-03-2013\020213-13587-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    System Uptime: 0 days 1:40:56.835
    Probably caused by : win32k.sys ( win32k!xxxInternalDoPaint+af )
    BugCheck 3B, {c0000005, fffff96000076e9f, fffff8800a4a3eb0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff96000076e9f, Address of the instruction which caused the bugcheck
    Arg3: fffff8800a4a3eb0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Usual causes: System service, Device driver, graphics driver, ?memory
    BUGCHECK_STR: 0x3B
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: firefox.exe
    FAILURE_BUCKET_ID: X64_0x3B_win32k!xxxInternalDoPaint+af
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2800
    
      BIOS Version           F1
      BIOS Release Date   08/18/2008
      Manufacturer          Gigabyte Technology Co., Ltd.
      Product Name         EP45-DS3LR
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Jan 23 21:08:26.289 2013 (UTC + 6:00)**************************
    Loading Dump File [C:\Users\Yusra\Downloads\haPPy00\SF_08-03-2013\012313-41511-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    System Uptime: 1 days 5:59:35.896
    *** WARNING: Unable to verify timestamp for netr7364.sys
    *** ERROR: Module load completed but symbols could not be loaded for netr7364.sys
    Probably caused by : netr7364.sys ( netr7364+680b )
    BugCheck 7F, {8, 80050031, 406f8, fffff8800725480b}
    BugCheck Info: UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000406f8
    Arg4: fffff8800725480b
    Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
    BUGCHECK_STR: 0x7f_8
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    PROCESS_NAME: 
    FAILURE_BUCKET_ID:  
    CPUID:        "Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2800
    
      BIOS Version           F1
      BIOS Release Date   08/18/2008
      Manufacturer          Gigabyte Technology Co., Ltd.
      Product Name         EP45-DS3LR
    Last edited by koolkat77; 08 Mar 2013 at 06:35. Reason: Analysis
      My Computer


  3. Posts : 2
    Windows 7 Professional 64-bit
    Thread Starter
       #3

    Thank you for a quick response, I will do as you say!
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    No problem, I suspect your RAM since crashes are all over the place. Look forward to the results.
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #5

    Have you got your BSOD problems sorted?
      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 20:19.
Find Us