Previously got BSOD, no longer happens however computer randomly slows

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Kingston\BSODDmpFiles\LiNkZoR\Windows_NT6_BSOD_jcgriff2\021912-14664-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03e55000 PsLoadedModuleList = 0xfffff800`0409a670
Debug session time: Sun Feb 19 10:17:58.278 2012 (GMT-7)
System Uptime: 0 days 2:35:05.645
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffb8a00fa64a48, 1, fffff88005197b7d, 7}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+135 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffb8a00fa64a48, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88005197b7d, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80004104100
 ffffb8a00fa64a48 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+135
fffff880`05197b7d 488908          mov     qword ptr [rax],rcx

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880057b85d0 -- (.trap 0xfffff880057b85d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb8a00fa64a48 rbx=0000000000000000 rcx=fffff8a00fa64a48
rdx=fffff880009f0180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005197b7d rsp=fffff880057b8760 rbp=fffff8a00fa64940
 r8=0000000000000002  r9=0000000000000070 r10=fffff80003e55000
r11=0000000000000175 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po cy
dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x135:
fffff880`05197b7d 488908          mov     qword ptr [rax],rcx ds:ffffb8a0`0fa64a48=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003e7c347 to fffff80003ed1c40

STACK_TEXT:  
fffff880`057b8468 fffff800`03e7c347 : 00000000`00000050 ffffb8a0`0fa64a48 00000000`00000001 fffff880`057b85d0 : nt!KeBugCheckEx
fffff880`057b8470 fffff800`03ecfd6e : 00000000`00000001 ffffb8a0`0fa64a48 fffffa80`00000000 fffff8a0`01adb590 : nt! ?? ::FNODOBFM::`string'+0x44711
fffff880`057b85d0 fffff880`05197b7d : fffffa80`0a75fbc0 fffff8a0`01adb590 00000000`00000001 00000000`000007ff : nt!KiPageFault+0x16e
fffff880`057b8760 fffff880`05192523 : fffffa80`0a8bc4e0 00000000`00000001 fffff8a0`0fa64940 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x135
fffff880`057b8810 fffff880`05178ecc : fffffa80`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`057b88e0 fffff880`03d22ccc : 00000000`00000000 fffff8a0`0fa25000 fffff8a0`0fa25000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`057b8910 fffff880`03d2265f : fffff8a0`0fa25000 fffff8a0`0fa26300 fffff8a0`00000000 00000000`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`057b8a00 fffff880`03d228e1 : fffff8a0`0fa25000 fffff8a0`0fa25000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`057b8a50 fffff880`03d2679c : fffff8a0`0fb6cd00 fffff880`057b8ea0 fffffa80`0863c000 fffff880`03ced3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`057b8aa0 fffff880`03d28e57 : fffff8a0`0fa25000 fffff880`057b8bb0 00000000`7efdb001 fffff880`04cb1201 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`057b8b30 fffff960`001cf51a : 00000000`0008fd20 fffffa80`09dabb60 00000000`00000020 00000000`746c6168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`057b8df0 fffff800`03ed0ed3 : fffffa80`07a18000 fffff880`00000001 fffffa80`05fc6540 00000000`13cfe3e0 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`057b8e20 00000000`746e141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008cab8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x746e141a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+135
fffff880`05197b7d 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+135

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+135

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+135

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

You need to start a backup and let it finish. That will resolve the "Backup in progress" message. I had the same thing at one point on my computer, and that is what cleared it. If you do not want to do a full backup, choose what files to backup and do a very small backup to clear the message.

Could this be responsible for hangs? Hangs still happen, but not as often after i did what you said above.

It's possible. See what happens with the hangs after you get the backup message to go away.

I think my browser is messing up or something, its showing post from a week ago and saying i haven't been on for a week, i had to do a system restore because i tried to turn on computer and it said registry error, then turned off. I ran the SFC /scannow in safe mode, but nothing it said no vunerability issues, or whatever that message is. The svchost still have 55% cpu usage.

I had asked yesterday if you still had 55% usage when in Safe Mode. Can you check on that next?

The server for these forums had a hardware malfunction last night, so the server was recovered from a backup resulting in 18 hours of lost data. That is why your posts from yesterday are missing and your activity is missing.

I went to safe mode and sat with only task manager open for about 10 minutes, nothing spiked or went about ~5%, and the highest svchost that i saw went was only 1%.

Also, after i rebooted after i went into safemode, the theme(i guess its called) got messed up, is there anyway to stop/fix that?

How is it messed up? You can change themes through right clicking the desktop, clicking Personalize, and choosing a different theme or creating your own.

turns white when i turn it on, and then the bar is like the classic windows bar. Anything else that i could do to fix the hanging problem?