BSOD Errors

Good Afternoon All!

I had some parts fail on me and did an RMA on my motherboard and CPU. I also replaced my RAM (I think my ram was the true culprit but I received new MB and CPU anyhow).

Ever since I have been unable to play any games with a BSOD. I can go anywhere from 30 mins to 3-4 days without a BSOD. I've attached my dump files. I've had multiple error codes pop up. Could it be I have faulty ram? I did run memtest and it found tons of errors on the core 4 processor stage of the test so maybe core 4 could be corrupt? Not sure exactly what all it was testing...

Before I did my RMA I never had a BSOD...I didn't reinstall windows 7 x64 (I'm installing SP1 as I'm typing this) when I rebuilt my computer as it was the same MB and cpu just different RAM. I did update my MB to the newest BIOS and my video driver is the most current.

I've attached some of my dump files from the past 2 weeks....hopefully some geniuses out there might be able to help me out...I'm at a loss on this one.

I appreciate any help!!

Jared

Hello and welcome to the forum.
Start by getting rid of this
sptd.sys 8/24/2010
Normally associated with Daemon Tools (but may be Alcohol or something else) go here DuplexSecure - Downloads, get the correct version for your architecture and run it and click UNINSTALL

Code:

BugCheck BE, {fffff880010910b0, 8000000003caa121, fffff8800ac89270, a}
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!AtapiSetupPrdTable+2b )
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly 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: fffff880010910b0, Virtual address for the attempted write.
Arg2: 8000000003caa121, PTE contents.
Arg3: fffff8800ac89270, (reserved)
Arg4: 000000000000000a, (reserved)
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  Diablo III.exe
CURRENT_IRQL:  7
TRAP_FRAME:  fffff8800ac89270 -- (.trap 0xfffff8800ac89270)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800ac89450 rbx=0000000000000000 rcx=fffffa800d6da6a8
rdx=fffffa800e626978 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001090bde rsp=fffff8800ac89408 rbp=000000000000000e
 r8=000000000000000a  r9=fffffa800d6da6a8 r10=3ee3dab0a4950000
r11=fffff8800ac89450 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
atapi!AtaPortGetScatterGatherList:
fffff880`01090bde ff25cc040000    jmp     qword ptr [atapi!_imp_AtaPortGetScatterGatherList (fffff880`010910b0)] ds:ff00:fffff880`010910b0={ataport!AtaPortGetScatterGatherList (fffff880`0109bf24)}
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80003153718 to fffff800030d5f00
STACK_TEXT:  
fffff880`0ac89108 fffff800`03153718 : 00000000`000000be fffff880`010910b0 80000000`03caa121 fffff880`0ac89270 : nt!KeBugCheckEx
fffff880`0ac89110 fffff800`030d3fee : 00000000`c7287000 fffffa80`0e626978 000020d0`b51d0028 00000000`00000010 : nt! ?? ::FNODOBFM::`string'+0x40a84
fffff880`0ac89270 fffff880`01090bde : fffff880`0108f60b 00000000`000001f6 fffffa80`0e626901 00000000`0000000e : nt!KiPageFault+0x16e
fffff880`0ac89408 fffff880`0108f60b : 00000000`000001f6 fffffa80`0e626901 00000000`0000000e fffff880`0108f5c9 : atapi!AtaPortGetScatterGatherList
fffff880`0ac89410 fffff880`0108f137 : fffffa80`0e626978 00000000`0000000e fffffa80`0e6269c0 fffffa80`0d6da6a8 : atapi!AtapiSetupPrdTable+0x2b
fffff880`0ac89460 fffff880`0108eee1 : fffffa80`0d450a50 fffffa80`0e626978 00000000`0000000e fffffa80`0cbd9000 : atapi!AtapiSendAtaCommand+0x11b
fffff880`0ac894d0 fffff880`0108e656 : fffffa80`0e626978 fffffa80`0da7b950 fffff880`0ac89750 00000004`000002d4 : atapi!AtapiHandleAtaCommand+0x45
fffff880`0ac89500 fffff880`00e7e296 : 00000000`0000003c 00000000`00000000 00000000`00000000 00000000`00000000 : atapi!AtapiHwStartIo+0x66
fffff880`0ac89530 00000000`0000003c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : sptd+0x46296
fffff880`0ac89538 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3c
STACK_COMMAND:  kb
FOLLOWUP_IP: 
atapi!AtapiSetupPrdTable+2b
fffff880`0108f60b 488bf0          mov     rsi,rax
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  atapi!AtapiSetupPrdTable+2b
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atapi
IMAGE_NAME:  atapi.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc113
FAILURE_BUCKET_ID:  X64_0xBE_atapi!AtapiSetupPrdTable+2b
BUCKET_ID:  X64_0xBE_atapi!AtapiSetupPrdTable+2b

One other suspicious driver
ahur1i04.SYS 7/17/2010
I say suspicious, because neither Google or Bing produces any information. So it may be worth doing a little investigating to see if you can determine what it is, what it is for and why it is loading. If not sure you may want to consider renaming it by changing the extension from ahur1i04.SYS to ahur1i04.OLD .... up to you.
If Blue Screens persist then:
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Then:
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area Help Us To Help You By Filling In Your System Specs. .
And perhaps consider updating to Service Pack 1 for Windows 7

UPDATE READINESS TOOL.
Download and install the correct system readiness tool prior to installing SP1.
System Update Readiness Tool for 32bit (x86)
System Update Readiness Tool for 64bit (x64)

Good luck
Randy

Thanks for the info Randy! I'll look into those and make the changes you suggested.

I've messed around with some things and I haven't had a BSOD since----6 hours and counting----not sure if I'm lucky or I fixed the problem. What I've done so far:

Reseated my ram--I tried different spots but still had BSOD even quicker than before so I put it back to the 3 and 4 spots and made sure it was nice and snug.
Updated Alcohol 120% prior to reading this post---you recommend I remove this-----
I was going to reinstall windows 7 but I did a repair for shits and giggles----maybe that helped? I havene't reinstalled yet.

I'll keep you all posted in case anyone else has something similar.

Thanks!

Jared