A BSOD a day keeps debuggers at play :|


  1. Posts : 15
    Windows 7 Professional x64
       #1

    A BSOD a day keeps debuggers at play :|


    Sry for the bad title.
    I keep getting random BSOD's like SYSTEM_SERVICE_EXCEPTION, IRQ_NOT_LESS_OR_EQUAL, and dxgmms1.sys crash BSOD.

    I kinda fixed the dxgmms1.sys by running a driver sweep in safe mode and reinstalling catalyst 10.11 drivers

    However the latest BSOD was PAGE_FAULT_IN_NON_PAGED_AREA and caused by wdf01000.sys

    Please check it out
    Have included the required files in the zipped file.
    Windows 7 x64
    is the original installed OS on the system
    - an OEM
    - System is 6-7 months old
    - OS is also same as was preinstalled
      My Computer


  2. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #2

    I looked at your four most recent dumps. They blame various drivers: ntkrnlmp.exe, one of the Windows system core files and very unlikely to be the real cause; dxgmms1.sys, Windows system Direct X driver and unlikely to be the real cause; and atikmdag.sys, a video driver which is up to date. The dumps indicate memory corruption,

    I recommend that you completely uninstall Norton/Symantec using this removal tool: Tool, Norton is a known cause of conflicts and BSOD"s on some Win 7 systems. Download and install Microsoft Security Essential and make sure Windows Firewall is turned on. Reboot and see how your system runs. Please update us and let us know. If you get another BSOD, upload it and we will go from there.
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
    Debug session time: Fri Jan  7 14:32:00.472 2011 (GMT-5)
    System Uptime: 0 days 8:03:52.908
    Loading Kernel Symbols
    ...............................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff88004420ce5, fffff880021c06a8, fffff880021bff10}
    
    Unable to load image Unknown_Module_00000000`00200020, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00200020
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00200020
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88004420ce5, The address that the exception occurred at
    Arg3: fffff880021c06a8, Exception Record Address
    Arg4: fffff880021bff10, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    +16
    fffff880`04420ce5 488b02          mov     rax,qword ptr [rdx]
    
    EXCEPTION_RECORD:  fffff880021c06a8 -- (.exr 0xfffff880021c06a8)
    ExceptionAddress: fffff88004420ce5
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff880021bff10 -- (.cxr 0xfffff880021bff10)
    rax=fffff880021c0908 rbx=0000000000000000 rcx=fffffa800631f000
    rdx=fffbfa80058b6170 rsi=fffffa8008184288 rdi=fffffa800631f000
    rip=fffff88004420ce5 rsp=fffff880021c08e0 rbp=fffffa8007f8c7a0
     r8=fffffa8006edad01  r9=0000000000000000 r10=0000000000000000
    r11=000000000000011c r12=00000000000000cb r13=0000000000000000
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    fffff880`04420ce5 488b02          mov     rax,qword ptr [rdx] ds:002b:fffbfa80`058b6170=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af0e0
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    +16
    fffff880`04420ce5 488b02          mov     rax,qword ptr [rdx]
    
    FAILED_INSTRUCTION_ADDRESS: 
    +16
    fffff880`04420ce5 488b02          mov     rax,qword ptr [rdx]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from 00000000ffffd978 to fffff88004420ce5
    
    STACK_TEXT:  
    fffff880`021c08e0 00000000`ffffd978 : 00000000`0000000d fffffa80`062fe000 fffffa80`062ff5b0 00000000`00000000 : 0xfffff880`04420ce5
    fffff880`021c08e8 00000000`0000000d : fffffa80`062fe000 fffffa80`062ff5b0 00000000`00000000 fffff880`0441ded3 : 0xffffd978
    fffff880`021c08f0 fffffa80`062fe000 : fffffa80`062ff5b0 00000000`00000000 fffff880`0441ded3 00000000`00000000 : 0xd
    fffff880`021c08f8 fffffa80`062ff5b0 : 00000000`00000000 fffff880`0441ded3 00000000`00000000 fffffa80`08184288 : 0xfffffa80`062fe000
    fffff880`021c0900 00000000`00000000 : fffff880`0441ded3 00000000`00000000 fffffa80`08184288 00000000`000000cb : 0xfffffa80`062ff5b0
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  X64_0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    ---------
    
    Debug session time: Sat Jan  8 14:33:08.512 2011 (GMT-5)
    System Uptime: 0 days 4:08:11.013
    Loading Kernel Symbols
    ...............................................
    Loading User Symbols
    Missing image name, possible paged-out or corrupt data.
    Loading unloaded module list
    .
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff88004c1b705, fffff880028c58c0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff88004c1b705, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff880028c58c0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    +529e952f00c6dd30
    fffff880`04c1b705 ??              ???
    
    CONTEXT:  fffff880028c58c0 -- (.cxr 0xfffff880028c58c0)
    Unable to read context, Win32 error 0n30
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002e8624a to fffff88004202c61
    
    STACK_TEXT:  
    fffff800`00b9cc98 fffff800`02e8624a : 00000000`0027d605 fffffa80`05a659d0 fffff800`02ff2e80 fffffa80`05b0a000 : 0xfffff880`04202c61
    fffff800`00b9cca0 fffff800`02e80ebc : fffff800`02ff2e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x53a
    fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
    
    
    FOLLOWUP_IP: 
    nt!PoIdle+53a
    fffff800`02e8624a 0fba25f61318000f bt      dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`03007648)],0Fh
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!PoIdle+53a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    STACK_COMMAND:  .cxr 0xfffff880028c58c0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_nt!PoIdle+53a
    
    BUCKET_ID:  X64_0x3B_nt!PoIdle+53a
    
    Followup: MachineOwner
    ---------
    
    Debug session time: Wed Jan 12 14:36:08.945 2011 (GMT-5)
    System Uptime: 0 days 10:13:39.381
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff88004531058, fffff88007650fd0, 0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+1c4 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff88004531058, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff88007650fd0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+1c4
    fffff880`04531058 483903          cmp     qword ptr [rbx],rax
    
    CONTEXT:  fffff88007650fd0 -- (.cxr 0xfffff88007650fd0)
    rax=fffffa800770e060 rbx=fffbf8a009f93560 rcx=fffff88007651b80
    rdx=0000000000000004 rsi=fffffa800762e010 rdi=0000000000000000
    rip=fffff88004531058 rsp=fffff880076519a0 rbp=0000000000000001
     r8=0000000000000016  r9=0000000000000011 r10=fffff880045268d0
    r11=0000000000000000 r12=fffff8a00e822a90 r13=0000000000000011
    r14=fffff8a001b31cc0 r15=0000000073452450
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x1c4:
    fffff880`04531058 483903          cmp     qword ptr [rbx],rax ds:002b:fffbf8a0`09f93560=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  BFBC2Game.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88004531058
    
    STACK_TEXT:  
    fffff880`076519a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x1c4
    
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+1c4
    fffff880`04531058 483903          cmp     qword ptr [rbx],rax
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+1c4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
    
    STACK_COMMAND:  .cxr 0xfffff88007650fd0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+1c4
    
    BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+1c4
    
    Followup: MachineOwner
    ---------
    
    Debug session time: Fri Jan 14 00:38:07.377 2011 (GMT-5)
    System Uptime: 0 days 0:21:23.439
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff88004929817, fffff88008382900, 0}
    
    Probably caused by : atikmdag.sys ( atikmdag+90817 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff88004929817, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff88008382900, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    atikmdag+90817
    fffff880`04929817 8b4820          mov     ecx,dword ptr [rax+20h]
    
    CONTEXT:  fffff88008382900 -- (.cxr 0xfffff88008382900)
    rax=0000000000000000 rbx=fffffa80054cee90 rcx=fffffa8004b831f0
    rdx=0000000000000000 rsi=0000000000000015 rdi=fffffa8004bff010
    rip=fffff88004929817 rsp=fffff880083832d0 rbp=fffffa8004b831f0
     r8=0000000000000015  r9=fffff88004ceb970 r10=0000000000000000
    r11=fffff88008383420 r12=0000000000000000 r13=fffffa8006da4010
    r14=0000000000000001 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    atikmdag+0x90817:
    fffff880`04929817 8b4820          mov     ecx,dword ptr [rax+20h] ds:002b:00000000`00000020=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88004929817
    
    STACK_TEXT:  
    fffff880`083832d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x90817
    
    
    FOLLOWUP_IP: 
    atikmdag+90817
    fffff880`04929817 8b4820          mov     ecx,dword ptr [rax+20h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  atikmdag+90817
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4cef1f94
    
    STACK_COMMAND:  .cxr 0xfffff88008382900 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+90817
    
    BUCKET_ID:  X64_0x3B_atikmdag+90817
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 15
    Windows 7 Professional x64
    Thread Starter
       #3

    I recommend that you completely uninstall Norton/Symantec using this removal tool: [FONT=Verdana]

    Which anti virus do u recommend or which do u use. I prefer more internet security coz i play a lot of multiplayer and im online for long times.
      My Computer


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

    AurA said:
    I recommend that you completely uninstall Norton/Symantec using this removal tool: [FONT=Verdana]
    Which anti virus do u recommend or which do u use. I prefer more internet security coz i play a lot of multiplayer and im online for long times.
    Use MSE and Windows Firewall or reinstall the latest version of Norton, v18.5.0.125
      My Computer


  5. Posts : 15
    Windows 7 Professional x64
    Thread Starter
       #5

    Use MSE and Windows Firewall or reinstall the latest version of Norton, v18.5.0.125
    IS MSE good. Never used it
      My Computer


  6. Posts : 927
    windows 7 ultimate
       #6

    Apart from anything else, MSE is BSOD friendly. Once you've cured your BSOD, feel free to pick your own poison, but ask advice first, there are a few that are definitely not Windows 7 friendly. Despite what they'll tell you to get your bucks from your pocket to theirs.
      My Computer


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

    AurA said:
    Use MSE and Windows Firewall or reinstall the latest version of Norton, v18.5.0.125
    IS MSE good. Never used it
    MSE offers basic protection, it might be unsuitable for heavy downloaders


    MSE is BSOD friendly
    MSE also causes BSODs(mpfilter.sys), but less frequently than other products
      My Computer


  8. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #8

    Once you know your system is stable, you can try Avast. Avast generally runs well with Win 7. MSE offers good protection. The one drawback is that it does not have an email scanner.
      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 20:38.
Find Us