Sudden memorydumps and Bluescreens

Ubetjent · 04 Aug 2010

Hi everyone.

I've been looking for a solution to my random bluescreens and memorydumps for some days now. I installed Windows 7 (x86) on my computer about two months ago, and haven't used it before a week ago.

What I have tried to fix the problem with:

Updating all drivers on my system
Installing new RAM
Reinstalling Windows

None of these seem to do the trick, so I'm not sure what to do anymore except asking you guys. :)

My system originally came with Windows xp professional (x86).
However, this was before windows 7 was released.
My OS now is full retail.

I bought the system in March, 2008

Added a performance scan like instructed

CarlTR6 · 04 Aug 2010

While a look at the rest of your dumps, uninstall Deamon Tools or any other virual CD program you are running. The driver SPTD.sys appears to have cause at least one of the crashes. SPTD.sys is a known cause of crashes.

I will be back with more.

Ubetjent · 04 Aug 2010

Alright Carl. Thanks alot. I'll stand by and wait for more info.
I've also uninstalled Deamon Tools now.

CarlTR6 · 04 Aug 2010

Your crashes are caused by hardware or hardware related problems. here are the error codes and their usual causes. Notice the causes in common in these error codes. This is where will will start looking.

Good job on uninstalling Deamon Tools.

STOP 0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

Usual causes: Device driver

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver

Here are the actual dumps.

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Documents.zip\Windows7_BSOD_jcgriff2\080410-18564-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
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 = 0x8343d000 PsLoadedModuleList = 0x83585810
Debug session time: Wed Aug  4 17:39:28.545 2010 (GMT-4)
System Uptime: 0 days 1:09:34.418
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
1: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {8b60fce4, 1460b963, 8b60fc38, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )

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

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 8b60fce4, Virtual address for the attempted execute.
Arg2: 1460b963, PTE contents.
Arg3: 8b60fc38, (reserved)
Arg4: 00000000, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  Installer.exe

CURRENT_IRQL:  7

TRAP_FRAME:  8b60fc38 -- (.trap 0xffffffff8b60fc38)
ErrCode = 00000011
eax=00000101 ebx=8340b844 ecx=00000007 edx=00000000 esi=84d6a52c edi=84d6a008
eip=8b60fce4 esp=8b60fcac ebp=8b60fccc iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210206
8b60fce4 70ef            jo      8b60fcd5                                [br=0]
Resetting default scope

LAST_CONTROL_TRANSFER:  from 83483638 to 834c2903

STACK_TEXT:  
8b60fc20 83483638 00000008 8b60fce4 00000000 nt!MmAccessFault+0x106
8b60fc20 8b60fce4 00000008 8b60fce4 00000000 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
8b60fccc 00000000 00000000 834a5ed0 f70f2e80 0x8b60fce4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTrap0E+dc
83483638 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiTrap0E+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cacf

FAILURE_BUCKET_ID:  0xFC_nt!KiTrap0E+dc

BUCKET_ID:  0xFC_nt!KiTrap0E+dc

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Documents.zip\Windows7_BSOD_jcgriff2\080310-20576-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
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 = 0x83419000 PsLoadedModuleList = 0x83561810
Debug session time: Tue Aug  3 11:10:27.716 2010 (GMT-4)
System Uptime: 0 days 0:27:02.480
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fd80cbec, 0, 945519a1, 0}


Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!CopySurfBitsFast+e5 )

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

0: 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: fd80cbec, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 945519a1, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 83581718
Unable to read MiSystemVaType memory at 83561160
 fd80cbec 

FAULTING_IP: 
cdd!CopySurfBitsFast+e5
945519a1 f30f6f06        movdqu  xmm0,xmmword ptr [esi]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  8d237268 -- (.trap 0xffffffff8d237268)
ErrCode = 00000000
eax=00000000 ebx=00000001 ecx=00000045 edx=00000020 esi=fd80cbe4 edi=a183a370
eip=945519a1 esp=8d2372dc ebp=8d2372f4 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
cdd!CopySurfBitsFast+0xe5:
945519a1 f30f6f06        movdqu  xmm0,xmmword ptr [esi] ds:0023:fd80cbe4=????????????????????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8345f638 to 8349e903

STACK_TEXT:  
8d237250 8345f638 00000000 fd80cbec 00000000 nt!MmAccessFault+0x106
8d237250 945519a1 00000000 fd80cbec 00000000 nt!KiTrap0E+0xdc
8d2372f4 94551d09 a183a370 00001000 fd80cbe4 cdd!CopySurfBitsFast+0xe5
8d237350 945633bb a1800370 00001000 fd80d14c cdd!CopySurfBits+0x81
8d2376dc 94563d74 ffb51010 fe928dc0 fd80d010 cdd!BitBltBitmap+0x3eb
8d237890 9456482f fe928dc0 fd80d010 00000000 cdd!DrvBitBlt+0xc2
8d2378c4 94398e0f fe928dc0 fd80d010 ffb5b7c8 cdd!DrvCopyBits+0x27
8d23790c 9437eab4 94564808 8d237b9c fe928dc0 win32k!OffCopyBits+0x7d
8d237bb0 9439c3e9 fe928dc0 fd80d010 00000000 win32k!SpBitBlt+0x252
8d237be4 9439cc3b fe928dc0 fd80d010 ffb5b7c8 win32k!SpCopyBits+0x27
8d237ccc 94384e1e fdf8c2e8 944d42f0 fdf8c2e8 win32k!NtGdiBitBltInternal+0x6ab
8d237d00 8345c44a 0a010b5f 0000001c 00000000 win32k!NtGdiBitBlt+0x2f
8d237d00 775e64f4 0a010b5f 0000001c 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012eec8 00000000 00000000 00000000 00000000 0x775e64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd!CopySurfBitsFast+e5
945519a1 f30f6f06        movdqu  xmm0,xmmword ptr [esi]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  cdd!CopySurfBitsFast+e5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bd992

FAILURE_BUCKET_ID:  0x50_cdd!CopySurfBitsFast+e5

BUCKET_ID:  0x50_cdd!CopySurfBitsFast+e5

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Documents.zip\Windows7_BSOD_jcgriff2\080310-19328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
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 = 0x83443000 PsLoadedModuleList = 0x8358b810
Debug session time: Mon Aug  2 21:17:29.348 2010 (GMT-4)
System Uptime: 0 days 1:20:36.986
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
1: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {a200f9c0, 72416963, a200f908, 0}

Probably caused by : hardware

Followup: MachineOwner
---------
 *** Possible invalid call from 834e01a2 ( nt!KeContextToKframes+0x350 )
 *** Expected target 834dfdcb ( nt!KiRecordDr7+0x0 )

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: a200f9c0, Virtual address for the attempted execute.
Arg2: 72416963, PTE contents.
Arg3: a200f908, (reserved)
Arg4: 00000000, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  StarCraft_2_EU

CURRENT_IRQL:  7

TRAP_FRAME:  a200f908 -- (.trap 0xffffffffa200f908)
ErrCode = 00000011
eax=00000000 ebx=85671008 ecx=864310b8 edx=0000ff07 esi=85b63ae0 edi=864903f4
eip=a200f9c0 esp=a200f97c ebp=a200fd34 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
a200f9c0 d2f7            sal     bh,cl
Resetting default scope

LAST_CONTROL_TRANSFER:  from 834e01a7 to a200f9c0

POSSIBLE_INVALID_CONTROL_TRANSFER:  from 834e01a2 to 834dfdcb

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
a200f978 834e01a7 00010017 a200f9c0 872ea4a0 0xa200f9c0
a200fd34 778864f4 badb0d00 00bdfdd4 00000000 nt!KeContextToKframes+0x355
a200fd38 badb0d00 00bdfdd4 00000000 00000000 0x778864f4
a200fd3c 00bdfdd4 00000000 00000000 00000000 0xbadb0d00
a200fd40 00000000 00000000 00000000 00000000 0xbdfdd4


STACK_COMMAND:  .trap 0xffffffffa200f908 ; kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CPU_CALL_ERROR

Followup: MachineOwner
---------
 *** Possible invalid call from 834e01a2 ( nt!KeContextToKframes+0x350 )
 *** Expected target 834dfdcb ( nt!KiRecordDr7+0x0 )



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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Documents.zip\Windows7_BSOD_jcgriff2\080210-20810-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
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 = 0x82e55000 PsLoadedModuleList = 0x82f9d810
Debug session time: Mon Aug  2 18:53:54.219 2010 (GMT-4)
System Uptime: 0 days 3:25:26.323
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fd907984, 0, 824019a1, 0}


Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!CopySurfBitsFast+e5 )

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

0: 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: fd907984, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 824019a1, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 82fbd718
Unable to read MiSystemVaType memory at 82f9d160
 fd907984 

FAULTING_IP: 
cdd!CopySurfBitsFast+e5
824019a1 f30f6f06        movdqu  xmm0,xmmword ptr [esi]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  a2c23268 -- (.trap 0xffffffffa2c23268)
ErrCode = 00000000
eax=00000000 ebx=00000001 ecx=00000050 edx=00000020 esi=fd90797c edi=a41a5d00
eip=824019a1 esp=a2c232dc ebp=a2c232f4 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
cdd!CopySurfBitsFast+0xe5:
824019a1 f30f6f06        movdqu  xmm0,xmmword ptr [esi] ds:0023:fd90797c=????????????????????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e9b638 to 82eda903

STACK_TEXT:  
a2c23250 82e9b638 00000000 fd907984 00000000 nt!MmAccessFault+0x106
a2c23250 824019a1 00000000 fd907984 00000000 nt!KiTrap0E+0xdc
a2c232f4 82401d09 a41a5d00 00001100 fd90797c cdd!CopySurfBitsFast+0xe5
a2c23350 824133bb a4199100 00001100 fd92014c cdd!CopySurfBits+0x81
a2c236dc 82413d74 ffb51010 fdf86818 fd920010 cdd!BitBltBitmap+0x3eb
a2c23890 8241482f fdf86818 fd920010 00000000 cdd!DrvBitBlt+0xc2
a2c238c4 82638e0f fdf86818 fd920010 fe47b7c8 cdd!DrvCopyBits+0x27
a2c2390c 8261eab4 82414808 a2c23b9c fdf86818 win32k!OffCopyBits+0x7d
a2c23bb0 8263c3e9 fdf86818 fd920010 00000000 win32k!SpBitBlt+0x252
a2c23be4 8263cc3b fdf86818 fd920010 fe47b7c8 win32k!SpCopyBits+0x27
a2c23ccc 82624e1e fdf97008 827742f0 fdf97008 win32k!NtGdiBitBltInternal+0x6ab
a2c23d00 82e9844a 0601116c 0000001c 00000082 win32k!NtGdiBitBlt+0x2f
a2c23d00 779d64f4 0601116c 0000001c 00000082 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0019e688 00000000 00000000 00000000 00000000 0x779d64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd!CopySurfBitsFast+e5
824019a1 f30f6f06        movdqu  xmm0,xmmword ptr [esi]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  cdd!CopySurfBitsFast+e5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bd992

FAILURE_BUCKET_ID:  0x50_cdd!CopySurfBitsFast+e5

BUCKET_ID:  0x50_cdd!CopySurfBitsFast+e5

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Documents.zip\Windows7_BSOD_jcgriff2\080210-19952-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
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 = 0x82a1f000 PsLoadedModuleList = 0x82b67810
Debug session time: Sun Aug  1 21:46:10.158 2010 (GMT-4)
System Uptime: 0 days 2:26:02.922
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 9, 1, 8880c4cc}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : PCIIDEX.SYS ( PCIIDEX!___PchSym_+2a4 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000009, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8880c4cc, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b87718
Unable to read MiSystemVaType memory at 82b67160
 00000000 

CURRENT_IRQL:  9

FAULTING_IP: 
PCIIDEX!___PchSym_+2a4
8880c4cc 0000            add     byte ptr [eax],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  807df91c -- (.trap 0xffffffff807df91c)
ErrCode = 00000002
eax=00000000 ebx=855fe3f4 ecx=855a70b8 edx=0000ff01 esi=84c17ca0 edi=855fe3f8
eip=8880c4cc esp=807df990 ebp=807df998 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
PCIIDEX!___PchSym_+0x2a4:
8880c4cc 0000            add     byte ptr [eax],al          ds:0023:00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8880c4cc to 82a6582b

STACK_TEXT:  
807df91c 8880c4cc badb0d00 0000ff01 88a42e6b nt!KiTrap0E+0x2cf
807df998 8882dcfa 855fe3f8 84c17ca0 00000000 PCIIDEX!___PchSym_+0x2a4
807df9c0 8882de3a 505fe3f4 84c17c68 8487152c atapi!AtapiSendAtaCommand+0xa8
807df9d8 8882de8d 855fe3f4 84c17c68 807dfa08 atapi!AtapiHandleAtaCommand+0x36
807df9e8 8884a83b 855fe3f4 84c17c68 855fd0e0 atapi!AtapiHwStartIo+0x29
WARNING: Stack unwind information not available. Following frames may be wrong.
807dfa08 88a3a6a5 84871008 855fe3f4 84c17c68 sptd+0x1383b
807dfa24 88a3fa51 855fd0e0 84c179e0 8562f9c0 ataport!CallMiniPortHwStartIo+0x87
807dfa40 82a5e43d 84c179e0 855fd002 855fd0e0 ataport!IdeStartCrbSynchronized+0x61
807dfa64 88a40147 855fd0e0 88a3f9f0 84c179e0 nt!KeSynchronizeExecution+0x3d
807dfa90 88808074 84c179e0 807dfac8 82e33a2e ataport!IdeStartIoCallBack+0xbb
807dfa9c 82e33a2e 855d1030 00000000 84c17a3c PCIIDEX!BmReceiveScatterGatherList+0x1e
807dfac8 88808199 84c17a3c 855d1030 864cce30 hal!HalBuildScatterGatherList+0x1ba
807dfb04 88a3fb46 855d10e8 84c179e0 84c17901 PCIIDEX!BmSetup+0x3d
807dfb20 88a40041 855fd0e0 84c17901 84c179e0 ataport!IdePortSetupScatterGatherList+0x2a
807dfb38 88a3ea12 855fd0e0 84c179e0 84c86f9a ataport!IdeDispatchChannelRequest+0x59
807dfb50 88a3ec6a 855fd0e0 84c179e0 84c86d10 ataport!IdeStartChannelRequest+0x42
807dfb64 88a402a0 8562f9c0 84c86d10 855fd0e0 ataport!IdeStartNextDeviceRequest+0x22
807dfbd8 88a4066b 855fd0e0 84c86d10 8486d008 ataport!IdeProcessCompletedRequests+0xd8
807dfc2c 88848894 855fd09c 855fd028 00000000 ataport!IdePortCompletionDpc+0xab
807dfc78 82a873b5 855fd09c 855fd028 00000000 sptd+0x11894
807dfcd4 82a87218 807c3120 807c8800 00000000 nt!KiExecuteAllDpcs+0xf9
807dfd20 82a87038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
807dfd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
PCIIDEX!___PchSym_+2a4
8880c4cc 0000            add     byte ptr [eax],al

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  PCIIDEX!___PchSym_+2a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PCIIDEX

IMAGE_NAME:  PCIIDEX.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf13

FAILURE_BUCKET_ID:  0xD1_PCIIDEX!___PchSym_+2a4

BUCKET_ID:  0xD1_PCIIDEX!___PchSym_+2a4

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Documents.zip\Windows7_BSOD_jcgriff2\080210-17472-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
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 = 0x82a47000 PsLoadedModuleList = 0x82b8f810
Debug session time: Tue Jul 20 10:05:00.397 2010 (GMT-4)
System Uptime: 0 days 0:32:53.036
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {806014cc, 9, 8, 806014cc}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : atapi.sys ( atapi!AtapiSendAtaCommand+a8 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 806014cc, memory referenced
Arg2: 00000009, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 806014cc, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82baf718
Unable to read MiSystemVaType memory at 82b8f160
 806014cc 

CURRENT_IRQL:  9

FAULTING_IP: 
+60d0952f01efda04
806014cc ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  807df91c -- (.trap 0xffffffff807df91c)
ErrCode = 00000010
eax=00000000 ebx=856003f4 ecx=855a50b8 edx=0000ff01 esi=84a522c8 edi=856003f8
eip=806014cc esp=807df990 ebp=807df998 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
806014cc ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 806014cc to 82a8d82b

FAILED_INSTRUCTION_ADDRESS: 
+60d0952f01efda04
806014cc ??              ???

STACK_TEXT:  
807df91c 806014cc badb0d00 0000ff01 88a15e6b nt!KiTrap0E+0x2cf
WARNING: Frame IP not in any known module. Following frames may be wrong.
807df98c 856003f8 84a52290 807df9c0 88602cfa 0x806014cc
807df998 88602cfa 856003f8 84a522c8 00000000 0x856003f8
807df9c0 88602e3a 506003f4 84a52290 8487152c atapi!AtapiSendAtaCommand+0xa8
807df9d8 88602e8d 856003f4 84a52290 807dfa08 atapi!AtapiHandleAtaCommand+0x36
807df9e8 8883d83b 856003f4 84a52290 855ff0e0 atapi!AtapiHwStartIo+0x29
807dfa08 88a0d6a5 84871008 856003f4 84a52290 sptd+0x1383b
807dfa24 88a12a51 855ff0e0 84a52008 856310e8 ataport!CallMiniPortHwStartIo+0x87
807dfa40 82a8643d 84a52008 855ff002 855ff0e0 ataport!IdeStartCrbSynchronized+0x61
807dfa64 88a13147 855ff0e0 88a129f0 84a52008 nt!KeSynchronizeExecution+0x3d
807dfa90 88801074 84a52008 807dfac8 82a14a2e ataport!IdeStartIoCallBack+0xbb
807dfa9c 82a14a2e 8482f030 00000000 84a52064 PCIIDEX!BmReceiveScatterGatherList+0x1e
807dfac8 88801199 84a52064 8482f030 85cfc7e0 hal!HalBuildScatterGatherList+0x1ba
807dfb04 88a12b46 8482f0e8 84a52008 84a52001 PCIIDEX!BmSetup+0x3d
807dfb20 88a13041 855ff0e0 84a52001 84a52008 ataport!IdePortSetupScatterGatherList+0x2a
807dfb38 88a11a12 855ff0e0 84a52008 84a9edba ataport!IdeDispatchChannelRequest+0x59
807dfb50 88a11c6a 855ff0e0 84a52008 84a9eb30 ataport!IdeStartChannelRequest+0x42
807dfb64 88a132a0 856310e8 84a9eb30 855ff0e0 ataport!IdeStartNextDeviceRequest+0x22
807dfbd8 88a1366b 855ff0e0 84a9eb30 8486d008 ataport!IdeProcessCompletedRequests+0xd8
807dfc2c 8883b894 855ff09c 855ff028 00000000 ataport!IdePortCompletionDpc+0xab
807dfc78 82aaf3b5 855ff09c 855ff028 00000000 sptd+0x11894
807dfcd4 82aaf218 807c3120 807c8800 00000000 nt!KiExecuteAllDpcs+0xf9
807dfd20 82aaf038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
807dfd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atapi!AtapiSendAtaCommand+a8
88602cfa 6a01            push    1

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atapi!AtapiSendAtaCommand+a8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atapi

IMAGE_NAME:  atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf13

FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_atapi!AtapiSendAtaCommand+a8

BUCKET_ID:  0xD1_CODE_AV_BAD_IP_atapi!AtapiSendAtaCommand+a8

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

We will first tackle device drivers since that is common in all of the dumps. The first one to eliminate is sptd.sys and you have done that. I forgot to tell you to run the sptd removal tool: DuplexSecure - Downloads. Use it to uninstall, not reinstall.

I found the following out of date driver on your system. Generally Win 7 does like older drivers. They can and do cause conflicts and crashes.

Rt86win7.sys Thu Feb 26 04:04:22 2009 - Realtek 8101E/8168/8169 NDIS 6.20 32-bit Driver. Realtek Update this driver from the Realtek website.

Reboot and run your system. If you get another BSOD, please upload it and we will take the next step. I hope these two drivers will solve your problem. Let us know how your system is doing.

Ubetjent · 04 Aug 2010

I've finished uninstalling the sptd.sys file.
Now, I'm sure the realtek drivers aren't the issue. I got BSOD's before I installed those drivers which I did yesterday. I used a programme that aparrantly found and installed the newest drivers availible and installed them.
I'm trying to get another BSOD now by installing starcraft 2. (Last BSOD happened during the installation).

CarlTR6 · 04 Aug 2010

Yes, your latest dump file shows that the Realtek driver is updated:

Rt86win7.sys Wed Jun 23 05:10:23 2010

Good work on that and uninstalling SPTD. Let's see what happens.

Ubetjent · 04 Aug 2010

Okay, I managed to install Starcraft without BSOD after deleting sptd.sys.
Then the game wouldn't launch. For some reason the screen just went black and the game crashed and asked me to send an error report. I've also noticed that films (even in 720p) have a very bad quality and lags.
i find this wierd, seeing I've got all the right drivers installed plus I'm running ATI Radeon HD 3870 Crossfire!

Then I got another BSOD after trying to set a new resolution for my monitor..

My stationary pc can't load windows for some reason either after BSOD.. I have to wait a while before it can actually load it, or it will just keep rebooting when it gets to the windows loading screen or just after I type in the password to enter windows..

I'll post log once I manage to enter windows.

Ubetjent · 04 Aug 2010

Okay, pc up and running now. Here's the report from the scan I just performed.

CarlTR6 · 04 Aug 2010

What third party firewall and antivirus programs are you running?

My mistake; there was not a new dump in your latest upload. Please enable Driver Verifier. Follow these instructions carefully. Driver Verifier will cause BSOD's; that is what it is supposed to do. Upload any BSOD's.

Driver Verifier - Enable and Disable

Using Driver Verifier to identify issues with Drivers

Ubetjent · 05 Aug 2010

Good morning. My system has been running all night with Driver Verifier active over night now. This is longer than it ever has without getting BSOD.
Also. I can't get an internet connection on my pc now. Cannot obtain default gateway. As a result, I can't use my pc as I usualy do when I get BSOD's.
Any ideas?