Problem with blue screen (windows 7 ultimate 32bit)


  1. Posts : 1
    windows 7 ultimate 32bit
       #1

    Problem with blue screen (windows 7 ultimate 32bit)


    Hello, i instaled to my pc windows 7 ultimate 32bit before a week. Everything was ok until blue screnn apears. Pc crash for few seconds and bluescreen apears. It hapens only when i a going to play tha game TRINE. I play tha game normally and then 5 minutes pc crashes , bluescreen and restart.

    BCCode: 1000007e
    BCP1: C0000005
    BCP2: 92145F37
    BCP3: 8C5F59D4
    BCP4: 8C5F55B0
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Please tell me where is the problem..
    My hardware is :

    Motherboard: DFI LANParty UT nF4 SLI-DR Expert
    CPU: DualCore AMD Athlon 64 X2, 2400 MHz (12 x 200) 4800+
    GPU: Point of view NVIDIA GeForce 7800 GTX (512 MB)
    Audio: Realtek ALC850 (AC'97) onboard card
    Hard Disk: Seagatte Baracuda ST3120813AS ATA Device (120 GB, 7200 RPM, SATA-II)
    RAM: OCZ 2x1 GB DDR SDRAM PC3200 EL Platinum Dual Channel (OCZ4002048ELPE)


    I will upload the .dmp i hope will help this. Thank you and sorry for my english!
    Last edited by Ronaldinho1985; 23 Dec 2011 at 05:42.
      My Computer


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

    Run some hardware tests,
    NVIDIA/AMD Video Card - Test with OCCT
    RAM - Test with Memtest86+

    Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.
    Note that this test may overheat the CPU, ensure proper cooling

    Remove IObit Smart Defrag, it has compatibility issues with Windows 7

    Update your Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller driver
    Marvell - Support - Driver Downloads

    Post back with your results
    Is your version of Windows 7 genuine?
    Code:
    yk62x86.sys        0x9201f000    0x9206f000    0x00050000    0x49a2b642    23/02/2009 18:44:18
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 92145f37, The address that the exception occurred at
    Arg3: 8c5f59d4, Exception Record Address
    Arg4: 8c5f55b0, 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_DEVICE::ReferenceCommitment+29
    92145f37 8b5104          mov     edx,dword ptr [ecx+4]
    
    EXCEPTION_RECORD:  8c5f59d4 -- (.exr 0xffffffff8c5f59d4)
    ExceptionAddress: 92145f37 (dxgmms1!VIDMM_DEVICE::ReferenceCommitment+0x00000029)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000000
       Parameter[1]: 00000074
    Attempt to read from address 00000074
    
    CONTEXT:  8c5f55b0 -- (.cxr 0xffffffff8c5f55b0)
    eax=84d0c2d0 ebx=8623d000 ecx=00000070 edx=00000060 esi=84dc8fe0 edi=84d0c2a0
    eip=92145f37 esp=8c5f5a9c ebp=8c5f5aa0 iopl=0         nv up ei ng nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
    dxgmms1!VIDMM_DEVICE::ReferenceCommitment+0x29:
    92145f37 8b5104          mov     edx,dword ptr [ecx+4] ds:0023:00000074=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    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:  00000074
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 829a2848
    Unable to read MiSystemVaType memory at 82981e20
     00000074 
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_DEVICE::ReferenceCommitment+29
    92145f37 8b5104          mov     edx,dword ptr [ecx+4]
    
    BUGCHECK_STR:  0x7E
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    LAST_CONTROL_TRANSFER:  from 9213ebf7 to 92145f37
    
    STACK_TEXT:  
    8c5f5aa0 9213ebf7 84d0c2a0 84ee4044 8623d000 dxgmms1!VIDMM_DEVICE::ReferenceCommitment+0x29
    8c5f5ab8 921409be 00000000 84d0c2a0 00000001 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x67
    8c5f5bb8 92157850 96501d40 00000000 84d90210 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xa68
    8c5f5d18 92158141 84d33f08 84da4828 8c5f5d3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
    8c5f5d28 921583de 84d33f08 82870509 86227350 dxgmms1!VidSchiSubmitQueueCommand+0x61
    8c5f5d3c 92158485 86227350 00000000 8623c410 dxgmms1!VidSchiRun_PriorityTable+0x24
    8c5f5d50 82a41fda 86227350 ad2a219e 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8c5f5d90 828ea1f9 92158406 86227350 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VIDMM_DEVICE::ReferenceCommitment+29
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1
    
    STACK_COMMAND:  .cxr 0xffffffff8c5f55b0 ; kb
    
    FAILURE_BUCKET_ID:  0x7E_dxgmms1!VIDMM_DEVICE::ReferenceCommitment+29
    
    BUCKET_ID:  0x7E_dxgmms1!VIDMM_DEVICE::ReferenceCommitment+29
    
    Followup: MachineOwner
    ---------
      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 03:34.
Find Us