locked
BSOD WINDOWS 7 problem recurring? RRS feed

  • Question

  • Recurring everyday begins to be anoying and it makes a noise like ATARI 8 bits noise you know it is strange because on the old PC never had the noisy sound it comes from above Ram memory and under the battery here are some details from the memory craash dump : 

    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 4105

    Additional information about the problem:
    BCCode: 1a
    BCP1: 0000000000005002
    BCP2: FFFFF70001080000
    BCP3: 0000000000001955
    BCP4: 8000194BFFFFFFFE
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\081113-25724-01.dmp
    C:\Users\WAEL\AppData\Local\Temp\WER-980…

    http://www.mediafire.com/?zz76jfjat7amq7s

    Sunday, August 11, 2013 6:22 AM

Answers

  • latest dump still shows memory issues:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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.
    Arguments:
    Arg1: fffffa8016ae6010, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80003595ca6, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003710100
    GetUlongFromAddress: unable to read from fffff800037101c0
     fffffa8016ae6010 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`03595ca6 480fb328        btr     qword ptr [rax],rbp
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  taskhost.exe
    
    ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre
    
    TRAP_FRAME:  fffff8800b9a3f40 -- (.trap 0xfffff8800b9a3f40)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8006ae6010 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003595ca6 rsp=fffff8800b9a40d0 rbp=0000000080000000
     r8=fffff8800b9a4100  r9=00000000ffffffff r10=ffffffffffffffff
    r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiReleaseConfirmedPageFileSpace+0x86:
    fffff800`03595ca6 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`06ae6010=ffffffffffdfffff
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800034d81a9 to fffff800034d8c00
    
    STACK_TEXT:  
    nt!KeBugCheckEx
    nt!KiBugCheckDispatch
    nt!KiPageFault
    nt!MiReleaseConfirmedPageFileSpace
    nt! ?? ::FNODOBFM::`string'
    nt!NtFreeVirtualMemory
    nt!KiSystemServiceCopyEnd
    0x0
    
    
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!mireleaseconfirmedpagefilespace+86
    
    

    Because of mireleaseconfirmedpagefilespace also do a chkdsk.


    "A programmer is just a tool which converts caffeine into code"

    Sunday, August 11, 2013 6:18 PM

All replies

  • The dump Shows RAM issues:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005002, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 0000000000001955
    Arg4: 8000194bfffffffe
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_5002
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88009f4f800 -- (.trap 0xfffff88009f4f800)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0000000003c70000
    rdx=fffffa800915f720 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800035a6145 rsp=fffff88009f4f990 rbp=fffff88009f4fb60
     r8=0000000000000000  r9=000000000000195b r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    nt!NtLockVirtualMemory+0x305:
    fffff800`035a6145 8b01            mov     eax,dword ptr [rcx] ds:00000000`03c70000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800034ff1be to fffff8000348ac00
    
    STACK_TEXT:  
    nt!KeBugCheckEx
    nt! ?? ::FNODOBFM::`string'
    nt!MmAccessFault
    nt!KiPageFault
    nt!NtLockVirtualMemory
    nt!KiSystemServiceCopyEnd
    0x0
    

    Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2][3] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If memtest86+ detects errors, test each module its own and replace the faulty RAM.

    If the memtest tells no error, please download CPU-Z [4], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    André

    [1] http://www.memtest.org/download/4.20/memtest86+-4.20.iso.zip
    [2] http://www.imgburn.com/index.php?act=download
    [3] http://forum.imgburn.com/index.php?showtopic=61
    [4] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code"

    • Proposed as answer by Andre.Ziegler Monday, August 12, 2013 7:44 PM
    Sunday, August 11, 2013 7:39 AM
  • the memtest showed alot of red lines and errors. I flooded the ram till 3.7GB and bsod happens, then tried it again and nothing happened the ram works just fine I updated all of the drivers. also run a chk check and an antivirus complete scan it seems then the problem is solved but no it would've decreased of times happening only, here are some other dumps and I hope not to make a supercharge for you and thank you for your time andré : 

    http://www.mediafire.com/?vrbzqkobbexvb11

    Sunday, August 11, 2013 3:41 PM
  • latest dump still shows memory issues:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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.
    Arguments:
    Arg1: fffffa8016ae6010, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80003595ca6, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003710100
    GetUlongFromAddress: unable to read from fffff800037101c0
     fffffa8016ae6010 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`03595ca6 480fb328        btr     qword ptr [rax],rbp
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  taskhost.exe
    
    ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre
    
    TRAP_FRAME:  fffff8800b9a3f40 -- (.trap 0xfffff8800b9a3f40)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8006ae6010 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003595ca6 rsp=fffff8800b9a40d0 rbp=0000000080000000
     r8=fffff8800b9a4100  r9=00000000ffffffff r10=ffffffffffffffff
    r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiReleaseConfirmedPageFileSpace+0x86:
    fffff800`03595ca6 480fb328        btr     qword ptr [rax],rbp ds:fffffa80`06ae6010=ffffffffffdfffff
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800034d81a9 to fffff800034d8c00
    
    STACK_TEXT:  
    nt!KeBugCheckEx
    nt!KiBugCheckDispatch
    nt!KiPageFault
    nt!MiReleaseConfirmedPageFileSpace
    nt! ?? ::FNODOBFM::`string'
    nt!NtFreeVirtualMemory
    nt!KiSystemServiceCopyEnd
    0x0
    
    
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!mireleaseconfirmedpagefilespace+86
    
    

    Because of mireleaseconfirmedpagefilespace also do a chkdsk.


    "A programmer is just a tool which converts caffeine into code"

    Sunday, August 11, 2013 6:18 PM
  • Hi Weals,

    Please use SkyDrive to upload collected files and post screen shot/picture.
    http://social.technet.microsoft.com/Forums/windows/en-US/4fc10639-02db-4665-993a-08d865088d65/use-skydrive-to-upload-collected-files-and-post-screen-shotpicture-updated-1162012/

    I would like to suggest you update graphic card driver and test the issue in Safe Mode.
    Advanced startup options (including safe mode):  http://windows.microsoft.com/en-US/windows7/Advanced-startup-options-including-safe-mode

    You may also refer to:
    Resolving stop (blue screen) errors in Windows 7
    http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

    Regards,

    Blair Deng


    blair deng

    TechNet Community Support

    Blair, I think it's fine to ask people to use SkyDrive (versus Mediafire), but I don't think those links are relevant to this topic. I think Andre is on top of it.

    We'll take this offline some more.

    Thanks!


    Ed Price, SQL Server Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Tuesday, August 13, 2013 5:10 PM