Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSoD nothings changed

06 Jun 2011   #1

Windows 7
 
 
BSoD nothings changed

Windows 7 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 System SpecsSystem Spec
.

06 Jun 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Chirpzilla View Post
Windows 7 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 System SpecsSystem Spec
06 Jun 2011   #3

Windows 7
 
 

I just clicked on the EXE not the folder, my mistake -_-
My System SpecsSystem Spec
.


07 Jun 2011   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Chirpzilla View Post
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 System SpecsSystem Spec
07 Jun 2011   #5

Windows 7
 
 

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 System SpecsSystem Spec
07 Jun 2011   #6

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Chirpzilla View Post
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 System SpecsSystem Spec
07 Jun 2011   #7

Windows 7
 
 

I reinstalled the drivers, gonna let memtest run over night for a complete scan.
I'll post the results tomorrow
My System SpecsSystem Spec
07 Jun 2011   #8

Windows 7
 
 

It's the memory. Luckily my crucial RAM has a lifetime warranty
My System SpecsSystem Spec
Reply

 BSoD nothings changed




Thread Tools



Similar help and support threads for2: BSoD nothings changed
Thread Forum
BSOD related to memory management (even after changed RAM) BSOD Help and Support
Solved RAMs changed twice still BSOD appear BSOD Help and Support
BSOD that changed resolution and restarted computer BSOD Help and Support
Error Code 0x490. Read every forum on the site an nothings worked.... General Discussion
Solved Common BSOD/changed boot disk Performance & Maintenance
BSOD when I changed Graphic card BSOD Help and Support
BSOD Win7 X64 error! changed major components and still BSOD! BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 07:16 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33