BSOD at "random": 0x1a, 0x50, 0x3b ntoskrnl.exe+7cc80

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 Home Premium x64
       #1

    BSOD at "random": 0x1a, 0x50, 0x3b ntoskrnl.exe+7cc80


    I have been running into BSOD's on my new computer and just can't seem to figure out what the problem is. I say random in that I can't find a trigger, sometimes I can play skyrim for hours without a BSOD, other times just opening explorer results in an issue.

    Computer is a ASUS g74sx-dh72, running Window 7 home premium with all updates installed.

    System has passed repeated memtest's though if run immediately after a crash sometimes says that manufactures should be contacted. Otherwise testing sticks in any configuration results in a pass.

    Any help would be greatly appreciated and I'm open to any suggestions.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    Your AVG Antivirus is the main culprit, remove it and use MSE

    Other Dumps point to a Memory Management issue/Memory Corruption, this indicates a possible RAM Defect.
    Run Memtest86+ for at least 7 passes.
    RAM - Test with Memtest86+

    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
    You can use MagicDisc as an alternative.
    Code:
    sptd.sys        fffff880`01005000    fffff880`01178000    0x00173000    0x4f524ac0    03/03/2012 20:45:52
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffac00b05ee08, 0, fffff80002f14fe8, 5}
    
    Unable to load image \SystemRoot\system32\DRIVERS\avgidsfiltera.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgidsfiltera.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgidsfiltera.sys
    
    Could not read faulting driver name
    Probably caused by : fileinfo.sys ( fileinfo!FIStreamGet+52 )
    
    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.
    Arguments:
    Arg1: fffffac00b05ee08, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002f14fe8, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fe100
     fffffac00b05ee08 
    
    FAULTING_IP: 
    nt!FsRtlLookupPerStreamContextInternal+7c
    fffff800`02f14fe8 48396810        cmp     qword ptr [rax+10h],rbp
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  avgidsagent.ex
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88006cef040 -- (.trap 0xfffff88006cef040)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffac00b05edf8 rbx=0000000000000000 rcx=fffff8a0116fd728
    rdx=0000000000000011 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f14fe8 rsp=fffff88006cef1d0 rbp=fffffa8007004800
     r8=0000000000000000  r9=fffff88006cef2a0 r10=0000000000000000
    r11=fffff88006cef1c0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!FsRtlLookupPerStreamContextInternal+0x7c:
    fffff800`02f14fe8 48396810        cmp     qword ptr [rax+10h],rbp ds:f000:fffffac0`0b05ee08=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e77c1f to fffff80002eccc80
    
    STACK_TEXT:  
    fffff880`06ceeed8 fffff800`02e77c1f : 00000000`00000050 fffffac0`0b05ee08 00000000`00000000 fffff880`06cef040 : nt!KeBugCheckEx
    fffff880`06ceeee0 fffff800`02ecadae : 00000000`00000000 fffffac0`0b05ee08 fffff8a0`0d59fc00 fffff8a0`116fd6f0 : nt! ?? ::FNODOBFM::`string'+0x43d41
    fffff880`06cef040 fffff800`02f14fe8 : fffff6fc`00000000 fffff8a0`116fd6f0 fffffa80`07004800 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`06cef1d0 fffff880`00d8daae : fffffa80`0badcf20 fffff880`06cef330 fffffa80`07004800 fffff880`012229f4 : nt!FsRtlLookupPerStreamContextInternal+0x7c
    fffff880`06cef210 fffff880`00d98da1 : fffffa80`07004800 fffff880`01224e84 fffffa80`09094010 00000000`00000001 : fltmgr!FltpGetStreamListCtrl+0x8e
    fffff880`06cef270 fffff880`00e62052 : 00000000`00000000 fffff140`117d5887 fffff880`06cef4c0 fffff880`012bdbd8 : fltmgr!FltGetStreamContext+0x21
    fffff880`06cef2a0 fffff880`00e60b07 : fffff140`117d5887 00000000`00000000 00000000`00000000 00000000`00000000 : fileinfo!FIStreamGet+0x52
    fffff880`06cef310 fffff880`00d8d288 : 00000000`00000000 00000000`00000000 fffffa80`090713b0 00000000`00000000 : fileinfo!FIPostCreateCallback+0xf3
    fffff880`06cef3a0 fffff880`00d8bd1b : fffffa80`07293030 fffffa80`0bb34e80 fffffa80`06f92bb0 fffffa80`06f92dd0 : fltmgr!FltpPerformPostCallbacks+0x368
    fffff880`06cef470 fffff880`00dab2b9 : fffffa80`09071010 fffffa80`07004800 fffffa80`09071000 fffffa80`06f02900 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x39b
    fffff880`06cef500 fffff880`02ba832b : fffffa80`090713f8 fffff800`02ee2dbf fffffa80`097ea060 00000000`00000000 : fltmgr!FltpCreate+0x2a9
    fffff880`06cef5b0 fffffa80`090713f8 : fffff800`02ee2dbf fffffa80`097ea060 00000000`00000000 fffffa80`0badcf20 : avgidsfiltera+0x332b
    fffff880`06cef5b8 fffff800`02ee2dbf : fffffa80`097ea060 00000000`00000000 fffffa80`0badcf20 fffffa80`09071010 : 0xfffffa80`090713f8
    fffff880`06cef5c0 fffff800`031c9d35 : 00000000`00000005 fffffa80`0ba73708 fffffa80`0973c010 fffffa80`0badcfb8 : nt!RtlCopyUnicodeString+0x3f
    fffff880`06cef5f0 fffff800`031c65d8 : fffffa80`06ee4c50 fffff800`00000000 fffffa80`0ba73550 00000000`00000001 : nt!IopParseDevice+0x5a5
    fffff880`06cef780 fffff800`031c77f6 : 00000000`00000000 fffffa80`0ba73550 fffffa80`06f02900 fffffa80`06739c90 : nt!ObpLookupObjectName+0x588
    fffff880`06cef870 fffff800`031c90fc : 00000000`00000400 00000000`00000000 fffffa80`0badce01 fffff880`06cef958 : nt!ObOpenObjectByName+0x306
    fffff880`06cef940 fffff800`031b4924 : 00000000`03aae498 fffff8a0`00000080 00000000`03aaecf0 00000000`03aae438 : nt!IopCreateFile+0x2bc
    fffff880`06cef9e0 fffff800`02ecbf13 : fffffa80`09c54060 00000000`00000001 fffffa80`0991f060 fffff800`031c3294 : nt!NtOpenFile+0x58
    fffff880`06cefa70 00000000`77ad164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`03aae3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ad164a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    fileinfo!FIStreamGet+52
    fffff880`00e62052 8bd8            mov     ebx,eax
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  fileinfo!FIStreamGet+52
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: fileinfo
    
    IMAGE_NAME:  fileinfo.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc481
    
    FAILURE_BUCKET_ID:  X64_0x50_fileinfo!FIStreamGet+52
    
    BUCKET_ID:  X64_0x50_fileinfo!FIStreamGet+52
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 6
    Windows 7 Home Premium x64
    Thread Starter
       #3

    yowanvista said:
    Your AVG Antivirus is the main culprit, remove it and use MSE

    Other Dumps point to a Memory Management issue/Memory Corruption, this indicates a possible RAM Defect.
    Run Memtest86+ for at least 7 passes.
    RAM - Test with Memtest86+

    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
    You can use MagicDisc as an alternative.
    Code:
    sptd.sys        fffff880`01005000    fffff880`01178000    0x00173000    0x4f524ac0    03/03/2012 20:45:52
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffac00b05ee08, 0, fffff80002f14fe8, 5}
    
    Unable to load image \SystemRoot\system32\DRIVERS\avgidsfiltera.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgidsfiltera.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgidsfiltera.sys
    
    Could not read faulting driver name
    Probably caused by : fileinfo.sys ( fileinfo!FIStreamGet+52 )
    
    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.
    Arguments:
    Arg1: fffffac00b05ee08, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002f14fe8, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fe100
     fffffac00b05ee08 
    
    FAULTING_IP: 
    nt!FsRtlLookupPerStreamContextInternal+7c
    fffff800`02f14fe8 48396810        cmp     qword ptr [rax+10h],rbp
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  avgidsagent.ex
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88006cef040 -- (.trap 0xfffff88006cef040)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffac00b05edf8 rbx=0000000000000000 rcx=fffff8a0116fd728
    rdx=0000000000000011 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f14fe8 rsp=fffff88006cef1d0 rbp=fffffa8007004800
     r8=0000000000000000  r9=fffff88006cef2a0 r10=0000000000000000
    r11=fffff88006cef1c0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!FsRtlLookupPerStreamContextInternal+0x7c:
    fffff800`02f14fe8 48396810        cmp     qword ptr [rax+10h],rbp ds:f000:fffffac0`0b05ee08=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e77c1f to fffff80002eccc80
    
    STACK_TEXT:  
    fffff880`06ceeed8 fffff800`02e77c1f : 00000000`00000050 fffffac0`0b05ee08 00000000`00000000 fffff880`06cef040 : nt!KeBugCheckEx
    fffff880`06ceeee0 fffff800`02ecadae : 00000000`00000000 fffffac0`0b05ee08 fffff8a0`0d59fc00 fffff8a0`116fd6f0 : nt! ?? ::FNODOBFM::`string'+0x43d41
    fffff880`06cef040 fffff800`02f14fe8 : fffff6fc`00000000 fffff8a0`116fd6f0 fffffa80`07004800 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`06cef1d0 fffff880`00d8daae : fffffa80`0badcf20 fffff880`06cef330 fffffa80`07004800 fffff880`012229f4 : nt!FsRtlLookupPerStreamContextInternal+0x7c
    fffff880`06cef210 fffff880`00d98da1 : fffffa80`07004800 fffff880`01224e84 fffffa80`09094010 00000000`00000001 : fltmgr!FltpGetStreamListCtrl+0x8e
    fffff880`06cef270 fffff880`00e62052 : 00000000`00000000 fffff140`117d5887 fffff880`06cef4c0 fffff880`012bdbd8 : fltmgr!FltGetStreamContext+0x21
    fffff880`06cef2a0 fffff880`00e60b07 : fffff140`117d5887 00000000`00000000 00000000`00000000 00000000`00000000 : fileinfo!FIStreamGet+0x52
    fffff880`06cef310 fffff880`00d8d288 : 00000000`00000000 00000000`00000000 fffffa80`090713b0 00000000`00000000 : fileinfo!FIPostCreateCallback+0xf3
    fffff880`06cef3a0 fffff880`00d8bd1b : fffffa80`07293030 fffffa80`0bb34e80 fffffa80`06f92bb0 fffffa80`06f92dd0 : fltmgr!FltpPerformPostCallbacks+0x368
    fffff880`06cef470 fffff880`00dab2b9 : fffffa80`09071010 fffffa80`07004800 fffffa80`09071000 fffffa80`06f02900 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x39b
    fffff880`06cef500 fffff880`02ba832b : fffffa80`090713f8 fffff800`02ee2dbf fffffa80`097ea060 00000000`00000000 : fltmgr!FltpCreate+0x2a9
    fffff880`06cef5b0 fffffa80`090713f8 : fffff800`02ee2dbf fffffa80`097ea060 00000000`00000000 fffffa80`0badcf20 : avgidsfiltera+0x332b
    fffff880`06cef5b8 fffff800`02ee2dbf : fffffa80`097ea060 00000000`00000000 fffffa80`0badcf20 fffffa80`09071010 : 0xfffffa80`090713f8
    fffff880`06cef5c0 fffff800`031c9d35 : 00000000`00000005 fffffa80`0ba73708 fffffa80`0973c010 fffffa80`0badcfb8 : nt!RtlCopyUnicodeString+0x3f
    fffff880`06cef5f0 fffff800`031c65d8 : fffffa80`06ee4c50 fffff800`00000000 fffffa80`0ba73550 00000000`00000001 : nt!IopParseDevice+0x5a5
    fffff880`06cef780 fffff800`031c77f6 : 00000000`00000000 fffffa80`0ba73550 fffffa80`06f02900 fffffa80`06739c90 : nt!ObpLookupObjectName+0x588
    fffff880`06cef870 fffff800`031c90fc : 00000000`00000400 00000000`00000000 fffffa80`0badce01 fffff880`06cef958 : nt!ObOpenObjectByName+0x306
    fffff880`06cef940 fffff800`031b4924 : 00000000`03aae498 fffff8a0`00000080 00000000`03aaecf0 00000000`03aae438 : nt!IopCreateFile+0x2bc
    fffff880`06cef9e0 fffff800`02ecbf13 : fffffa80`09c54060 00000000`00000001 fffffa80`0991f060 fffff800`031c3294 : nt!NtOpenFile+0x58
    fffff880`06cefa70 00000000`77ad164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`03aae3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ad164a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    fileinfo!FIStreamGet+52
    fffff880`00e62052 8bd8            mov     ebx,eax
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  fileinfo!FIStreamGet+52
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: fileinfo
    
    IMAGE_NAME:  fileinfo.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc481
    
    FAILURE_BUCKET_ID:  X64_0x50_fileinfo!FIStreamGet+52
    
    BUCKET_ID:  X64_0x50_fileinfo!FIStreamGet+52
    
    Followup: MachineOwner
    ---------
    Thanks for the quick reply yowanvista,

    I don't believe that AVG is the culprit to the source problem as I only installed it 3 day ago, originally I had Avast after 2 weeks or so with problems I removed and did not have any protection running because I was without internet for about a week before installing AVG. BSOD's have occurred under all configurations.

    I had installed Daemon tools yesterday morning along with the SPTD.

    I'll take your advice and have removed AVG as well as Daemon tools and the SPTD. I have not been overclocking my system, and system seems to be running around 40C. If any new BSOD's occur I will re-load dumps. Given that AVG has not been present since the beginning of problem are there any other things I should consider.
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    AVG was involved in the last crash, removing it will eliminate it from the list of possible causes.
    Run the Ram Test for 7 passes (It shall take ~4 Hours) and post back with your results. :)
      My Computer


  5. Posts : 6
    Windows 7 Home Premium x64
    Thread Starter
       #5

    yowanvista said:
    AVG was involved in the last crash, removing it will eliminate it from the list of possible causes.
    Run the Ram Test for 7 passes (It shall take ~4 Hours) and post back with your results. :)
    Ran a Ram test using basic setting with 7 passes, it passed. I've attached the results.

    I can try again with extended and Cache on but when I have tried this before with 2 passes, it has passed.
      My Computer


  6. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #6

    Riverman88 said:
    yowanvista said:
    AVG was involved in the last crash, removing it will eliminate it from the list of possible causes.
    Run the Ram Test for 7 passes (It shall take ~4 Hours) and post back with your results. :)
    Ran a Ram test using basic setting with 7 passes, it passed. I've attached the results.

    I can try again with extended and Cache on but when I have tried this before with 2 passes, it has passed.
    We'll need the dump files for analysis if you experience more BSODs. You RAM seems to fine so far. :)
      My Computer


  7. Posts : 6
    Windows 7 Home Premium x64
    Thread Starter
       #7

    Managed to go nearly 24 hours without a crash while running the computer non-stop (though mostly idle aside from some torrent use). Tried to copy files from hard drive to the other and had a crash. Rebooted and had a crash while I was absent. I have gathered the dumps and perfmon again for evaluation. 3rd crash occurred while attempting to post initial results. All of these results are attached. I'm going to run another memory test now that crashes are happening again. Thanks for continued help... this is getting frustrating!
      My Computer


  8. Posts : 6
    Windows 7 Home Premium x64
    Thread Starter
       #8

    Memtest showed this screen but after test I could find no results in the event viewer. Could I just have a bad stick of ram or worse yet a poor motherboard socket?
      My Computer


  9. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #9

    It has something related with your RAM, Test your RAM stick individually & reseat them.

    This driver, ASMMAP64.sys also be involved, it is the oldest driver on your system.
    It is an ATK Hotkey ATK0101 ACPI UTILITY Driver, which you may be able to find an update for on the Asus support page. ASUSTeK Computer Inc. -Support- Drivers and Download
      My Computer


  10. Posts : 6
    Windows 7 Home Premium x64
    Thread Starter
       #10

    Tried updating the ASMMAP64.sys driver by installing the newest driver from the site but after it seems that the driver was already up to date. I'm attaching information from my BSODs over the last couple of days, maybe something new will be apparent.
      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 15:10.
Find Us