BSOD, help please

The new graphics card should definitely help. Keep us posted.

This latest dump does not tell us very much. The error code is 1A. It is a hardware/hardware related error code.
[quote]
STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel[/auote]

Code:

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


Loading Dump File [C:\Users\Owner\Downloads\081510-14109-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
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 = 0x82c47000 PsLoadedModuleList = 0x82d86570
Debug session time: Sat Aug 14 19:14:03.199 2010 (GMT-4)
System Uptime: 0 days 15:22:43.199
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
1: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 20e1001, 0, c0402000}

Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+21a )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 020e1001
Arg3: 00000000
Arg4: c0402000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82cbfd85 to 82d18574

STACK_TEXT:  
a5019a64 82cbfd85 0000001a 00041284 020e1001 nt!KeBugCheckEx+0x1e
a5019a8c 82cb403b c0809384 c0008384 84000000 nt!MiLocateWsle+0xc1
a5019aa8 82cced19 020e1000 8732b560 00000000 nt!MiTerminateWsle+0x1f
a5019b8c 82cc42fc 8732b370 020e2fff 9525ac9f nt!MiDeleteVirtualAddresses+0x1de
a5019c24 82c7c79a ffffffff a5019d18 a5019d1c nt!NtFreeVirtualMemory+0x60b
a5019c24 82c7a74d ffffffff a5019d18 a5019d1c nt!KiFastCallEntry+0x12a
a5019cac 991b3bed ffffffff a5019d18 a5019d1c nt!ZwFreeVirtualMemory+0x11
a5019d08 82c7c79a 010108d0 00000000 020e0000 win32k!NtGdiCreateDIBSection+0x21a
a5019d08 76fc64f4 010108d0 00000000 020e0000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01afa9f0 00000000 00000000 00000000 00000000 0x76fc64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!NtGdiCreateDIBSection+21a
991b3bed eb0b            jmp     win32k!NtGdiCreateDIBSection+0x227 (991b3bfa)

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  win32k!NtGdiCreateDIBSection+21a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc2a2

FAILURE_BUCKET_ID:  0x1a_41284_win32k!NtGdiCreateDIBSection+21a

BUCKET_ID:  0x1a_41284_win32k!NtGdiCreateDIBSection+21a

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

The dump does not point to a real cause.

You have tested your memory and hard disk to eliminate those. Have you run Driver Verifier since you reinstalled Windows? I know it kept showing Windows drivers the last time you enabled it. If you have not enabled since the reinstall, let's give it a try. Remember, it will cause a crash if it finds a faulty driver. Upload any dumps it triggers.

I suspect Jonathan is right about the problem being your video card.

Please upload the new dump files to us to see if we can get any information out from the new dmp, then we will tell you whether or not to enable driver verifier

Did you ever try the new video card?

Let's see how your system does when you install the new video card.