Solved Various BSODs are back, not consistent, seems random

[lian9]

Ok I'll let you know how it went in ~36hrs. Thanks for your help so far

 

[lian9]

Alright, I haven't gotten any BSODs whatsoever from driver verifier.

 

[koolkat77]

Thanks for the update
Wait for some more hours before our next step

 

[lian9]

And for a second I thought they had randomly gone away for good. There was another BSOD, this time when I was just browsing the internet. I didn't really get to see anything in time but there was a memory dump, I think, in case me telling you that even matters. I attached the zip.

 

[koolkat77]

Please update the drivers to your manufactures networking card.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1048, 2, 0, fffff88001a79027}

Probably caused by : tcpip.sys ( tcpip!UdpBeginDelivery+7 )

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330c100
 0000000000001048 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!UdpBeginDelivery+7
fffff880`01a79027 488b4248        mov     rax,qword ptr [rdx+48h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff88003bbc7c0 -- (.trap 0xfffff88003bbc7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800b06c080 rbx=0000000000000000 rcx=fffffa8006e03820
rdx=0000000000001000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001a79027 rsp=fffff88003bbc950 rbp=fffffa8006e03820
 r8=0000000000000000  r9=0000000000000000 r10=fffff880009ecb20
r11=fffff88003bbc9c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
tcpip!UdpBeginDelivery+0x7:
fffff880`01a79027 488b4248        mov     rax,qword ptr [rdx+48h] ds:0092:00000000`00001048=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030dc769 to fffff800030dd1c0

STACK_TEXT:  
fffff880`03bbc678 fffff800`030dc769 : 00000000`0000000a 00000000`00001048 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03bbc680 fffff800`030db3e0 : fffffa80`0b06c0a8 fffff880`01a44a18 fffffa80`00000000 fffffa80`0b677ec0 : nt!KiBugCheckDispatch+0x69
fffff880`03bbc7c0 fffff880`01a79027 : fffffa80`0acd9a10 00000000`00000040 fffffa80`0acd99e0 00000000`000007ff : nt!KiPageFault+0x260
fffff880`03bbc950 fffff880`01a7f8ce : fffffa80`0b677ec0 fffffa80`0b030280 fffffa80`06e03820 fffffa80`0b677ec0 : tcpip!UdpBeginDelivery+0x7
fffff880`03bbc9d0 fffff880`01a793ed : fffffa80`00000028 fffffa80`0b677ec0 fffffa80`00000000 fffffa80`06a50cc8 : tcpip!UdpDeliverDatagrams+0x20e
fffff880`03bbcb60 fffff880`01a57c37 : fffffa80`06df9ea0 fffffa80`0b030280 00000000`00000017 00000000`00000000 : tcpip!UdpReceiveDatagrams+0x1ed
fffff880`03bbcc70 fffff880`01a5774a : 00000000`00000000 fffff880`01b69800 fffff880`03bbce30 fffffa80`06e03820 : tcpip!IppDeliverListToProtocol+0xf7
fffff880`03bbcd30 fffff880`01a56d49 : 00000000`00000000 fffffa80`0b106100 00000000`00000000 fffff880`03bbce20 : tcpip!IppProcessDeliverList+0x5a
fffff880`03bbcdd0 fffff880`01a3b5df : fffffa80`0b1061c0 fffffa80`00000001 00000000`00000000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`03bbceb0 fffff800`030d4cb7 : fffff880`01b69800 00000000`00000011 00000000`00000000 00000000`00000000 : tcpip!IppLoopbackTransmit+0x38f
fffff880`03bbcf60 fffff800`030d4c78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`0c2550a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!UdpBeginDelivery+7
fffff880`01a79027 488b4248        mov     rax,qword ptr [rdx+48h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!UdpBeginDelivery+7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5034f727

FAILURE_BUCKET_ID:  X64_0xD1_tcpip!UdpBeginDelivery+7

BUCKET_ID:  X64_0xD1_tcpip!UdpBeginDelivery+7

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

 

[lian9]

You mean this driver? I'm not sure this is the right driver because in device manager it shows driver version as 1005.22.615.2011, which is dated 6/15/2011 and windows update says it's already up to date. Am I looking at the right one?
ASUS - Networks- ASUS PCE-N15
For win7 64 bit, it shows under the wireless tab that the latest driver is 1.0.0.8

 

[koolkat77]

Can you upload your msinfo file again

To get this:

• Click on the Start rb:
• Type msinfo32 into the Search programs and files box
• When it opens, go to File, Save
• Save as msinfo32.nfo and save in a place you will remember
• Let it finish the process of gathering and saving the system info
• Right click the .nfo file, click send to compressed (zipped) folder
• Upload the .zip file here.

 

[lian9]

Here you go.

 

[lian9]

Had two more bsods since the last post. Since these have been happening since the day I made the computer and driver verifier found nothing I guess it's hardware but I have no idea what could be screwing up.

 

[koolkat77]

iusb3xhc.sys

What's connected to your USB ports?

 

[lian9]

I have a usb extender which has the usb plug for the wireless mouse and keyboard, that's it.

 

[koolkat77]

Hmm okay.
Did you enable verifier at all?

 

[lian9]

Yeah I ran it for 36 hours but never got a blue screen during that time.

 

[koolkat77]

Well I hope you already know the purpose of Driver verifier? If there are no BSODs when verifier is enabled, the problem lies within hardware.

I've seen your older threads and assume your computer is still under its warranty.

Anyway, do you prefer doing a clean install on your computer?

 

[lian9]

Yeah, I figured that when verifier didn't lead anywhere that the problem was in hardware. When I replaced the motherboard I ended up doing a clean install and the problem remained, so unless I need another motherboard I'm not too confident a clean install will solve anything.

One thing I've been thinking of doing is replacing the graphics card, because when I'm playing games, they will occasionally freeze and then I will get a message along the lines of "AMD driver has stopped responding and recovered" and sometimes the computer will say something like "your computer is running slower than it should, disable windows aero color scheme?" and in the reviews of this graphics card none of these issues were ever mentioned. Seeing as how I have the latest graphics card drivers, I'm thinking maybe my card is a bit faulty.

However, the BSODs that you've looked over and the same the other guys saw in the previous thread saw didn't lead anyone to point at the graphics card as the issue. I'm just not sure how to narrow down hardware problems. I would like to think I'm not so unlucky that that I got two motherboard duds

 

[koolkat77]

It's okay, don't be sad as long as you're computer is under it's warranty.

Go through this thread, see how the OP found out where his/her problem was.
→ http://www.sevenforums.com/crashes-debugging/250949-problem-irql_not_less_or_equal.html

Btw, does your mobo have an on-board VGA slot? If yes, how does your computer act when connected there?

You may take the following video card stress test

Video Card - Stress Test with Furmark
→ http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Monitor your temps with Speccy during the test
→ Speccy - System Information - Free Download

 

[lian9]

I did the graphics stress test and after about maybe 7 minutes the computer froze and I got the message "AMD driver has stopped responding and has recovered" and the test wouldn't resume. The temperatures seemed to be leveling out at 74C.

However, I suppose if the motherboard is faulty, it could be affecting the graphics card. I looked at that thread and I see I'm not the only unlucky one.

The motherboard does have a vga slot, and if I recall, using the vga slot means the graphics card needs to be disabled and the intel graphics will be used. I've got to go to bed now so I can address that tomorrow. Thanks for your help so far. It looks like the problems may remain with the motherboard...again, the most pain in the *** part of the computer to replace.

 

[koolkat77]

Okay no problem, get some sleep now.

And yes when you're up next we'll try your VGA slot.
The options for that can be changed from your BIOS.

See you soon

 

[lian9]

Using the vga slot without the graphics card didn't stop the blue screen. This time the bsod occured when I was playing an online game, and I was getting unusually large and long lag spikes, although that might be unrelated.

 

[koolkat77]

Just blaming the direct x files this time.
Now I'm sure this is a defective motherboard issue.

Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880031de270, fffff88005be0528, fffff88005bdfd80}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::EndPreparation+48 )

I'd suggest you to RMA, as these tests and tweaks that we're doing might void the warranty.

Let us know your decision.