I will reply in this thread, because you created 2 with the same problem.
Both BSoDs point to a hardware conflict or problem.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\David\AppData\Local\Temp\7zO40DA.tmp\070310-17265-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.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82c0f000 PsLoadedModuleList = 0x82d4e570
Debug session time: Sat Jul 3 05:08:50.774 2010 (UTC - 7:00)
System Uptime: 0 days 0:04:10.180
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {d, 0, 0, 0}
Probably caused by : win32k.sys ( win32k!GreExtGetObjectW+125 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 951e3dee to 82c482bb
STACK_TEXT:
8e4bab0c 951e3dee badb0d00 021d0570 86a40858 nt!KiSystemFatalException+0xf
8e4bab94 95189dab 8485080a 00000018 8e4babac win32k!GreExtGetObjectW+0x125
8e4babd4 95188e02 8485080a 00000000 00000000 win32k!GetWallpaperCenterRect+0x19
8e4bac20 95189d6f fe199de8 90010f6e 8e4bac40 win32k!CenterOrStretchWallpaper+0x5d
8e4bac54 9517fa7e fe199de8 fe800618 90010f6e win32k!xxxDrawWallpaper+0x86
8e4bac9c 951888a7 ff5d1d28 90010f6e 8e4bacc4 win32k!xxxDesktopPaintCallback+0x166
8e4bad20 82c4479a 00010001 90010f6e 003fe988 win32k!NtUserPaintMonitor+0xcb
8e4bad20 774764f4 00010001 90010f6e 003fe988 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
003fe9b4 00000000 00000000 00000000 00000000 0x774764f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!GreExtGetObjectW+125
951e3dee e89aa10000 call win32k!SURFREF::SURFREF (951edf8d)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: win32k!GreExtGetObjectW+125
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bdc3f5e
FAILURE_BUCKET_ID: 0x7f_d_win32k!GreExtGetObjectW+125
BUCKET_ID: 0x7f_d_win32k!GreExtGetObjectW+125
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\David\AppData\Local\Temp\7zOD616.tmp\070310-15968-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.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82c56000 PsLoadedModuleList = 0x82d95570
Debug session time: Sat Jul 3 07:47:10.125 2010 (UTC - 7:00)
System Uptime: 0 days 0:00:21.531
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, 8ba4a02b, 9acc9a38, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+dc )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c000001d, The exception code that was not handled
Arg2: 8ba4a02b, The address that the exception occurred at
Arg3: 9acc9a38, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
+dc
8ba4a02b ?? ???
TRAP_FRAME: 9acc9b10 -- (.trap 0xffffffff9acc9b10)
ErrCode = 00000003
eax=024b0000 ebx=98580003 ecx=8ba4a02b edx=00000ffc esi=9859cd53 edi=861d0108
eip=82e82967 esp=9acc9b84 ebp=9acc9b84 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!MiDoSingleFixup+0x29:
82e82967 0101 add dword ptr [ecx],eax ds:0023:8ba4a02b=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 9859cd53 to 8ba4a02b
FAILED_INSTRUCTION_ADDRESS:
+dc
8ba4a02b ?? ???
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
9acc9aa8 9859cd53 9acc9b84 21cc9ab0 82d81d00 0x8ba4a02b
9acc9af8 82c8e988 00000001 8ba4a02b 00000000 0x9859cd53
9acc9af8 82e82967 00000001 8ba4a02b 00000000 nt!KiTrap0E+0xdc
9acc9b84 82e829d7 024b0000 00000fff 98580000 nt!MiDoSingleFixup+0x29
9acc9b98 82ea7ab8 8ba4a000 024b0000 98580000 nt!MiApplyCompressedFixups+0x62
9acc9bd4 82eacbe0 861d0108 024b0000 00000001 nt!MiPerformFixups+0x6d
9acc9bfc 82cf0c1e 861d0108 00000000 0000039f nt!MiRelocateImagePfn+0xf1
9acc9c5c 82d025db 9acc9c88 86708f30 9acc9c94 nt!MiWaitForInPageComplete+0x152
9acc9cac 82cb7143 86708f30 7604f1f7 8670db41 nt!MiIssueHardFault+0x3b6
9acc9d1c 82c8e988 00000000 7604f1f7 00000001 nt!MmAccessFault+0x25b9
9acc9d1c 7604f1f7 00000000 7604f1f7 00000001 nt!KiTrap0E+0xdc
02d6e7ac 00000000 00000000 00000000 00000000 0x7604f1f7
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+dc
82c8e988 85c0 test eax,eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiTrap0E+dc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cac3
FAILURE_BUCKET_ID: 0x8E_BAD_IP_nt!KiTrap0E+dc
BUCKET_ID: 0x8E_BAD_IP_nt!KiTrap0E+dc
Followup: MachineOwner
---------
~Lordbob
Quote