BSOD While playing Games and somtimes Randomly


  1. Posts : 2
    Windows 7 64bit
       #1

    BSOD While playing Games and somtimes Randomly


    Been having trouble lately with BSOD cant play any games without getting BSOD and sometimes randomly without playing a game but mainly games. According to BlueScreenView the caused by address/driver is 'ntoskrnl.exe+75c40'

    I have ran MemTest86+ with all tests and it gave no errors. Im currently trying and running with Driver Verifiers Enabled, it runs slow with it on but no BSOD but im not playing games.


    My graphics drivers from Nvidia are updated fully. Im at a lost for answers, and cant play any games otherwise m computer crashes if anyone can help me please i would be grateful
      My Computer


  2. Posts : 544
    Windows 7 64bit
       #2

    Hi Myrddin,

    The following are the major crashes observed:
    Code:
    Loading Dump File [C:\Errors\SF_13-03-2013\031313-28890-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    Machine Name:
    Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c8e670
    Debug session time: Thu Mar 14 02:01:11.353 2013 (UTC + 5:30)
    System Uptime: 0 days 0:40:12.916
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffaa005183850, 0, fffff80002d96322, 5}
    
    
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt!RtlpAddKnownAce+22 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: fffffaa005183850, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002d96322, 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 fffff80002cf8100
     fffffaa005183850 
    
    FAULTING_IP: 
    nt!RtlpAddKnownAce+22
    fffff800`02d96322 0fb607          movzx   eax,byte ptr [rdi]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800a6d0890 -- (.trap 0xfffff8800a6d0890)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8005183850 rbx=0000000000000000 rcx=fffff8a00f7e32b0
    rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002d96322 rsp=fffff8800a6d0a20 rbp=fffff8a010c9b8c0
     r8=0000000000000000  r9=00000000000f01ff r10=fffff8a00f7e32f0
    r11=fffff8a00f7e32f8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    nt!RtlpAddKnownAce+0x22:
    fffff800`02d96322 0fb607          movzx   eax,byte ptr [rdi] ds:0017:00000000`00000000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002b3c673 to fffff80002abfc40
    
    STACK_TEXT:  
    fffff880`0a6d0728 fffff800`02b3c673 : 00000000`00000050 fffffaa0`05183850 00000000`00000000 fffff880`0a6d0890 : nt!KeBugCheckEx
    fffff880`0a6d0730 fffff800`02abdd6e : 00000000`00000000 fffffaa0`05183850 00000000`00000000 fffff8a0`0f7e32b0 : nt! ?? ::FNODOBFM::`string'+0x43801
    fffff880`0a6d0890 fffff800`02d96322 : fffff8a0`0f7e32b0 00000000`00000002 fffff8a0`000015d0 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`0a6d0a20 fffff800`02d965ae : fffff8a0`0f7e32b0 fffff880`0a6d0b20 fffff8a0`01f3c060 00000000`000f01ff : nt!RtlpAddKnownAce+0x22
    fffff880`0a6d0a60 fffff800`02d95f7b : fffffa80`07905060 fffff880`0a6d0ca0 00000000`00000000 fffffa80`07b7f060 : nt!SepCreateImpersonationTokenDacl+0x146
    fffff880`0a6d0ac0 fffff800`02d962f1 : fffffa80`07b7f060 fffff880`00000008 00000000`00000001 00000000`00000001 : nt!NtOpenThreadTokenEx+0x24b
    fffff880`0a6d0be0 fffff800`02abeed3 : fffffa80`07b7f060 00000000`00000001 00000000`00000000 fffffa80`08591c50 : nt!NtOpenThreadToken+0x11
    fffff880`0a6d0c20 00000000`773f155a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0210e778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773f155a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!RtlpAddKnownAce+22
    fffff800`02d96322 0fb607          movzx   eax,byte ptr [rdi]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!RtlpAddKnownAce+22
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!RtlpAddKnownAce+22
    
    BUCKET_ID:  X64_0x50_nt!RtlpAddKnownAce+22
    
    Followup: MachineOwner
    ---------
    
    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=2015]
    BiosVendor = Phoenix Technologies, LTD
    BiosVersion = ASUS M2N4-SLI ACPI BIOS Revision 1205
    BiosReleaseDate = 08/19/2008
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    SystemVersion = System Version
    BaseBoardManufacturer = ASUSTeK Computer INC.
    BaseBoardProduct = M2N4-SLI
    BaseBoardVersion = 1.XX
    
    
    -----------------------------------------------------------------------------------------------------
    
    
    Loading Dump File [C:\Errors\SF_13-03-2013\031313-32687-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    Machine Name:
    Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c5c670
    Debug session time: Thu Mar 14 01:20:11.512 2013 (UTC + 5:30)
    System Uptime: 0 days 21:26:44.075
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffaa00954ffd0, 0, fffff80002aa216d, 5}
    
    
    Could not read faulting driver name
    Probably caused by : Npfs.SYS ( Npfs!NpFsdWrite+76 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: fffffaa00954ffd0, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002aa216d, 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 fffff80002cc6100
     fffffaa00954ffd0 
    
    FAULTING_IP: 
    nt!IopCompleteRequest+fd
    fffff800`02aa216d 488b87b0000000  mov     rax,qword ptr [rdi+0B0h]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  LCDClock.exe
    
    CURRENT_IRQL:  1
    
    IRP_ADDRESS:  ffffffffffffff88
    
    DEVICE_OBJECT: fffffa800c0b0898
    
    TRAP_FRAME:  fffff880035e8530 -- (.trap 0xfffff880035e8530)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffa8009cf5bd1 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002aa216d rsp=fffff880035e86c0 rbp=0000000000000000
     r8=fffffa8009cf5bd0  r9=0000000000000020 r10=fffff80002c0a760
    r11=fffffa80077113b0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!IopCompleteRequest+0xfd:
    fffff800`02aa216d 488b87b0000000  mov     rax,qword ptr [rdi+0B0h] ds:00000000`000000b0=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002b0a673 to fffff80002a8dc40
    
    STACK_TEXT:  
    fffff880`035e83c8 fffff800`02b0a673 : 00000000`00000050 fffffaa0`0954ffd0 00000000`00000000 fffff880`035e8530 : nt!KeBugCheckEx
    fffff880`035e83d0 fffff800`02a8bd6e : 00000000`00000000 fffffaa0`0954ffd0 00000000`00000000 fffffa80`0b4931e0 : nt! ?? ::FNODOBFM::`string'+0x43801
    fffff880`035e8530 fffff800`02aa216d : 00000000`00000001 fffff800`02a90b8a 00000000`5246704e fffff800`02aadacd : nt!KiPageFault+0x16e
    fffff880`035e86c0 fffff800`02a80657 : 00000000`00000000 00000000`00000000 fffffa80`16a13100 00000000`00000000 : nt!IopCompleteRequest+0xfd
    fffff880`035e8790 fffff800`02ae78b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
    fffff880`035e8810 fffff800`02a6e712 : fffff800`02c09e80 00000000`00000000 00000000`00000001 fffffa80`00000002 : nt! ?? ::FNODOBFM::`string'+0xcc36
    fffff880`035e8880 fffff800`02a91ef3 : fffffa80`09539670 00000000`a000000c 00000000`00000000 fffffa80`05fca000 : nt!KeInsertQueueApc+0xa2
    fffff880`035e88e0 fffff880`03ada16a : fffffa80`0c0b0850 00000000`03500002 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0xb63
    fffff880`035e89d0 fffff800`02d99e0b : 00000000`00000001 fffffa80`0954ff20 00000000`00000000 fffffa80`0c0b0780 : Npfs!NpFsdWrite+0x76
    fffff880`035e8a40 fffff800`02da4803 : fffffa80`0c0b0898 00000000`00000000 fffffa80`0954ff20 fffff800`02c09e80 : nt!IopSynchronousServiceTail+0xfb
    fffff880`035e8ab0 fffff800`02a8ced3 : 00000000`00000001 00000000`00000000 000007fe`fcf248e0 00000001`8001c1c0 : nt!NtWriteFile+0x7e2
    fffff880`035e8bb0 00000000`7737139a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`03bbfd48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7737139a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    Npfs!NpFsdWrite+76
    fffff880`03ada16a 488d442440      lea     rax,[rsp+40h]
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  Npfs!NpFsdWrite+76
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Npfs
    
    IMAGE_NAME:  Npfs.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc114
    
    FAILURE_BUCKET_ID:  X64_0x50_Npfs!NpFsdWrite+76
    
    BUCKET_ID:  X64_0x50_Npfs!NpFsdWrite+76
    
    Followup: MachineOwner
    ---------
    
    
    -----------------------------------------------------------------------------------------------------------------
    
    Loading Dump File [C:\Errors\SF_13-03-2013\022613-31140-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    Machine Name:
    Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02ca6670
    Debug session time: Wed Feb 27 06:41:08.694 2013 (UTC + 5:30)
    System Uptime: 0 days 20:58:28.256
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck BE, {fffff88002c56488, 43200001464d0101, fffff80000ba2cd0, a}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4333b )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: fffff88002c56488, Virtual address for the attempted write.
    Arg2: 43200001464d0101, PTE contents.
    Arg3: fffff80000ba2cd0, (reserved)
    Arg4: 000000000000000a, (reserved)
    
    Debugging Details:
    ------------------
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xBE
    
    PROCESS_NAME:  swkotor2.exe
    
    CURRENT_IRQL:  2
    
    TRAP_FRAME:  fffff80000ba2cd0 -- (.trap 0xfffff80000ba2cd0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa80112d5c30 rbx=0000000000000000 rcx=fffff88002c56488
    rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ae25ff rsp=fffff80000ba2e60 rbp=000000000049bd10
     r8=fffffa80159d1ef0  r9=00000000000000c1 r10=0000000000000010
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac po cy
    nt!KiTimerExpiration+0xef:
    fffff800`02ae25ff 488901          mov     qword ptr [rcx],rax ds:fffff880`02c56488=4100000180c18148
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002b5420b to fffff80002ad7c40
    
    STACK_TEXT:  
    fffff800`00ba2b68 fffff800`02b5420b : 00000000`000000be fffff880`02c56488 43200001`464d0101 fffff800`00ba2cd0 : nt!KeBugCheckEx
    fffff800`00ba2b70 fffff800`02ad5d6e : fffff880`0499b3c8 fffffa80`0664a000 00000000`00000000 000000af`ce6da2a7 : nt! ?? ::FNODOBFM::`string'+0x4333b
    fffff800`00ba2cd0 fffff800`02ae25ff : 000000af`ce6d3036 fffff800`00ba2e88 00000000`0049bd10 fffff800`02c56488 : nt!KiPageFault+0x16e
    fffff800`00ba2e60 fffff800`02ae24b7 : fffffa80`06733dc1 fffff800`0049bd10 00000000`00000000 00000000`00000010 : nt!KiTimerExpiration+0xef
    fffff800`00ba2f00 fffff800`02adae15 : 00000000`00000000 fffffa80`14e0fb50 00000000`00000000 fffff880`0167e800 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`02adac2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    fffff880`09f419e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+4333b
    fffff800`02b5420b cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4333b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935
    
    FAILURE_BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4333b
    
    BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4333b
    
    Followup: MachineOwner
    ---------
    
    
    -------------------------------------------------------------------------------------------------------------
    BaseBoardManufacturer = ASUSTeK Computer INC.
    BaseBoardProduct = M2N4-SLI
    Check if the 'Windows 7' supports the 'Motherboard'. Tried to check for a current BIOS version, but could not find one that supports 'Windows 7'. Please recheck with the 'Motherboard manufacturer' about it: ASUS - M2N4-SLI

    Several crashes were seen as caused by : 'ntkrnlmp.exe' driver. This relates to 'NT Kernel & System' and is installed with 'Windows Updates'.
    'Bug check 0x50' usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
    Another common cause is the installation of a faulty system service.
    Antivirus software can also trigger this error, as can a corrupted 'NTFS volume'.

    Another crash happened due to 'Npfs.SYS' driver.
    Bug Check 0xBE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
    This is issued if a driver attempts to write to a read-only memory segment.

    Please follow the below mentioned steps to see if they help:
    1. Uninstall AVG with an uninstaller tool: Download tools and utilities | AVG India
    2. If hardware has been added to the system recently, remove it to see if the error recurs.
    3. Run Diagnostics on the 'Hard Drive': WD Support / Downloads / SATA & SAS / WD Blue / SE / SE16 (SATA II)
    4. Use 'Option 2' (in the given tutorial) to check the 'Disk' for any errors and attempt repairs: Disk Check
    5. Install 'Microsoft Security Essentials': Download Microsoft Security Essentials from Official Microsoft Download Center
    6. Install 'Windows Updates': Microsoft Windows Update

    Recheck results.
    Do reply with the findings; would be glad to assist.
      My Computer


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

    Thank you for the help. I have done all the steps you mentioned above. All of them showed no errors. And uninstalled AVG. I have not installed any recent hardware.

    I played a game and after a little it crashed again this is the dump.
    Last edited by Myrddin; 14 Mar 2013 at 20:30.
      My Computer


  4. Posts : 544
    Windows 7 64bit
       #4

    Hi Myrddin,

    Thank you for the reply.

    The crashes reported the following errors:
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Errors\031413-18781-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    Machine Name:
    Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02c5e670
    Debug session time: Fri Mar 15 06:55:58.014 2013 (UTC + 5:30)
    System Uptime: 0 days 4:32:46.561
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41284, f9f3001, 4383, fffff70001080000}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041284, A PTE or the working set list is corrupt.
    Arg2: 000000000f9f3001
    Arg3: 0000000000004383
    Arg4: fffff70001080000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_41284
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  MsMpEng.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002ae67e7 to fffff80002a8fc40
    
    STACK_TEXT:  
    fffff880`02baf7e8 fffff800`02ae67e7 : 00000000`0000001a 00000000`00041284 00000000`0f9f3001 00000000`00004383 : nt!KeBugCheckEx
    fffff880`02baf7f0 fffff800`02b00b2c : fffffa80`047a7530 b8300001`7e271025 00000000`0f9f2000 f3a00001`771c0025 : nt! ?? ::FNODOBFM::`string'+0x4ad3
    fffff880`02baf830 fffff800`02ac28e9 : 00000000`00000000 00000000`109effff ffffffff`00000000 00000002`00000001 : nt! ?? ::FNODOBFM::`string'+0x34d80
    fffff880`02baf9f0 fffff800`02dab2e1 : fffffa80`0ab19350 00000000`00000000 fffffa80`05537240 fffffa80`05537240 : nt!MiRemoveMappedView+0xd9
    fffff880`02bafb10 fffff800`02dab6ef : 0000007f`00000000 00000000`0f9f0000 fffffa80`00000001 00000000`04600301 : nt!MiUnmapViewOfSection+0x1b1
    fffff880`02bafbd0 fffff800`02a8eed3 : 00000000`00000001 00000000`0462493a fffffa80`07b01060 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f
    fffff880`02bafc20 00000000`77a615ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`01a3e728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a615ba
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+4ad3
    fffff800`02ae67e7 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ad3
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935
    
    FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3
    
    BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3
    
    Followup: MachineOwner
    ---------
    
    0: kd> !sysinfo cpuspeed
    sysinfo: unknown error 80004005
    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=2015]
    BiosVendor = Phoenix Technologies, LTD
    BiosVersion = ASUS M2N4-SLI ACPI BIOS Revision 1205
    BiosReleaseDate = 08/19/2008
    SystemManufacturer = System manufacturer
    SystemProductName = System Product Name
    SystemVersion = System Version
    BaseBoardManufacturer = ASUSTeK Computer INC.
    BaseBoardProduct = M2N4-SLI
    BaseBoardVersion = 1.XX
    The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred. Good that the 'Memtest' passed.

    BaseBoardManufacturer = ASUSTeK Computer INC.
    BaseBoardProduct = M2N4-SLI
    Check if the 'Windows 7' supports the 'Motherboard'. Tried to check for a current BIOS version, but could not find one that supports 'Windows 7'. Please recheck with the 'Motherboard manufacturer' about it: ASUS - M2N4-SLI
    Did you check for a 'BIOS' update that supports 'Windows 7'?

    Run Diagnostics on the 'Hard Drive': WD Support / Downloads / SATA & SAS / WD Blue / SE / SE16 (SATA II)
    Use 'Option 2' (in the given tutorial) to check the 'Disk' for any errors and attempt repairs: Disk Check
    What were the results of 'Hard Drive' diagnostics? Did you attempt a 'Disk drive' scan (Chkdsk)? If not, please do that and share results.

    Second crash:
    Code:
    Loading Dump File [C:\Errors\031413-19078-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    Machine Name:
    Kernel base = 0xfffff800`02a16000 PsLoadedModuleList = 0xfffff800`02c5a670
    Debug session time: Fri Mar 15 01:12:55.474 2013 (UTC + 5:30)
    System Uptime: 0 days 0:39:56.005
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff88002a9132a, 2, 8, fffff88002a9132a}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextRunningTimeAtISR+137 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff88002a9132a, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff88002a9132a, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc4100
     fffff88002a9132a 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    +50392faf0377d86c
    fffff880`02a9132a ??              ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  RelicCOH.exe
    
    TRAP_FRAME:  fffff8800ac38020 -- (.trap 0xfffff8800ac38020)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=257c402e95ad0000
    rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002a9132a rsp=fffff8800ac381b0 rbp=0000000000000000
     r8=000000000000000f  r9=000000000000000f r10=fffff80002a16000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    fffff880`02a9132a ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a8b1e9 to fffff80002a8bc40
    
    FAILED_INSTRUCTION_ADDRESS: 
    +50392faf0377d86c
    fffff880`02a9132a ??              ???
    
    STACK_TEXT:  
    fffff880`0ac37ed8 fffff800`02a8b1e9 : 00000000`0000000a fffff880`02a9132a 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff880`0ac37ee0 fffff800`02a89e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02c07e80 : nt!KiBugCheckDispatch+0x69
    fffff880`0ac38020 fffff880`02a9132a : fffffa80`00000000 fffff880`00000000 fffffa80`061c6d00 fffff880`03e0c188 : nt!KiPageFault+0x260
    fffff880`0ac381b0 fffffa80`00000000 : fffff880`00000000 fffffa80`061c6d00 fffff880`03e0c188 fffffa80`076f6400 : 0xfffff880`02a9132a
    fffff880`0ac381b8 fffff880`00000000 : fffffa80`061c6d00 fffff880`03e0c188 fffffa80`076f6400 00000000`00000000 : 0xfffffa80`00000000
    fffff880`0ac381c0 fffffa80`061c6d00 : fffff880`03e0c188 fffffa80`076f6400 00000000`00000000 00000000`00000000 : 0xfffff880`00000000
    fffff880`0ac381c8 fffff880`03e0c187 : fffffa80`076f6400 00000000`00000000 00000000`00000000 00000000`00000003 : 0xfffffa80`061c6d00
    fffff880`0ac381d0 fffffa80`076f6400 : 00000000`00000000 00000000`00000000 00000000`00000003 00000000`00000000 : dxgmms1!VidSchiUpdateContextRunningTimeAtISR+0x137
    fffff880`0ac381d8 00000000`00000000 : 00000000`00000000 00000000`00000003 00000000`00000000 ffffddfc`4aed141d : 0xfffffa80`076f6400
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VidSchiUpdateContextRunningTimeAtISR+137
    fffff880`03e0c187 cc              int     3
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  dxgmms1!VidSchiUpdateContextRunningTimeAtISR+137
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_dxgmms1!VidSchiUpdateContextRunningTimeAtISR+137
    
    BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_dxgmms1!VidSchiUpdateContextRunningTimeAtISR+137
    
    Followup: MachineOwner
    The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access page-able memory at a process IRQL that was too high. This bug check is usually caused by drivers that have used improper addresses.

    It appears to be a conflicting security program left in place before installing 'Microsoft Security Essentials'. If you removed 'AVG' from 'Control Panel', its 'left overs' may still be creating a conflict. Please try removing it from the uninstaller, if not done already: Download tools and utilities | AVG India

    If you still experience similar issues, try removing 'Microsoft Security Essentials' also (for troubleshooting purpose); and check results: How to manually uninstall Microsoft Security Essentials 1.0.1963 if you cannot uninstall it by using the Add or Remove Programs item\

    Hope this helps. Do reply with the findings.
      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 15:31.
Find Us