BSoD nothings changed


  1. Chirpzilla
    Posts : 8
    Windows 7
       New #1

    BSoD nothings changed


    win7 pro 32bit just installed
    had the same problem on windows XP thought maybe a fresh install would fix it and I get a free upgrade to win 7 pro from my school.

    The system is about a year and a half hold, but the hardware is a little older as a built the computer on a budget.
    Been using a backup hard drive since mine crashed about half a year ago.


    2 gb memory
    amd athlon 64 x2 dual core processor 5400+ 2.80ghz

    hope you guys can tell me whats wrong

    I have a sinking suspicion that this hard drive is finally biting the dust after its long tour of duty.
      My Computer
    Quote Quote

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

    Chirpzilla said:
    win7 pro 32bit just installed
    had the same problem on windows XP thought maybe a fresh install would fix it and I get a free upgrade to win 7 pro from my school.

    The system is about a year and a half hold, but the hardware is a little older as a built the computer on a budget.
    Been using a backup hard drive since mine crashed about half a year ago.


    2 gb memory
    amd athlon 64 x2 dual core processor 5400+ 2.80ghz

    hope you guys can tell me whats wrong

    I have a sinking suspicion that this hard drive is finally biting the dust after its long tour of duty.

    You uploaded the app not the results. Try this method




    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



    To ensure minidumps are enabled:

    Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    Under the Advanced tab, click on the Startup and Recovery Settings... button.
    Ensure that Automatically restart is unchecked.
    Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    OK your way out.
    Reboot if changes have been made.
      My Computer
    Quote Quote

  4. Chirpzilla
    Posts : 8
    Windows 7
    Thread Starter
       New #3

    I just clicked on the EXE not the folder, my mistake -_-
      My Computer
    Quote Quote

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

    Chirpzilla said:
    I just clicked on the EXE not the folder, my mistake -_-
    No problem

    One DMP is always a challenge (no trend to follow) yours is a memory exception caused by the dirextX part of your video driver/card.

    I would re-install the newest driver using this method and run memtest.


    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.


    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

    Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    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\060611-19250-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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82803000 PsLoadedModuleList = 0x8294b810
Debug session time: Mon Jun  6 23:48:16.072 2011 (GMT-4)
System Uptime: 0 days 0:08:20.774
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8d2ddebd, 8a82db64, 8a82d740}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+27 )

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: c0000005, The exception code that was not handled
Arg2: 8d2ddebd, The address that the exception occurred at
Arg3: 8a82db64, Exception Record Address
Arg4: 8a82d740, 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::RemoveCommitment+27
8d2ddebd ff0e            dec     dword ptr [esi]

EXCEPTION_RECORD:  8a82db64 -- (.exr 0xffffffff8a82db64)
ExceptionAddress: 8d2ddebd (dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x00000027)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 01d85b88
Attempt to write to address 01d85b88

CONTEXT:  8a82d740 -- (.cxr 0xffffffff8a82d740)
eax=867b0508 ebx=99504678 ecx=9cad0ee0 edx=8a82dcf8 esi=01d85b88 edi=9cad0c98
eip=8d2ddebd esp=8a82dc2c ebp=8a82dc3c iopl=0         nv up ei pl nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010207
dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x27:
8d2ddebd ff0e            dec     dword ptr [esi]      ds:0023:01d85b88=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

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:  00000001

EXCEPTION_PARAMETER2:  01d85b88

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8296b718
Unable to read MiSystemVaType memory at 8294b160
 01d85b88 

FOLLOWUP_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+27
8d2ddebd ff0e            dec     dword ptr [esi]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 8d2d261e to 8d2ddebd

STACK_TEXT:  
8a82dc3c 8d2d261e 9cad0ee0 867b0508 9cad0c98 dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x27
8a82dc54 8d2d94c4 867b0508 00000000 00000000 dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x1e
8a82dcc4 8d2d9e66 8a82dce0 00000000 8a82dcf8 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x406
8a82dcf0 8d2db4c8 00000000 8a82dd18 8d2ef2cd dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+0x40
8a82dcfc 8d2ef2cd 86cd9898 86c4a008 86c4a008 dxgmms1!VidMmiProcessTerminationCommand+0x10
8a82dd18 8d2f027d 849ce560 8683dbe0 8a82dd3c dxgmms1!VidSchiSubmitDeviceCommand+0x33
8a82dd28 8d2f04cc 86c4a008 8283f3f1 862f3330 dxgmms1!VidSchiSubmitQueueCommand+0xaf
8a82dd3c 8d2f0573 862f3330 00000000 8633e510 dxgmms1!VidSchiRun_PriorityTable+0x24
8a82dd50 82a1166d 862f3330 aeadfd2c 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8a82dd90 828c30d9 8d2f04f4 862f3330 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_DEVICE::RemoveCommitment+27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc265

STACK_COMMAND:  .cxr 0xffffffff8a82d740 ; kb

FAILURE_BUCKET_ID:  0x7E_dxgmms1!VIDMM_DEVICE::RemoveCommitment+27

BUCKET_ID:  0x7E_dxgmms1!VIDMM_DEVICE::RemoveCommitment+27

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: c0000005, The exception code that was not handled
Arg2: 8d2ddebd, The address that the exception occurred at
Arg3: 8a82db64, Exception Record Address
Arg4: 8a82d740, 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::RemoveCommitment+27
8d2ddebd ff0e            dec     dword ptr [esi]

EXCEPTION_RECORD:  8a82db64 -- (.exr 0xffffffff8a82db64)
ExceptionAddress: 8d2ddebd (dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x00000027)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 01d85b88
Attempt to write to address 01d85b88

CONTEXT:  8a82d740 -- (.cxr 0xffffffff8a82d740)
eax=867b0508 ebx=99504678 ecx=9cad0ee0 edx=8a82dcf8 esi=01d85b88 edi=9cad0c98
eip=8d2ddebd esp=8a82dc2c ebp=8a82dc3c iopl=0         nv up ei pl nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010207
dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x27:
8d2ddebd ff0e            dec     dword ptr [esi]      ds:0023:01d85b88=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

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:  00000001

EXCEPTION_PARAMETER2:  01d85b88

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8296b718
Unable to read MiSystemVaType memory at 8294b160
 01d85b88 

FOLLOWUP_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+27
8d2ddebd ff0e            dec     dword ptr [esi]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 8d2d261e to 8d2ddebd

STACK_TEXT:  
8a82dc3c 8d2d261e 9cad0ee0 867b0508 9cad0c98 dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x27
8a82dc54 8d2d94c4 867b0508 00000000 00000000 dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x1e
8a82dcc4 8d2d9e66 8a82dce0 00000000 8a82dcf8 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x406
8a82dcf0 8d2db4c8 00000000 8a82dd18 8d2ef2cd dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+0x40
8a82dcfc 8d2ef2cd 86cd9898 86c4a008 86c4a008 dxgmms1!VidMmiProcessTerminationCommand+0x10
8a82dd18 8d2f027d 849ce560 8683dbe0 8a82dd3c dxgmms1!VidSchiSubmitDeviceCommand+0x33
8a82dd28 8d2f04cc 86c4a008 8283f3f1 862f3330 dxgmms1!VidSchiSubmitQueueCommand+0xaf
8a82dd3c 8d2f0573 862f3330 00000000 8633e510 dxgmms1!VidSchiRun_PriorityTable+0x24
8a82dd50 82a1166d 862f3330 aeadfd2c 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8a82dd90 828c30d9 8d2f04f4 862f3330 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_DEVICE::RemoveCommitment+27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc265

STACK_COMMAND:  .cxr 0xffffffff8a82d740 ; kb

FAILURE_BUCKET_ID:  0x7E_dxgmms1!VIDMM_DEVICE::RemoveCommitment+27

BUCKET_ID:  0x7E_dxgmms1!VIDMM_DEVICE::RemoveCommitment+27

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  7. Chirpzilla
    Posts : 8
    Windows 7
    Thread Starter
       New #5

    The link you provided to Guru3D - Driver Sweeper states that it has been discontinued and the links will not be provided at that site. Not a problem for me I'll use phyxion just wanted to let you know for future reference. I'll get back to you with the test results asap
      My Computer
    Quote Quote

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

    Chirpzilla said:
    The link you provided to Guru3D - Driver Sweeper states that it has been discontinued and the links will not be provided at that site. Not a problem for me I'll use phyxion just wanted to let you know for future reference. I'll get back to you with the test results asap
    Thanks some users report it dead but for continuity I leave it
      My Computer
    Quote Quote

  10. Chirpzilla
    Posts : 8
    Windows 7
    Thread Starter
       New #7

    I reinstalled the drivers, gonna let memtest run over night for a complete scan.
    I'll post the results tomorrow
      My Computer
    Quote Quote

  11. Chirpzilla
    Posts : 8
    Windows 7
    Thread Starter
       New #8

    It's the memory. Luckily my crucial RAM has a lifetime warranty
      My Computer
    Quote Quote

 

  Related Discussions
Does anyone know how the mouse sensitivity can change without any settings being changed on the mouse or in control panel?
Hi guys, so I have a little problem, I've downloaded FileTypesMan because I wanted to change the .exe files appearance on my computer. I did this using this program - all .exe file icons changed, however, with them changed ALL the shortcuts to all the programs that I have on my laptop - now they...
RAMs changed twice still BSOD appear
in BSOD Help and Support

hi guys, i have replaced my rams twice but still some how the BSOD don't leave me alone. I have carried out memtest and found no problems in the slots or the ram. the rams are also of the same frequency and make and slots are also dimm 1 and dimm 0 but still getting BSOD. when ever i play and game...
Names Bryan. got a dell 531s aint sure for the specs right off hand, BUT i got this error code after putting my hard drive into a different tower an I can NOT get it to go away. i've done everything possible that I'd found online an everything. I'm ready to just part it out to my sister & brother...
Windows 7 x64 Windows 7 is the original installed OS Retail Vers. System is a year old OS install is less than 2 Months old I am having issues trying to narrow down what is causing my computer to keep crashing. I have just about changed every single part in my computer and am going nutts....
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 11:26.
Find Us