BSOD When Surfing the Internet / Screen...Very Annoying Freezes


  1. Posts : 4
    Windows 7 Ultimate x64
       #1

    BSOD When Surfing the Internet / Screen...Very Annoying Freezes


    I got a new custom built computer a month ago, and it's been quite some time since I have been struggling with constant BSODs. I formatted and upgraded from Vista to Windows 7, but still the BSODs persist. The computer seems to BSOD once a while as I'm surfing on Firefox. If that doesn't happen, the screen will freeze up and I get the message "display driver has stopped working and has recovered successfully". All the BSODs have to do with 0x01 memory management. I think it might have something to do with my graphics card. I'll really appreciate some help with this. Thanks for the help.

    System specs:
    Windows 7 Ultimate x64 Retail
    Intel i5 2500k Sandy Bridge
    2 x 4GB Ram
    Gigabyte Radeon HD 6950
    700W power supply
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    darkxstorm said:
    I got a new custom built computer a month ago, and it's been quite some time since I have been struggling with constant BSODs. I formatted and upgraded from Vista to Windows 7, but still the BSODs persist. The computer seems to BSOD once a while as I'm surfing on Firefox. If that doesn't happen, the screen will freeze up and I get the message "display driver has stopped working and has recovered successfully". All the BSODs have to do with 0x01 memory management. I think it might have something to do with my graphics card. I'll really appreciate some help with this. Thanks for the help.

    System specs:
    Windows 7 Ultimate x64 Retail
    Intel i5 2500k Sandy Bridge
    2 x 4GB Ram
    Gigabyte Radeon HD 6950
    700W power supply

    Most of these were cuased by your video driver (or card)

    I would re-install using this method and the newest version you can find.

    When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

    Or Phyxion.net - Driver Sweeper

    When it is removed then download and install the fresh copy.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\052011-19578-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;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`0305b650
    Debug session time: Fri May 20 23:05:50.429 2011 (GMT-4)
    System Uptime: 0 days 4:04:55.272
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................
    Loading User Symbols
    Loading unloaded module list
    ...........
    Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A0000001, {5, 0, 0, 0}
    
    Probably caused by : atikmdag.sys ( atikmdag+4a0a1 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Unknown bugcheck code (a0000001)
    Unknown bugcheck description
    Arguments:
    Arg1: 0000000000000005
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA0000001
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  a
    
    LAST_CONTROL_TRANSFER:  from fffff880048cd0a1 to fffff80002e95d00
    
    STACK_TEXT:  
    fffff800`00b9c518 fffff880`048cd0a1 : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9c520 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x4a0a1
    fffff800`00b9c528 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`00000000 : 0xa0000001
    fffff800`00b9c530 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`00000000 00000000`00000000 : 0x5
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+4a0a1
    fffff880`048cd0a1 ??              ???
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  atikmdag+4a0a1
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d7702d1
    
    FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+4a0a1
    
    BUCKET_ID:  X64_0xA0000001_atikmdag+4a0a1
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thanks for the reply. I have tried what you have suggested. I use Phyxion to remove the ATI driver and later reinstalled it. I also turned off overclocking. However, the BSOD still occurs as I am surfing the internet; there doesn't seem to be any difference. What could be causing the problem?
      My Computer


  4. Posts : 1
    Win 7
       #4

    looking at the first message it uses a vista ati driver in windows 7,
    are you sure you have the correct driver for windows 7?

    els maybe try to see what another browser can do for you like Opera or firefox to see if this couses same issues perhaps.
    Let us know
    Regards
      My Computer


  5. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #5

    It's been a couple days and I'm still receiving BSODs. I discovered that the BSOD might not be limited to only browsers, as I have been getting crashes/freezes while playing games as well. Sometimes my screen will freeze with "display driver has stopped working and has recovered successfully" when I load up MineCraft. Here's another BSOD that I got while playing Street Fighter IV:
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    darkxstorm said:
    It's been a couple days and I'm still receiving BSODs. I discovered that the BSOD might not be limited to only browsers, as I have been getting crashes/freezes while playing games as well. Sometimes my screen will freeze with "display driver has stopped working and has recovered successfully" when I load up MineCraft. Here's another BSOD that I got while playing Street Fighter IV:
    With the limited information in the snip I can tell you that it was provably caused by the directX portion of your video driver. It is also indicative of a video card problem.

    Please upload the DMP file so we can run it.
      My Computer


  7. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Thanks for the reply. I have uploaded the dump file of the latest BSOD that I had.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    darkxstorm said:
    Thanks for the reply. I have uploaded the dump file of the latest BSOD that I had.
    As I thought. Your DX video driver or card.

    Please re-install using this.

    When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

    Or if the above doesnt work for you. Phyxion.net - Driver Sweeper

    When it is removed then download and install the fresh copy.




    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\052211-22089-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;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`02e04000 PsLoadedModuleList = 0xfffff800`03049650
    Debug session time: Mon May 23 02:56:11.857 2011 (GMT-4)
    System Uptime: 0 days 14:05:47.732
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 10E, {1f, fffff8a00f4991e0, 0, 20193e}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
    The video memory manager encountered a condition that it can't recover from. By crashing,
    the video memory manager is attempting to get enough information into the minidump such that
    somebody can pinpoint what lead to this condition.
    Arguments:
    Arg1: 000000000000001f, The subtype of the bugcheck:
    Arg2: fffff8a00f4991e0
    Arg3: 0000000000000000
    Arg4: 000000000020193e
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x10e_1f
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff8800145f22f to fffff80002e83d00
    
    STACK_TEXT:  
    fffff880`059d9738 fffff880`0145f22f : 00000000`0000010e 00000000`0000001f fffff8a0`0f4991e0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`059d9740 fffff880`04391098 : fffff8a0`0f4991e0 fffff8a0`0f4991e0 00000000`0020193e 00000000`00000000 : watchdog!WdLogEvent5+0x11b
    fffff880`059d9790 fffff880`0438e8af : 00000000`00000000 fffffa80`0a70b980 00000000`00000c3a fffffa80`0aac1c88 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148
    fffff880`059d97d0 fffff880`043a865d : 00000000`00000000 fffff8a0`0ef1b860 fffffa80`00000000 fffffa80`0a60b430 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
    fffff880`059d99a0 fffff880`043a8398 : fffff880`02f69f40 fffff880`043a7d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`059d9b90 fffff880`043a7e96 : 00000000`00000000 fffffa80`0a7fa730 00000000`00000080 fffffa80`086e0410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`059d9bc0 fffff800`0312032e : 00000000`032136fa fffffa80`08cbda10 fffffa80`066edb30 fffffa80`08cbda10 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`059d9c00 fffff800`02e75666 : fffff880`02f65180 fffffa80`08cbda10 fffff880`02f6ffc0 fffff880`01269384 : nt!PspSystemThreadStartup+0x5a
    fffff880`059d9c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
    fffff880`04391098 c7442450c5f3ffff mov     dword ptr [rsp+50h],0FFFFF3C5h
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    FAILURE_BUCKET_ID:  X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
    
    BUCKET_ID:  X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
    
    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 05:08.
Find Us