BSOD after playing graphics intensive games

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by PeaceKeeper, Feb 13, 2011.

  1. PeaceKeeper

    PeaceKeeper New Member

    Joined:
    Jan 16, 2011
    Messages:
    48
    Likes Received:
    0
    Hello there, I have yet played any games after my last post, ill post after a day or two if anything comes up. Though there were some BSOD encountered while not playing games, e.g restarting windows or windows loading

    attached is a new set of dump files. kindly advice if the raw dump files are sufficient enough
     

    Attached Files:

  2. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Most likely RAM is set wrong, or some other wrong setting in the bios. You may want to load sdetup/optimized defaults.

    Give link to a .pdf or a web page with the specs outlined for your RAM sticks and one for your motherboard.

    Re-attach MEMORY snip as you have it now.



    1. Install Catalyst 11.2:
    Guru3D - Driver Sweeper
    AMD Graphics Drivers & Software



    2. Update Primax Gaming Mouse
    NMgamingms.sys Fri Jul 24 04:55:08 2009



    3. Uninstall MagicISO
    mcdbus.sys Tue Feb 24 05:34:07 2009








    Crash Dumps:

    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\022311-23484-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`04411000 PsLoadedModuleList = 0xfffff800`0464ee50
    Debug session time: Tue Feb 22 17:22:11.907 2011 (UTC - 5:00)
    System Uptime: 0 days 1:58:00.875
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 109, {a3a039d89a552975, b3b7465eecd1fb6b, fffff800048fb6a0, 1}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a039d89a552975, Reserved
    Arg2: b3b7465eecd1fb6b, Reserved
    Arg3: fffff800048fb6a0, Failure type dependent information
    Arg4: 0000000000000001, Type of corrupted region, can be
    	0 : A generic data region
    	1 : Modification of a function or .pdata
    	2 : A processor IDT
    	3 : A processor GDT
    	4 : Type 1 process list corruption
    	5 : Type 2 process list corruption
    	6 : Debug routine modification
    	7 : Critical MSR modification
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x109
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80004481740
    
    STACK_TEXT:  
    fffff880`033625d8 00000000`00000000 : 00000000`00000109 a3a039d8`9a552975 b3b7465e`ecd1fb6b fffff800`048fb6a0 : nt!KeBugCheckEx
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    BUCKET_ID:  BAD_STACK
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\022311-28781-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`0441f000 PsLoadedModuleList = 0xfffff800`0465ce50
    Debug session time: Tue Feb 22 15:21:18.207 2011 (UTC - 5:00)
    System Uptime: 0 days 0:25:54.175
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 109, {a3a039d89a71c5c7, b3b7465eecee97cd, fffff800048f6670, 1}
    
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a039d89a71c5c7, Reserved
    Arg2: b3b7465eecee97cd, Reserved
    Arg3: fffff800048f6670, Failure type dependent information
    Arg4: 0000000000000001, Type of corrupted region, can be
    	0 : A generic data region
    	1 : Modification of a function or .pdata
    	2 : A processor IDT
    	3 : A processor GDT
    	4 : Type 1 process list corruption
    	5 : Type 2 process list corruption
    	6 : Debug routine modification
    	7 : Critical MSR modification
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x109
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8000448f740
    
    STACK_TEXT:  
    fffff880`033695d8 00000000`00000000 : 00000000`00000109 a3a039d8`9a71c5c7 b3b7465e`ecee97cd fffff800`048f6670 : nt!KeBugCheckEx
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        fffff800048f6940-fffff800048f6951  18 bytes - nt!ObpStartRTStackTrace+2ce
    	[ f8 9c d3 ff 75 08 e8 55:70 00 05 00 00 00 00 0a ]
    18 errors : !nt (fffff800048f6940-fffff800048f6951)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  LARGE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    
    Followup: memory_corruption
    ---------
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\022311-25421-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`0441a000 PsLoadedModuleList = 0xfffff800`04657e50
    Debug session time: Tue Feb 22 14:50:33.468 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:13.437
    Loading Kernel Symbols
    ...............................................................
    ................................................
    Loading User Symbols
    Loading unloaded module list
    .
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff800048c1787, 0, 0}
    
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800048c1787, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!IopConnectLineBasedInterrupt+17
    fffff800`048c1787 0a00            or      al,byte ptr [rax]
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800046c20e0
     0000000000000000 
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    BUGCHECK_STR:  0x1E_c0000005
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    EXCEPTION_RECORD:  fffff88003368e98 -- (.exr 0xfffff88003368e98)
    ExceptionAddress: fffff800048c1787 (nt!IopConnectLineBasedInterrupt+0x0000000000000017)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000000
    Attempt to read from address 0000000000000000
    
    TRAP_FRAME:  fffff88003368f40 -- (.trap 0xfffff88003368f40)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80062a1a20
    rdx=fffffa800633a020 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800048c1787 rsp=fffff880033690d8 rbp=0000000000000000
     r8=fffff88004849f20  r9=fffffa800633a000 r10=fffff8000441a000
    r11=000000000000015d r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!IopConnectLineBasedInterrupt+0x17:
    fffff800`048c1787 0a00            or      al,byte ptr [rax] ds:4b60:00000000`00000000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800044c4a39 to fffff8000448a740
    
    STACK_TEXT:  
    fffff880`033686c8 fffff800`044c4a39 : 00000000`0000001e ffffffff`c0000005 fffff800`048c1787 00000000`00000000 : nt!KeBugCheckEx
    fffff880`033686d0 fffff800`04489d82 : fffff880`03368e98 fffff880`03369220 fffff880`03368f40 fffff880`0336935c : nt!KiDispatchException+0x1b9
    fffff880`03368d60 fffff800`044888fa : 00000000`00000000 fffff880`03369220 fffff880`03368f00 fffff880`03368f00 : nt!KiExceptionDispatch+0xc2
    fffff880`03368f40 fffff800`048c1787 : 00000000`00000000 00000000`00000000 00000000`00000100 fffff880`0336935c : nt!KiPageFault+0x23a
    fffff880`033690d8 00000000`00000000 : 00000000`00000000 fffff880`03369220 00000000`00000000 00000000`00000000 : nt!IopConnectLineBasedInterrupt+0x17
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        fffff800048c1780-fffff800048c1785  6 bytes - nt!IopConnectLineBasedInterrupt+10
    	[ 41 56 48 81 ec c0:70 00 05 00 00 00 ]
        fffff800048c1787 - nt!IopConnectLineBasedInterrupt+17 (+0x07)
    	[ 00:0a ]
        fffff800048c1789-fffff800048c1791  9 bytes - nt!IopConnectLineBasedInterrupt+19 (+0x02)
    	[ 48 8b 05 50 32 d4 ff 48:00 00 00 24 00 00 00 00 ]
    16 errors : !nt (fffff800048c1780-fffff800048c1791)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  LARGE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    
    Followup: memory_corruption
    ---------
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\022311-52109-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`04407000 PsLoadedModuleList = 0xfffff800`04644e50
    Debug session time: Tue Feb 22 17:30:57.861 2011 (UTC - 5:00)
    System Uptime: 0 days 0:07:58.955
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 109, {a3a039d897a1c726, b3b7465eea1e991c, fffff800048ab4a0, 1}
    
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a039d897a1c726, Reserved
    Arg2: b3b7465eea1e991c, Reserved
    Arg3: fffff800048ab4a0, Failure type dependent information
    Arg4: 0000000000000001, Type of corrupted region, can be
    	0 : A generic data region
    	1 : Modification of a function or .pdata
    	2 : A processor IDT
    	3 : A processor GDT
    	4 : Type 1 process list corruption
    	5 : Type 2 process list corruption
    	6 : Debug routine modification
    	7 : Critical MSR modification
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x109
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80004477740
    
    STACK_TEXT:  
    fffff880`033705d8 00000000`00000000 : 00000000`00000109 a3a039d8`97a1c726 b3b7465e`ea1e991c fffff800`048ab4a0 : nt!KeBugCheckEx
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        fffff800048ab5c0-fffff800048ab5d1  18 bytes - nt!SepDeleteLogonSessionTrack+120
    	[ b7 ff 49 3b fd 74 10 48:70 00 05 00 00 00 00 0a ]
    18 errors : !nt (fffff800048ab5c0-fffff800048ab5d1)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  LARGE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE
    
    Followup: memory_corruption
    ---------
    
    
    
    



    Drivers:

    Code:
    start             end                 module name
    fffff880`051d1000 fffff880`051e9000   1394BUS  1394BUS.SYS  Mon Jul 13 20:06:38 2009 (4A5BCC0E)
    fffff880`00ef9000 fffff880`00f50000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
    fffff880`055ac000 fffff880`055c4000   adfs     adfs.SYS     Mon Nov 03 11:48:14 2008 (490F2B4E)
    fffff880`02ce1000 fffff880`02d6b000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`04817000 fffff880`0482d000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
    fffff880`010fa000 fffff880`01105000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
    fffff880`010c7000 fffff880`010d0000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`010d0000 fffff880`010fa000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
    fffff880`00c5c000 fffff880`00c7c000   AtihdW76 AtihdW76.sys Wed Nov 17 07:02:04 2010 (4CE3C43C)
    fffff880`04832000 fffff880`05043000   atikmdag atikmdag.sys Thu Nov 25 21:46:44 2010 (4CEF1F94)
    fffff880`040f4000 fffff880`04140000   atikmpag atikmpag.sys Thu Nov 25 21:16:47 2010 (4CEF188F)
    fffff960`00980000 fffff960`009e1000   ATMFD    ATMFD.DLL    unavailable (00000000)
    fffff880`04810000 fffff880`04817000   AVVideoCard AVVideoCard.sys Tue Oct 05 16:38:34 2010 (4CAB8CCA)
    fffff880`01864000 fffff880`0186b000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
    fffff880`040a7000 fffff880`040b8000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
    fffff880`054d8000 fffff880`054f6000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
    fffff880`019a9000 fffff880`019ad700   BtHidBus BtHidBus.sys Wed Jan 07 10:29:05 2009 (4964CA41)
    fffff960`00690000 fffff960`006b7000   cdd      cdd.dll      unavailable (00000000)
    fffff880`07535000 fffff880`07552000   cdfs     cdfs.sys     Mon Jul 13 19:19:46 2009 (4A5BC112)
    fffff880`043c8000 fffff880`043f2000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`00d38000 fffff880`00df8000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
    fffff880`01979000 fffff880`019a9000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00cda000 fffff880`00d38000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`01000000 fffff880`01073000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
    fffff880`04800000 fffff880`04810000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
    fffff880`055c4000 fffff880`055cc000   cpuz132_x64 cpuz132_x64.sys Thu Mar 26 19:17:23 2009 (49CC0D03)
    fffff880`055cc000 fffff880`055d5000   cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A)
    fffff880`075a6000 fffff880`075b4000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`04006000 fffff880`04089000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
    fffff880`04089000 fffff880`040a7000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
    fffff880`02cb4000 fffff880`02cc3000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
    fffff880`01963000 fffff880`01979000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`06ef9000 fffff880`06f1b000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
    fffff880`075c0000 fffff880`075c9000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`075b4000 fffff880`075c0000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`075c9000 fffff880`075dc000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    fffff880`07200000 fffff880`0720c000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
    fffff880`05043000 fffff880`05137000   dxgkrnl  dxgkrnl.sys  Tue Jan 25 23:20:10 2011 (4D3FA0FA)
    fffff880`05137000 fffff880`0517d000   dxgmms1  dxgmms1.sys  Tue Jan 25 23:19:38 2011 (4D3FA0DA)
    fffff880`01151000 fffff880`01165000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
    fffff880`01105000 fffff880`01151000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
    fffff880`01200000 fffff880`0120a000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
    fffff880`01929000 fffff880`01963000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
    fffff880`0148b000 fffff880`014d5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
    fffff800`049e4000 fffff800`04a2d000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
    fffff880`0517d000 fffff880`051a1000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
    fffff880`0721a000 fffff880`07233000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
    fffff880`07233000 fffff880`0723b080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
    fffff880`0720c000 fffff880`0721a000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
    fffff880`05400000 fffff880`054c8000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
    fffff880`01920000 fffff880`01929000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
    fffff880`040de000 fffff880`040f4000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    fffff880`01916000 fffff880`01920000   johci    johci.sys    Thu Dec 23 01:51:48 2010 (4D12F184)
    fffff880`00e00000 fffff880`00e21000   jraid    jraid.sys    Fri Oct 29 06:12:47 2010 (4CCA9E1F)
    fffff880`042a7000 fffff880`042b6000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`0723f000 fffff880`0724d000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff800`00bc9000 fffff800`00bd3000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
    fffff880`04304000 fffff880`04347000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
    fffff880`013d1000 fffff880`013eb000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
    fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
    fffff880`06f1b000 fffff880`06f20200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
    fffff880`0728b000 fffff880`072a0000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`07268000 fffff880`0728b000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
    fffff880`08571000 fffff880`0857b000   mbam     mbam.sys     Thu Dec 16 15:53:16 2010 (4D0A7C3C)
    fffff880`042c5000 fffff880`04301880   mcdbus   mcdbus.sys   Tue Feb 24 05:34:07 2009 (49A3CD1F)
    fffff880`00c82000 fffff880`00cc6000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
    fffff880`0725a000 fffff880`07268000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
    fffff880`042b6000 fffff880`042c5000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`0724d000 fffff880`0725a000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff880`010ad000 fffff880`010c7000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`0182a000 fffff880`0185b000   MpFilter MpFilter.sys Tue Sep 14 20:19:28 2010 (4C901110)
    fffff880`054c8000 fffff880`054d8000   MpNWMon  MpNWMon.sys  Tue Sep 14 20:19:30 2010 (4C901112)
    fffff880`054f6000 fffff880`0550e000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
    fffff880`0550e000 fffff880`0553b000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
    fffff880`0553b000 fffff880`05589000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
    fffff880`05589000 fffff880`055ac000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
    fffff880`015f1000 fffff880`015fc000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00f59000 fffff880`00f63000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    fffff880`01165000 fffff880`011c3000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
    fffff880`02ca9000 fffff880`02cb4000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
    fffff880`01904000 fffff880`01916000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
    fffff880`014f6000 fffff880`015e8000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`02cc3000 fffff880`02ccf000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
    fffff880`04217000 fffff880`04246000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
    fffff880`043b3000 fffff880`043c8000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
    fffff880`02ddf000 fffff880`02dee000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff880`02d6b000 fffff880`02db0000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
    fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Thu Apr 08 22:43:59 2010 (4BBE946F)
    fffff880`0855c000 fffff880`08571000   NisDrvWFP NisDrvWFP.sys Tue Sep 14 20:20:25 2010 (4C901149)
    fffff880`0723c000 fffff880`0723ec00   NMgamingms NMgamingms.sys Fri Jul 24 04:55:08 2009 (4A6976EC)
    fffff880`0120a000 fffff880`0121b000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`02c9d000 fffff880`02ca9000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
    fffff800`04407000 fffff800`049e4000   nt       ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
    fffff880`0122e000 fffff880`013d1000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
    fffff880`0185b000 fffff880`01864000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
    fffff880`051bf000 fffff880`051d0c80   ohci1394 ohci1394.sys Mon Jul 13 20:06:45 2009 (4A5BCC15)
    fffff880`02db9000 fffff880`02ddf000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
    fffff880`00fa3000 fffff880`00fb8000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00f70000 fffff880`00fa3000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`00fcd000 fffff880`00fd4000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
    fffff880`00fd4000 fffff880`00fe4000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`013eb000 fffff880`013fc000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
    fffff880`06f5a000 fffff880`07000000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
    fffff880`06ebc000 fffff880`06ef9000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
    fffff880`00cc6000 fffff880`00cda000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
    fffff880`00e21000 fffff880`00e45000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
    fffff880`04246000 fffff880`04261000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
    fffff880`04261000 fffff880`04282000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
    fffff880`04282000 fffff880`0429c000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
    fffff880`02c4c000 fffff880`02c9d000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
    fffff880`0429c000 fffff880`042a7000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
    fffff880`0186b000 fffff880`01874000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`019f2000 fffff880`019fb000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`015e8000 fffff880`015f1000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
    fffff880`018ca000 fffff880`01904000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
    fffff880`06f42000 fffff880`06f5a000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`04196000 fffff880`041fd000   Rt64win7 Rt64win7.sys Wed Dec 29 06:44:36 2010 (4D1B1F24)
    fffff880`072a5000 fffff880`07534280   RTKVHD64 RTKVHD64.sys Wed Dec 29 22:52:42 2010 (4D1C020A)
    fffff880`0107e000 fffff880`010ad000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
    fffff880`055d5000 fffff880`055e0000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
    fffff880`051e9000 fffff880`051f5000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
    fffff880`02c00000 fffff880`02c1d000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
    fffff880`018c2000 fffff880`018ca000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
    fffff880`0857b000 fffff880`085ec000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
    fffff880`084c6000 fffff880`0855c000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
    fffff880`06e2d000 fffff880`06e94000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
    fffff880`06e00000 fffff880`06e2d000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
    fffff880`04302000 fffff880`04303480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
    fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
    fffff880`055e0000 fffff880`055f2000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
    fffff880`0121b000 fffff880`01228000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
    fffff880`011c3000 fffff880`011e1000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
    fffff880`02c38000 fffff880`02c4c000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
    fffff960`005c0000 fffff960`005ca000   TSDDD    TSDDD.dll    unavailable (00000000)
    fffff880`040b8000 fffff880`040de000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
    fffff880`07552000 fffff880`075a6000   udfs     udfs.sys     Mon Jul 13 19:23:37 2009 (4A5BC1F9)
    fffff880`04347000 fffff880`04359000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
    fffff880`075dc000 fffff880`075f9000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
    fffff880`075f9000 fffff880`075faf00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
    fffff880`051ae000 fffff880`051bf000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
    fffff880`04359000 fffff880`043b3000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
    fffff880`04140000 fffff880`04196000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
    fffff880`051a1000 fffff880`051ae000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
    fffff880`00f63000 fffff880`00f70000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
    fffff880`019e4000 fffff880`019f2000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
    fffff880`01800000 fffff880`01825000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
    fffff880`014d5000 fffff880`014e5000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
    fffff880`00fb8000 fffff880`00fcd000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
    fffff880`01876000 fffff880`018c2000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
    fffff880`02c1d000 fffff880`02c38000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
    fffff880`014e5000 fffff880`014f5000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
    fffff880`00e46000 fffff880`00eea000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
    fffff880`00eea000 fffff880`00ef9000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`02db0000 fffff880`02db9000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff960`00020000 fffff960`00330000   win32k   win32k.sys   unavailable (00000000)
    fffff880`051f5000 fffff880`051fe000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
    fffff880`00f50000 fffff880`00f59000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`06f21000 fffff880`06f42000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
    
    Unloaded modules:
    fffff880`019ae000 fffff880`019bc000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`019bc000 fffff880`019c8000   dump_ataport
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000C000
    fffff880`019c8000 fffff880`019d1000   dump_atapi.s
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00009000
    fffff880`019d1000 fffff880`019e4000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00013000
    fffff880`01800000 fffff880`0182a000   cdrom.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0002A000
    
    
     
  3. PeaceKeeper

    PeaceKeeper New Member

    Joined:
    Jan 16, 2011
    Messages:
    48
    Likes Received:
    0
    After a couple of times in the past few days of removing the ATI drivers, after restarting the pc, my screen hangs in the Windows loading part. Luckily, I managed to uninstall my current ATI drivers, cleaned it using the Driver Sweeper, and restart windows successfully last wednesday. Then I reinstalled the latest ATI drivers.

    Also I was able to completely remove the MagicISO application.

    Yhe last pending item I still haven't completed is the update of Primax Gaming Mouse. I just could not find any way how to update this.

    So far no BSODs encountered after playing games. Rven the new ones I just posted above is now not being seen. I'll post again in a day or two about my status
     
  4. PeaceKeeper

    PeaceKeeper New Member

    Joined:
    Jan 16, 2011
    Messages:
    48
    Likes Received:
    0
    Hello there,

    So far after playing a couple of graphics intensive games, I have not encountered any BSOD when exiting games. Hooray! Thank you Cybercore for your help.

    I guess the setting of the correct RAM frequency and installing the latest ATI drivers did the trick
     
  5. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    You are much welcome, glad to here it's working well after "playing a couple of graphics intensive games" - it's a good sign.

    Enjoy. :)
     

Share This Page

Loading...