BSOD randomly with my new computer

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 Ultimate x64
       #1

    BSOD randomly with my new computer


    After switching to this new computer, I have had quite a few BSOD, first here is my specs:

    Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
    8.00 GB RAM
    NVIDIA GeForce GTX 560 Ti
    Display driver version: 8.17.12.8566

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1a
    BCP1: 0000000000005002
    BCP2: FFFFF70001080000
    BCP3: 000000000000E643
    BCP4: 8000E644FFFFFFFE
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\091612-5928-01.dmp
    C:\Windows\Temp\WER-8595-0.sysdata.xml


    and


    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: a
    BCP1: FFFFFA8018E6E010
    BCP2: 0000000000000002
    BCP3: 0000000000000001
    BCP4: FFFFF80003192366
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\091712-6442-01.dmp
    C:\Windows\Temp\WER-9063-0.sysdata.xml




    I don't know what exactly trigger this BSOD since it's random, please help !
      My Computer


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

    Please upload the dumps following:
    https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


  3. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #3

    OK, here.
      My Computer


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

    Thanks.

    If you are overclocking any hardware, please stop.

    Bug checks:
    1. STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL BSOD Index Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
    2. STOP 0x0000001A: MEMORY_MANAGEMENT BSOD Index Usual causes: Device driver, memory, kernel
    3. STOP 0x00000019: BAD_POOL_HEADER BSOD Index Usual causes: Device driver

    Code:
    Start Menu\Programs\ASRock Utility	Public:Start Menu\Programs\ASRock Utility	Public
    Start Menu\Programs\avast! Free Antivirus	Public:Start Menu\Programs\avast! Free Antivirus	Public
    Suggestions:
    Recommend removing your ASRock utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability. They are also not needed for the system to function properly and may reduce system resources.

    Please uninstall Avast! antivirus and keep MSE while we troubleshoot with your computer.
    Microsoft Security Essentials - Free Antivirus for Windows

    After uninstalling these, run memtest86+ on each stick for 8 passes preferably overnight:
    RAM - Test with Memtest86+

    Post back results

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {3, fffff8a01b4f6260, 7ffff8a01b4f6260, fffff8a01b4f6260}
    
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )
    
    Followup: Pool_corruption
    ---------
    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.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {5002, fffff70001080000, e643, 8000e644fffffffe}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+464b8 )
    
    Followup: MachineOwner
    ---------
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffa8018e6e010, 2, 1, fffff80003192366}
    
    Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )
    
    Followup: MachineOwner
    ---------
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
      My Computer


  5. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Well, I deleted all ASROCK motherboard utilities on my computer and let it run for a day and it still gave me BSOD, so I downloaded this memtest86+ and scanned my RAM pass twice, and it gave me 211,xxx amount of errors, it's a pair of brand new G.SKILL RIP JAWS, so this is a hardware defect and cannot be fixed with software right?
      My Computer


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

    oOMeowthOo said:
    Well, I deleted all ASROCK motherboard utilities on my computer and let it run for a day and it still gave me BSOD, so I downloaded this memtest86+ and scanned my RAM pass twice, and it gave me 211,xxx amount of errors, it's a pair of brand new G.SKILL RIP JAWS, so this is a hardware defect and cannot be fixed with software right?

    Yes you're right although overclocking does create problem sometimes.
      My Computer


  7. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Here is another thing I observed, when I install games, it always say files corrupted or missing, and I believe nothing is wrong with the game itself. Is the defective RAM causing this problem as well?
      My Computer


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

    Could be. Do you have a friend or neighbor to borrow ram to test on your pc?
      My Computer


  9. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #9

    I just took someone's RAM and snap it on my computer, then when I install games, it doesn't have files corruption anymore, also the one who switch with my RAM now experience what I suffer during the past few weeks where FireFox crash frequently, but anyways now I know what is wrong with my computer.
      My Computer


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

    oOMeowthOo said:
    I just took someone's RAM and snap it on my computer, then when I install games, it doesn't have files corruption anymore, also the one who switch with my RAM now experience what I suffer during the past few weeks where FireFox crash frequently, but anyways now I know what is wrong with my computer.
    Great!

    So what have you decided now? And do you want to keep this thread open for more troubleshooting?

    Keep us posted :)
      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 06:30.
Find Us