Solved BSODs: 0x09F and 0x0E6. Rtnicprop64.dll also seems to be unsigned.

[shadedgrey63]

The 0x09F BSODs seem to occur going into standby, as I'm usually away from the computer when they occur. As for the 0x0E6 BSODs, they seems like they might be happening when I'm installing something or dowloading larger files. I recently ran Driver Verification and rtnicprop64.dll came up unsigned; two files were not scanned as well.

While trying to attach the .zip right now, I had another 0x0E6 BSOD. I hope it works this time. :huh: Yay, it worked!

 

[Skylais]

The 0x09F BSODs seem to occur going into standby, as I'm usually away from the computer when they occur. As for the 0x0E6 BSODs, they seems like they might be happening when I'm installing something or dowloading larger files. I recently ran Driver Verification and rtnicprop64.dll came up unsigned; two files were not scanned as well.

While trying to attach the .zip right now, I had another 0x0E6 BSOD. I hope it works this time. :huh: Yay, it worked!

Are you sure the attached file was uploaded? try again.

 

[shadedgrey63]

There you go. I did edit this post a couple times - would that have had removed the attachment?

 

[Skylais]

aha got it
netr28x.sys:
Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer)
go to device manager and find the wireless card, give me the name of it or a screenshot like mine here:

 

[Skylais]

This is our bad driver on your pc, making them BSODs occur.
1. Right click the driver called Name 802.11n Wireless LAN Card in
"device manager" >"Properties">Roll back. If there is no roll back option. Right click the driver and uninstall, then to install again proceed with this : http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html.
Please provide feedback with how this goes.

 

[shadedgrey63]

Okay, here's a screenshot because I'm not sure exactly which network adapter is problematic.

 

[Skylais]

Okay, here's a screenshot because I'm not sure exactly which network adapter is problematic.

The 1st one please follow the previous instructions
:
1. Right click the driver called Name 802.11n Wireless LAN Card in
"device manager" >"Properties">Roll back. If there is no roll back option. Right click the driver and uninstall, then to install again proceed with this : http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html.
Please provide feedback with how this goes.
Thanks for your cooperation!

 

[shadedgrey63]

Okay, right after clicking on Roll-Back Driver, I had yet another e6 BSOD. But I'm looking in the properties now and the driver date is different than from before the BSOD anyway (nor can it be rolled back any more).

 

[Skylais]

Okay, right after clicking on Roll-Back Driver, I had yet another e6 BSOD. But I'm looking in the properties now and the driver date is different than from before the BSOD anyway (nor can it be rolled back any more).

Ok lets see how this plays out. How often do the BSOD occur? See if it runs fine, for now. Please upload that last BSOD mindiump. It can be found in C:\Windows\Minidump
Sort by date modified and give me the latest one please

 

[shadedgrey63]

I couldn't zip it because access was denied.

 

[shadedgrey63]

Nevermind, here it is. I just had to copy it to my desktop first. My BSODs occur anything from daily to maybe every few days, I think.

 

[Skylais]

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


Loading Dump File [C:\Users\Skyler\AppData\Local\Temp\Rar$DIa0.007\091012-50887-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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 Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0320b000 PsLoadedModuleList = 0xfffff800`0344f670
Debug session time: Mon Sep 10 00:17:54.745 2012 (UTC - 5:00)
System Uptime: 0 days 0:58:23.806
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E6, {9, fffffa800b6fdc80, 1, fffffa800b720e70}

*** WARNING: Unable to verify timestamp for [COLOR="red"]netr28x.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by : [COLOR="red"]netr28x.sys[/COLOR] ( netr28x+8592 )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000000000009, Cannot put adapter until all map registers are freed.
Arg2: fffffa800b6fdc80, Pointer to the DMA adapter.
Arg3: 0000000000000001, Number of outstanding map registers.
Arg4: fffffa800b720e70, Pointer to the corresponding internal verifier data.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xE6

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800037103dc to fffff8000328a1c0

STACK_TEXT:  
fffff880`0375aff8 fffff800`037103dc : 00000000`000000e6 00000000`00000009 fffffa80`0b6fdc80 00000000`00000001 : nt!KeBugCheckEx
fffff880`0375b000 fffff800`0371a6a2 : fffff800`0370e850 00000000`00000004 00000000`00000065 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0375b040 fffff800`03722929 : fffffa80`0b720e70 fffff880`01901100 00000000`00000000 00000000`00000001 : nt!ViHalReportIssueWithOptions+0x1a2
fffff880`0375b090 fffff880`018d9806 : fffff980`0673cf60 fffff980`0673cf60 00000000`00000000 fffff880`01901110 : nt!VfPutDmaAdapter+0x1d9
fffff880`0375b0f0 fffff880`0191e055 : 00000000`00000010 fffffa80`0b5241a0 00000000`00000000 fffff880`01901110 : ndis!ndisDereferenceDmaAdapter+0x66
fffff880`0375b120 fffff880`0540f592 : fffffa80`0bc242b8 00000000`00000000 fffffa80`0bc24250 fffffa80`0bc00000 : ndis!NdisMDeregisterScatterGatherDma+0x55
fffff880`0375b150 fffffa80`0bc242b8 : 00000000`00000000 fffffa80`0bc24250 fffffa80`0bc00000 00000000`d0d03000 : netr28x+0x8592
fffff880`0375b158 00000000`00000000 : fffffa80`0bc24250 fffffa80`0bc00000 00000000`d0d03000 fffff880`018cc92d : 0xfffffa80`0bc242b8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
netr28x+8592
fffff880`0540f592 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  netr28x+8592

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netr28x

IMAGE_NAME:  [COLOR="Red"]netr28x.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4f54b390

FAILURE_BUCKET_ID:  X64_0xE6_netr28x+8592

BUCKET_ID:  X64_0xE6_netr28x+8592

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

The netr28x.sys is our issue, lets see how it runs on the older drivers, if we get another BSOD then we will remove and clean, then somehow find the most up to date version for your computer we can. Is your pc custom built? if not then what make and model is it. thanks for being patientwhile you and i try to solve this.

 

[shadedgrey63]

Not exactly. It is a customizable model from HP which I then upgraded its graphics card, and power supply to handle it, not long after getting it. It's a Hewlett-Packard HPE-350t. No problem, I've been trying to fix these BSODs for months so I'm pretty used to having patience with this.

 

[Skylais]

Not exactly. It is a customizable model from HP which I then upgraded its graphics card, and power supply to handle it, not long after getting it. It's a Hewlett-Packard HPE-350t. No problem, I've been trying to fix these BSODs for months so I'm pretty used to having patience with this.

Ok thanks this helps,
Latest driver i can find for this is here : Ralink Wireless Network Controller Driver Update HP Pavilion Elite HPE-350t CTO Desktop PC - HP Customer Care (United States - English) version : 3.1.9.0

but we have under original driver this one : Original Ralink Wireless Networking Controller Driver HP Pavilion Elite HPE-350t CTO Desktop PC - HP Customer Care (United States - English) version : 3.0.14.0

Now what driver version is it currently on?

 

[shadedgrey63]

Neither - the current driver is from 11/14/2011.

 

[Skylais]

Neither - the current driver is from 11/14/2011.

Weird, does it have the driver version? you can check by right clicking the wireless card in device manager "properties" and then driver. You should see the driver version.

 

[shadedgrey63]

It says the version is 3.2.7.0

 

[Skylais]

Ok think we may have found our problem, i suspect the wrong driver was installed. Because for that computer you have, the latest version is here and it is version : 3.1.9.0 Not version 3.2.7.0 (the one you have now): Ralink Wireless Network Controller Driver Update HP Pavilion Elite HPE-350t CTO Desktop PC - HP Customer Care (United States - English) it is version : 3.1.9.0
So let's again uninstall that driver and then install the one in the link.
See how it runs, with this new driver.
This is that computer correct ?? (besides the PSU and Graphics card) : http://h10025.www1.hp.com/ewfrf/wc/...link=ot_we/prodlink/en_us/4242295/loc:0&cc=us

 

[shadedgrey63]

Yes, it is. Problem is, I had another e6 BSOD when I started to uninstall 3.2.7.0 via Device Manager. I checked after restarting; it's still that driver.

 

[Skylais]

Yes, it is. Problem is, I had another e6 BSOD when I started to uninstall 3.2.7.0 via Device Manager. I checked after restarting; it's still that driver.

Hmm can you uninstall it while stable enough in safe mode?