BSOD after 10minutes While playing Crossfire!

Page 1 of 4 123 ... LastLast

  1. Posts : 26
    Windows 7 Professional SP1
       #1

    BSOD after 10minutes While playing Crossfire!


    The Title Says It All!
    Here are My System Specs
    Windows 7 Ultimate SP1
    Nvidia GeForce 8400 GS
    Pentium(R) Dual-Core CPU E5300 @ 2.60GHz
    Microsoft PS/2 Mouse
    Standard PS/2 Keyboard


    My Minidumps!!
    Attachment 198007
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #2

    Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with more information and the crash reports. While the minidumps are useful, they are not the most comprehensive information available to allow us to provide informed troubleshooting.

    Your latest crash was caused by Norton. Please remove it using the Norton Removal Tool and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall.
      My Computer


  3. Posts : 26
    Windows 7 Professional SP1
    Thread Starter
       #3

    writhziden said:
    Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with more information and the crash reports. While the minidumps are useful, they are not the most comprehensive information available to allow us to provide informed troubleshooting.

    Your latest crash was caused by Norton. Please remove it using the Norton Removal Tool and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall.
    Here!
    Attachment 198074

    Is Windows 7 . . .
    - x86 (32-bit) or x64 ? X86 (32-Bit)
    - the original installed OS on the system? Windows XP SP3
    - an OEM or full retail version? Full Retail

    - What is the age of system (hardware)? Don't Remember
    - What is the age of OS installation (have you re-installed the OS?) Don't Remember and Yes i re-installed!
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    Given that you have a lot of NTFS sets on the stack, remove Smart Defrag as it is known to cause crashes related to the NTFS driver. Post back if you still have crashes after removing Norton and Smart Defrag.
      My Computer


  5. Posts : 26
    Windows 7 Professional SP1
    Thread Starter
       #5

    writhziden said:
    Given that you have a lot of NTFS sets on the stack, remove Smart Defrag as it is known to cause crashes related to the NTFS driver. Post back if you still have crashes after removing Norton and Smart Defrag.
    I Already Remove Norton and Installs Microsoft Security Essentials - Free Antivirus for Windows but how can i remove smart defrag?
      My Computer


  6. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #6

    Smart Defrag is a freeware program. You should be able to remove it through Start Menu -> Control Panel -> Uninstall a program.
      My Computer


  7. Posts : 26
    Windows 7 Professional SP1
    Thread Starter
       #7

    writhziden said:
    Smart Defrag is a freeware program. You should be able to remove it through Start Menu -> Control Panel -> Uninstall a program.
    Just Uninstalled Norton and Smart Defrag but still BSOD here is my DUMPS!!
    Attachment 198380
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #8

    Code:
    
    Loading Dump File [F:\BSODDmpFiles\devilron24\123\021512-13046-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
    Machine Name:
    Kernel base = 0x82c09000 PsLoadedModuleList = 0x82d49230
    Debug session time: Tue Feb 14 15:00:52.345 2012 (GMT-7)
    System Uptime: 0 days 2:29:09.017
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {c0000005, 91f07bb1, 8e7e29e8, 8e7e25c0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f )
    
    Followup: MachineOwner
    ---------
    
    0: 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: c0000005, The exception code that was not handled
    Arg2: 91f07bb1, The address that the exception occurred at
    Arg3: 8e7e29e8, Exception Record Address
    Arg4: 8e7e25c0, 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: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    91f07bb1 8b31            mov     esi,dword ptr [ecx]
    
    EXCEPTION_RECORD:  8e7e29e8 -- (.exr 0xffffffff8e7e29e8)
    ExceptionAddress: 91f07bb1 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000f)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000000
       Parameter[1]: 00000000
    Attempt to read from address 00000000
    
    CONTEXT:  8e7e25c0 -- (.cxr 0xffffffff8e7e25c0)
    eax=867d9a80 ebx=00000000 ecx=00000000 edx=00000002 esi=86669000 edi=86669000
    eip=91f07bb1 esp=8e7e2ab0 ebp=8e7e2abc iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xf:
    91f07bb1 8b31            mov     esi,dword ptr [ecx]  ds:0023:00000000=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
    
    PROCESS_NAME:  System
    
    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:  00000000
    
    EXCEPTION_PARAMETER2:  00000000
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82d68828
    Unable to read MiSystemVaType memory at 82d48d80
     00000000 
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    91f07bb1 8b31            mov     esi,dword ptr [ecx]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from 91f0b24c to 91f07bb1
    
    STACK_TEXT:  
    8e7e2abc 91f0b24c 867d9a80 00000001 00000000 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xf
    8e7e2bb8 91f22850 971213f0 00000000 84fdd628 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x2f6
    8e7e2d18 91f23141 84d777f8 86f40d90 8e7e2d3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
    8e7e2d28 91f233de 84d777f8 82c37fa2 86633748 dxgmms1!VidSchiSubmitQueueCommand+0x61
    8e7e2d3c 91f23485 86633748 00000000 86636d48 dxgmms1!VidSchiRun_PriorityTable+0x24
    8e7e2d50 82df146a 86633748 ad99475f 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8e7e2d90 82c92989 91f23406 86633748 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1
    
    STACK_COMMAND:  .cxr 0xffffffff8e7e25c0 ; kb
    
    FAILURE_BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    
    BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    
    Followup: MachineOwner
    ---------
    Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

    1. Download the latest drivers for your display card(s)
    2. Click Start Menu
    3. Right Click My Computer/Computer
    4. Click Manage
    5. Click Device Manager from the list on the left
    6. Expand Display adapters
    7. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    8. Restart your computer after uninstalling drivers for all display cards
    9. Install the latest driver for the display cards once Windows starts


    Alternatively:
    1. Login as an adminstrative user
    2. Download the latest drivers for your display card(s)
    3. Click Start Menu
    4. Click Control Panel
    5. Click Hardware and Sound
    6. Click Device Manager (the last link under Devices and Printers)
    7. Expand Display adapters
    8. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Restart your computer after uninstalling drivers for all display cards
    10. Install the latest driver for the display cards once Windows starts





    Update your Realtek Network driver. It is dated pre-Windows 7. Realtek

    Code:
    Rt86win7	91f49000	91f6e000	Thu Feb 26 02:04:22 2009 (49a65b16)	00022867		Rt86win7.sys
    Last edited by writhziden; 14 Feb 2012 at 22:16. Reason: DirectX crash
      My Computer


  9. Posts : 26
    Windows 7 Professional SP1
    Thread Starter
       #9

    writhziden said:
    Code:
    
    Loading Dump File [F:\BSODDmpFiles\devilron24\123\021512-13046-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
    Machine Name:
    Kernel base = 0x82c09000 PsLoadedModuleList = 0x82d49230
    Debug session time: Tue Feb 14 15:00:52.345 2012 (GMT-7)
    System Uptime: 0 days 2:29:09.017
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {c0000005, 91f07bb1, 8e7e29e8, 8e7e25c0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f )
    
    Followup: MachineOwner
    ---------
    
    0: 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: c0000005, The exception code that was not handled
    Arg2: 91f07bb1, The address that the exception occurred at
    Arg3: 8e7e29e8, Exception Record Address
    Arg4: 8e7e25c0, 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: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    91f07bb1 8b31            mov     esi,dword ptr [ecx]
    
    EXCEPTION_RECORD:  8e7e29e8 -- (.exr 0xffffffff8e7e29e8)
    ExceptionAddress: 91f07bb1 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000f)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000000
       Parameter[1]: 00000000
    Attempt to read from address 00000000
    
    CONTEXT:  8e7e25c0 -- (.cxr 0xffffffff8e7e25c0)
    eax=867d9a80 ebx=00000000 ecx=00000000 edx=00000002 esi=86669000 edi=86669000
    eip=91f07bb1 esp=8e7e2ab0 ebp=8e7e2abc iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xf:
    91f07bb1 8b31            mov     esi,dword ptr [ecx]  ds:0023:00000000=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
    
    PROCESS_NAME:  System
    
    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:  00000000
    
    EXCEPTION_PARAMETER2:  00000000
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82d68828
    Unable to read MiSystemVaType memory at 82d48d80
     00000000 
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    91f07bb1 8b31            mov     esi,dword ptr [ecx]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from 91f0b24c to 91f07bb1
    
    STACK_TEXT:  
    8e7e2abc 91f0b24c 867d9a80 00000001 00000000 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xf
    8e7e2bb8 91f22850 971213f0 00000000 84fdd628 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x2f6
    8e7e2d18 91f23141 84d777f8 86f40d90 8e7e2d3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
    8e7e2d28 91f233de 84d777f8 82c37fa2 86633748 dxgmms1!VidSchiSubmitQueueCommand+0x61
    8e7e2d3c 91f23485 86633748 00000000 86636d48 dxgmms1!VidSchiRun_PriorityTable+0x24
    8e7e2d50 82df146a 86633748 ad99475f 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8e7e2d90 82c92989 91f23406 86633748 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1
    
    STACK_COMMAND:  .cxr 0xffffffff8e7e25c0 ; kb
    
    FAILURE_BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    
    BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
    
    Followup: MachineOwner
    ---------
    Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

    1. Download the latest drivers for your display card(s)
    2. Click Start Menu
    3. Right Click My Computer/Computer
    4. Click Manage
    5. Click Device Manager from the list on the left
    6. Expand Display adapters
    7. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    8. Restart your computer after uninstalling drivers for all display cards
    9. Install the latest driver for the display cards once Windows starts


    Alternatively:
    1. Login as an adminstrative user
    2. Download the latest drivers for your display card(s)
    3. Click Start Menu
    4. Click Control Panel
    5. Click Hardware and Sound
    6. Click Device Manager (the last link under Devices and Printers)
    7. Expand Display adapters
    8. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Restart your computer after uninstalling drivers for all display cards
    10. Install the latest driver for the display cards once Windows starts





    Update your Realtek Network driver. It is dated pre-Windows 7. Realtek

    Code:
    Rt86win7	91f49000	91f6e000	Thu Feb 26 02:04:22 2009 (49a65b16)	00022867		Rt86win7.sys
    Finish Installing New Realtek Driver but the Nvidia is not after i launch the installer or extract it an error POPS UP! 7-Zip: Data Error. Please HELP!
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #10

    Try re-installing 7-Zip. If that does not work, please post an image of the error by following the steps in Screenshots and Files - Upload and Post in Seven Forums
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:27.
Find Us