BSOD at random, usually upon closing laptop

That's strange. I took a look at the driver again; it is indeed 5.0.9. It must have reverted after I used the HP Update tool. It's strange that I can't trust HP's own software to provide the right driver.

I've installed DriverMax and used it to find the latest version of the Ralink driver (as well as a bunch of other ones). According to DriverMax, the latest supported update is 5.0.5. This is different than the version you suggested, but this seems to have stopped the bluescreens from occurring again. Is it possible that the version you suggested (3.2.2.0) was just what came with the computer? All of the drivers in your link are from 2011.

I'm not sure why the more recent BSOD's don't come up in the file. Perhaps the computer didn't bluescreen those times but improperly shut down in some other way? In any case, I'll run the utility one more time and attach the results. Maybe that will do it

Here's the newest file

Attachment 274568

ikontool

Please stop using drivermax to update your drivers !!!! You are calling for more trouble than getting the latest

You may use it for backing up the drivers but never to update it. !!

There is a reason why each manufacturer has their own set of drivers.. they update them based on the feedback they get from customers and internal testing.. even if the version is dated in 2011 !!..

There are certain drivers like Graphics card that can be update from the respective chip manufacturer (Nvidia or ATI) even if they come from different partners.

If what i say is not enough.... look at the dump file date 30/6/2013.... look at the drivers marked in red

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800601d060, fffff80005045518, fffffa800867f9d0}

Probably caused by : pci.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800601d060, Physical Device Object of the stack
Arg3: fffff80005045518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800867f9d0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000ef3000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF8000504BFB0

STACK_TEXT:  
fffff800`050454c8 fffff800`031388c2 : 00000000`0000009f 00000000`00000003 fffffa80`0601d060 fffff800`05045518 : nt!KeBugCheckEx
fffff800`050454d0 fffff800`030d384c : fffff800`05045600 fffff800`05045600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`05045570 fffff800`030d36e6 : fffff800`03278f20 00000000`00670210 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`050455e0 fffff800`030d35ce : 000000f5`32f19c9b fffff800`05045c58 00000000`00670210 fffff800`03246488 : nt!KiProcessExpiredTimerList+0xc6
fffff800`05045c30 fffff800`030d33b7 : 00000023`da0929c1 00000023`00670210 00000023`da09293e 00000000`00000010 : nt!KiTimerExpiration+0x1be
fffff800`05045cd0 fffff800`030c090a : fffff800`03243e80 fffff800`03251cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`05045d80 00000000`00000000 : fffff800`05046000 fffff800`05040000 fffff800`05045d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_netr28x_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_netr28x_IMAGE_pci.sys

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

0: kd> !irp fffffa800867f9d0
Irp is active with 5 stacks 3 is current (= 0xfffffa800867fb30)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0  0 fffffa8007131050 00000000 00000000-00000000    
	      Unable to load image \SystemRoot\system32\DRIVERS\netr28x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
 \Driver\netr28x
			Args: 00014400 00000000 00000004 00000002
 [ 16, 2]   0 e1 fffffa8007118a10 00000000 fffff80003315200-fffffa800b01b650 Success Error Cancel pending
	       \Driver\vwifibus	nt!PopSystemIrpCompletion
			Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800b01b650    

			Args: 00000000 00000000 00000000 00000000

Got it. I'll uninstall drivermax. Will installing the Ralink driver version 3.2.2.0 solve this once and for all then? Was this what caused all of the BSOD's?

Update:

I'm still getting the BSOD. I've confirmed that my Ralink driver is indeed version 3.2.2.0.

This time, from what I can gather, using windows debugger, the crash points to a file called "RT2860." The only information I can find on this is that it refers to a wireless adaptor by Ralink... that I don't have. Is this anything close to right? What should I do about it?

I've attached the latest SF log:
Attachment 274615

Upon further snooping in the device manager, it seems that RT2860.sys is the location of the 3.2.2.0 version driver for the Ralink adapter. Does this mean that my newly-installed driver doesn't work either?

The RT2860 is your Ralink Wifi driver.... Its correct.

All right next in line is the Firewall.. Please uninstall Kaspersky Internet Security 2013 and use MSE and the windows firewall for most of your needs. The NDIS drivers of these are known to cause issue

Then uninstall Demon tool Pro..

Restart your system and let me know when it crashes

Alright, I'll get on that. I'll mark this as solved for now and create a new thread if more problems arise