BSOD Error STOP: 0x02B46B13

okay..if you get more bsod,upload the new logs

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\acgref3\SF_03-10-2013\100313-18314-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c5a6d0
Debug session time: Fri Oct  4 04:07:21.859 2013 (UTC + 6:00)
System Uptime: 0 days 0:06:05.796
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 6f8, fffff8800110fc0a}

Probably caused by : ataport.SYS ( ataport!IdeStartIoCallBack+2e )

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

0: 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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff8800110fc0a

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Azureus.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002a8c129 to fffff80002a8cb80

STACK_TEXT:  
fffff800`00ba4d28 fffff800`02a8c129 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02a8a5f2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`0110fc0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`0872c1b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ataport!IdeStartIoCallBack+0x2e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdeStartIoCallBack+2e
fffff880`0110fc0a 498b742458      mov     rsi,qword ptr [r12+58h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ataport!IdeStartIoCallBack+2e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  51fef9b5

FAILURE_BUCKET_ID:  X64_0x7f_8_ataport!IdeStartIoCallBack+2e

BUCKET_ID:  X64_0x7f_8_ataport!IdeStartIoCallBack+2e

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

Make scans with these tools -

• TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
• Online Virus Scanner Eset

------------------------
Upload a screenshot using:

• CrystalDiskInfo For how to upload a screenshot or file, read here

Test your Hard Drive(s) by running:

• Hard Drive Diagnostic Procedure

------------------------
Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to Part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

------------------------
Monitor hardware temperature with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:

• Piriform - Speccy
• CPUID - HWMonitor
• For how to upload a screenshot or file, read here

Ok, we may be onto something. First off, I got two more blue screens over the last couple of days. I've attached a new dump file.

The TDSSKiller scanned and said no threats were found. The ESET online virus scanner said no threats were found. The hard drive diagnostic completed without error...the short and long tests both passed. I've uploaded screenshots of the Crystal Disk Info and Speccy.

The RAM test came back with an error after less than 10 minutes. This is what my screen showed:

Tst___Pass___Failing Address___________Good____Bad_____ErrBits_____Count___CPU
8_____0_____ 00060dbbf50-1549.6MB___7fffffff___ffffffff___80000000___1_______0

I don't know if this means anything specific. I haven't done the "if you have errors" part yet. I'll try to test all that over the next couple of days. A question about that though...if it turns out to be a bad slot, can I just not use a RAM stick in that slot or does it mean the motherboard needs to be replaced completely because of one bad slot?

One last question, is it safe to say that this IS the reason for my blue screen or could it still be something else?

acgref, Koolkat asked me to give my opinion on your problem. I am not a BSOD analysis, I'm not that smart. I'm pretty much a hardware guy. I have briefly skimmed the thread so if I say something that has already been covered, please excuse me. But, your ram test has to be resolved before anything else. To answer your question, it most likely is the problem that has been causing you the problems. No one can tell you it is a 100% guarantee, there is always the possibility that you have more than 1 problem, but pretty unlikely. If your computer is still under warranty, Dell can replace the Ram for you. otherwise I would recommend the Crucial Memory advisor. You can fill in your system specs or let it scan your hardware to make sure the ram you buy is compatable with your computer. Once you find out what you need, you can buy ram from whoever you like as long as the specs match what the Crucial advisor gives you. I would recommend buying from a major supplier like G Skill, Corsair or Crucial as they give a lifetime warranty on the ram they sell. If you have bad ram, buy a set of ram as it has been tested to work together. If your tests reveal you have a bad slot, then it means your motherboard is bad and needs repair or replacing. If you have any questions, feel free to ask.