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: Sudden memorydumps and Bluescreens

05 Aug 2010   #11
Tews

64-bit Windows 8.1 Pro
 
 

Do a quick system restore and see if you are able to connect...


My System SpecsSystem Spec
.
05 Aug 2010   #12
Ubetjent

Windows 7 (x86)
 
 

Got a BSOD now.
I had to start windows in safe mode to be able to turn off the verifier and get into windows.
After that I ran a perfmon /report which I have attatched to this reply.
My System SpecsSystem Spec
05 Aug 2010   #13
Ubetjent

Windows 7 (x86)
 
 

Seems I didn't see that you asked me what third party firewall and anti virus I'm running. Sorry for that.

I'm running normal windows firewall if i'm not mistaken. I'm not sure what is meant by third party firewall.

Antivirus = Avast
My System SpecsSystem Spec
.

05 Aug 2010   #14
CarlTR6

Windows 7 Ultimate 32 bit
 
 

That was the info I was looking for. You are not running a third party (non-Microsoft) firewall. These sometimes cause connection problems which is why I asked (from experience). Avast should be OK.

I didn't see the BSOD. I will take a look at it.
My System SpecsSystem Spec
05 Aug 2010   #15
CarlTR6

Windows 7 Ultimate 32 bit
 
 

I have only looked at two BSOD's. I will look at the rest and I will edit this post to add the information. You may have to refresh the page to see the info.

Your second BSOD pointed to sptd.sys as a possible cause. Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use the driver, sptd.sys, which is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Don't reinstall sptd; just uninstall it.

All of your dumps are caused by hardware or hardware related problems. Notice that device driver is mentioned in all three error codes.

Quote:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

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 0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

Usual causes: Device driver
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\Temp2_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\Temp2_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\Temp2_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
---------
Your drivers appear up to date. Remove sptd and see how your system runs. If you get another BSOD, upload it and enable Driver Verifier. Driver Verifier will cause BSOD's when it encounters a faulty driver.

Driver Verifier - Enable and Disable
My System SpecsSystem Spec
05 Aug 2010   #16
Ubetjent

Windows 7 (x86)
 
 

Alright. Sorry about the sptd.sys problem I read on a forum that it wouldn't install it, but guess i was wrong. Hehe. I appreciate the help alot mate.
I'll uninstall it right away and then wait and see.
My System SpecsSystem Spec
05 Aug 2010   #17
CarlTR6

Windows 7 Ultimate 32 bit
 
 

You are welcome. No problem. That actually is an updated sptd driver version. I would not have suggested uninstalling it except one of the dumps directly pointed to it. The older sptd drivers definitely cause BSOD's. I was hoping the newer driver would be good. Keep us updated.
My System SpecsSystem Spec
Reply

 Sudden memorydumps and Bluescreens




Thread Tools




Similar help and support threads
Thread Forum
I keep getting bluescreens from BC2
Hello everyone. I'm new here and for the past month I have been getting bluescreens on BFBC2 while playing online. I also crash now and then. I uploaded the dump so please view that and tell me why this is happening. Thank you.
BSOD Help and Support
Some bluescreens
Hello! I had fully working computer till I changed my motherboard. Before my setting was: MB: Asus P5B CPU: QuadCore Intel Core 2 Quad Q9450, 2666 MHz (8 x 333) RAM: 4GB G-Skill DDR2-800 DDR2 SDRAM (5-5-5-15 @ 400 MHz) (4-4-4-10 @ 266 MHz) GPU: Ati Radeon HD6850
BSOD Help and Support
Computer random crashes/bluescreen/memorydumps
I'm having random computer crashes and want to find out why I've attached my memory dump files and the SF diagnostic files
BSOD Help and Support
A lot of Bluescreens
Hello everyone here at SevenForums! I've as of lately have had alot of problems with my computer.(I built it myself this February) My computer crashes(Bluescreen) when I play games such as Battlefield: Bad Company 2 and World in Conflict and I'm getting error messages when I try to update...
BSOD Help and Support
Bluescreens all over
hello guys, i have been having quite alot problems with bluescreens and freezes lately. my friends suggested to me i should buy a new videocard as it seemed to be the problem, so i replaced my radeon 5770 with a radeon 6970. to prevent conflicts in drivers i reinstalled windows too. but the...
BSOD Help and Support
Bluescreens on my new PC
Hi, I have had several bluescreens since I got my new PC a few days ago. Now I saved the *.dmp for you. Would you please give a statement? Windows 7 Upgrade Advisor gave no hints. Sometimes the Bluescreens appear while beeing on the desctop but also while playing games. The PC is a...
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 13:44.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App