BSOD occurs everytime. Need help!

Page 2 of 2 FirstFirst 12

  1. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #11

    Hello and Welcome !

    Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! « Captain Debugger lets make sure it's not a hardware problem.

    Uninstall ESET completely out of your System and use the Cleanup Tool to remove the left over files ESET Knowledgebase - How do I manually uninstall my ESET security product? and Install Microsoft Security Essentials.

    Bugcheck:

    Code:
    ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
    An attempt was made to write to readonly memory.  The guilty driver is on the
    stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffff88001291030, Virtual address for the attempted write.
    Arg2: 0a300000035d3121, PTE contents.
    Arg3: fffff880059ff6f0, (reserved)
    Arg4: 000000000000000b, (reserved)
    
    Debugging Details:
    ------------------
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xBE
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff880059ff6f0 -- (.trap 0xfffff880059ff6f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8a001291062 rbx=0000000000000000 rcx=fffff88001291060
    rdx=fffff88001291060 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800028d280c rsp=fffff880059ff880 rbp=0000000000000001
     r8=0000002000000002  r9=0000000000000000 r10=fffffa800691c0f0
    r11=fffffa80049fd060 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    nt!ObfDereferenceObject+0x2c:
    fffff800`028d280c f0480fc11f      lock xadd qword ptr [rdi],rbx ds:0040:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000294dae2 to fffff800028cd740
    
    STACK_TEXT:  
    fffff880`059ff588 fffff800`0294dae2 : 00000000`000000be fffff880`01291030 0a300000`035d3121 fffff880`059ff6f0 : nt!KeBugCheckEx
    fffff880`059ff590 fffff800`028cb82e : 00000000`00000001 ffffffff`ffffffff 00000000`00f80000 fffff8a0`0f30c144 : nt! ?? ::FNODOBFM::`string'+0x4237e
    fffff880`059ff6f0 fffff800`028d280c : 00000000`829e02bc fffff8a0`0000c590 fffff8a0`00004920 fffff8a0`01291060 : nt!KiPageFault+0x16e
    fffff880`059ff880 fffff800`02bc6ecf : 00000000`00000001 00000000`00000000 fffff880`01291060 00000000`00000001 : nt!ObfDereferenceObject+0x2c
    fffff880`059ff8e0 fffff800`02bcbe4d : fffffa80`0691c010 fffff880`059ffa40 fffff8a0`00000040 fffffa80`03a10510 : nt!ObpLookupObjectName+0x5d0
    fffff880`059ff9e0 fffff800`02baadcc : fffff8a0`01291060 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ObOpenObjectByName+0x1cd
    fffff880`059ffa90 fffff800`02bacf0f : 00000000`06f7d848 00000000`02000000 00000000`06f7d898 000007fe`00000000 : nt!CmOpenKey+0x28a
    fffff880`059ffbe0 fffff800`028cc993 : fffffa80`049fd060 fffff880`00000008 00000000`06f7daa0 00000000`03342850 : nt!NtOpenKeyEx+0xf
    fffff880`059ffc20 00000000`778c0caa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`06f7d808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778c0caa
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+4237e
    fffff800`0294dae2 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4237e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4237e
    
    BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4237e
    
    Followup: MachineOwner
    Post us back the results,
    Captain
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #12

    Just run the jcgriff2 app, like you did before, if you get more BSODs.
      My Computer


  3. Posts : 9
    Windows 7 Ultimate x64
    Thread Starter
       #13

    thanks i will do as posted. be back as soon as everything is done.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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:12.
Find Us