BSOD Error STOP: 0x02B46B13

[acgref]

Two days ago, my computer randomly restarted for no apparent reason. Upon restart, it went into a System Repair and I picked the option for it to try and find the problem. It came back after 10 minutes saying it could not find a problem. I shut down and restarted and it started fine and everything seemed to be ok. The next morning, I started my computer and after a few minutes, I got the BSOD. I shut down and started up again and it seemed fine. Now I'm 2 days after the random restart and I got the BSOD again. I wrote down the technical information:

****STOP: 0x02B46B13 (0XFFFFFA800887A8A8, 0XFFFFFA800ACD61C0, 0X0000000000000009, 0X0000000000000000

I tried searching online for that code and came up empty. I should mention that I haven't downloaded or installed anything recently or clicked on any random links at all. My virus scan shows nothing. When these BSODs happened, I wasn't really doing anything. I had opened my email and walked away from my computer and when I came back a minute later, the BSOD was there. It was a similar thing the second time.

I'm attaching a Dump File like the instructions say. I don't know what it is...just followed the instructions so I hope I did it right. Any help would be appreciated.

Thanks!

 

[koolkat77]

[FONT="Lucida Console"]Host Name:                 AMBER-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Amber
Registered Organization:   
Product ID:                00426-OEM-8992662-00400
Original Install Date:     2/1/2013, 1:02:15 PM
System Boot Time:          8/28/2013, 5:11:11 PM
System Manufacturer:       DELL Inc.
System Model:              Studio XPS 435T/9000
System Type:               x64-based PC[/FONT]

Where did you acquire your copy of Windows from?

 

[acgref]

It came with my computer when I bought it. I don't know if this matters, but in January, my hard drive failed and I had to replace it. After I installed the new one, I used the Dell Reinstallation DVD that also came with the computer to reinstall Windows.

 

[koolkat77]

Never mind. Looks fine, thanks

There seems to be no new dump.

First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.

• Create a Dump File when you get a BSOD

Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.

Perform these steps after that.
------------------------
Reduce the start-up items, Antivirus software is basically whats required.

• Remove Startup Programs in Windows 7
• Clean Startup in Windows 7

------------------------
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow - read here

Run Disk Check on your Hard Drive for file system errors and bad sectors on it - read here
------------------------
Try updating your WUBS300N.sys Linksys Wireless-N USB Network Adapter WUSB300N to its latest driver version.

• Driver Reference Table - WUBS300N.sys

Let us know the results.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, fffff880024e3cc0}

*** WARNING: Unable to verify timestamp for WUBS300N.sys
*** ERROR: Module load completed but symbols could not be loaded for WUBS300N.sys
Probably caused by : WUBS300N.sys ( WUBS300N+ccc0 )

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

2: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880024e3cc0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb8100
GetUlongFromAddress: unable to read from fffff80002cb81c0
 0000000000000008 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
WUBS300N+ccc0
fffff880`024e3cc0 4d8b742408      mov     r14,qword ptr [r12+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF88002F93FB0

TRAP_FRAME:  fffff88002f8c570 -- (.trap 0xfffff88002f8c570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800a4417b8
rdx=fffffa800a443702 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880024e3cc0 rsp=fffff88002f8c700 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=fffffa800a2e1200
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
WUBS300N+0xccc0:
fffff880`024e3cc0 4d8b742408      mov     r14,qword ptr [r12+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a801a9 to fffff80002a80c00

STACK_TEXT:  
fffff880`02f8c428 fffff800`02a801a9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f8c430 fffff800`02a7ee20 : fffffa80`09671050 fffffa80`0a16bc00 fffffa80`09671000 fffffa80`0a386000 : nt!KiBugCheckDispatch+0x69
fffff880`02f8c570 fffff880`024e3cc0 : 00000000`00000c27 fffff880`02c36aed fffffa80`0a443768 fffffa80`0a386000 : nt!KiPageFault+0x260
fffff880`02f8c700 00000000`00000c27 : fffff880`02c36aed fffffa80`0a443768 fffffa80`0a386000 ffff0000`00bb20a8 : WUBS300N+0xccc0
fffff880`02f8c708 fffff880`02c36aed : fffffa80`0a443768 fffffa80`0a386000 ffff0000`00bb20a8 00000000`00000000 : 0xc27
fffff880`02f8c710 00000000`00000c27 : 00000000`00000000 fffffa80`0a443768 00000000`00000001 00000000`00000000 : USBPORT!USBPORT_Core_iInsertPriorityTransfer+0x131
fffff880`02f8c750 00000000`00000000 : fffffa80`0a443768 00000000`00000001 00000000`00000000 fffffa80`0a386000 : 0xc27


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WUBS300N+ccc0
fffff880`024e3cc0 4d8b742408      mov     r14,qword ptr [r12+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  WUBS300N+ccc0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WUBS300N

IMAGE_NAME:  WUBS300N.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45fa10cd

FAILURE_BUCKET_ID:  X64_0xD1_WUBS300N+ccc0

BUCKET_ID:  X64_0xD1_WUBS300N+ccc0

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

2: kd> lmvm WUBS300N
start             end                 module name
fffff880`024d7000 fffff880`0252b480   WUBS300N T (no symbols)           
    Loaded symbol image file: WUBS300N.sys
    Image path: \SystemRoot\system32\DRIVERS\WUBS300N.sys
    Image name: WUBS300N.sys
    Timestamp:        Fri Mar 16 09:36:45 2007 (45FA10CD)
    CheckSum:         000617B1
    ImageSize:        00054480
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[acgref]

Ok, so my dump file setting was set to the "kernel" one so I've switched it to the Small Memory Dump. Just to be clear, I don't upload a new dump file now...only if I get another BSOD, correct?

C:\Windows\Minidump does exist

I ran the System File Checker and it came back with "Windows Resource Protection did not find any integrity violations."

I tried to run a Disk Check and it told me I couldn't do it while it was in use so I clicked to schedule it to run on my next startup. I restarted right away and nothing seemed to happen...unless it's something that's done behind the scenes? If not, how do I check to make sure it was alright. Or am I doing something wrong?

When trying to install the Drivers for my network adapter, it said I already had them.

Thanks for your help!

 

[acgref]

So it was more than two weeks without any problems, but today, my computer completely froze. I had to restart manually and started in safe mode. While I was in safe mode, I got a BSOD again. It restarted too quickly to read what it said. I've attached a new dump file.

 

[koolkat77]

Do you have anything connected to the USB ports?
Did you acquire any updates from windows updates recently?

 

[acgref]

I have my printer, my network adapter and my keyboard/mouse adapter connected by USB. Windows did an automatic update a few days before this last BSOD if I remember correctly.

 

[koolkat77]

Okay, did you have anymore BSODs?

 

[acgref]

No, my last BSOD was two days ago (post #6). The one before that was two and a half weeks before.

 

[koolkat77]

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

 

[acgref]

So two and a half weeks with no problems and I got another BSOD tonight. My computer was idle when it happened. I've attached the dump files.

 

[koolkat77]

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:tip: 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

• :info: Pay close attention to Part 3 of the tutorial "If you have errors"
• :tip: 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
• :info: For how to upload a screenshot or file, read here

 

[acgref]

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?

 

[essenbe]

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.