Windows 7 Need help->>>

[CryoN86]

I have been getting a BSOD lately, help!

View attachment Seven Forums.zip

 

[Trouble]

Hello and welcome to the forum
Let's start by taking the debugger at face value and address this issue:
DUMP:

BugCheck A, {fffff6fb401d8010, 2, 0, fffff80002cbc301}
Unable to load image \SystemRoot\system32\DRIVERS\[U][B][COLOR=#ff0000]netr28ux.sys[/COLOR][/B][/U], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [B][U][COLOR=#ff0000]netr28ux.sys[/COLOR][/U][/B]
*** ERROR: Module load completed but symbols could not be loaded for netr28ux.sys
[COLOR=#ff0000][U][B]Probably caused by[/B][/U][/COLOR] : [B][U][COLOR=#ff0000]netr28ux.sys[/COLOR][/U][/B] ( [B][U][COLOR=#ff0000]netr28ux[/COLOR][/U][/B]+b214 )
Followup: MachineOwner
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff6fb401d8010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002cbc301, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eff100
 fffff6fb401d8010 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!MmBuildMdlForNonPagedPool+81
fffff800`02cbc301 488b4500        mov     rax,qword ptr [rbp]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
TRAP_FRAME:  fffff80004310e10 -- (.trap 0xfffff80004310e10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000b1 rbx=0000000000000000 rcx=0000000000000000
rdx=00000000000010b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cbc301 rsp=fffff80004310fa8 rbp=fffff6fb401d8010
 r8=0000000000000000  r9=000000003b002d50 r10=fffffa80071fcf40
r11=005a0076005aa000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MmBuildMdlForNonPagedPool+0x81:
fffff800`02cbc301 488b4500        mov     rax,qword ptr [rbp] ss:0018:fffff6fb`401d8010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ccc1e9 to fffff80002cccc40
STACK_TEXT:  
fffff800`04310cc8 fffff800`02ccc1e9 : 00000000`0000000a fffff6fb`401d8010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`04310cd0 fffff800`02ccae60 : fffffa80`00000000 00000000`00000000 fffffa80`07b2f010 fffffa80`071fcf70 : nt!KiBugCheckDispatch+0x69
fffff800`04310e10 fffff800`02cbc301 : fffffa80`06df3c60 00000000`00000000 fffff880`084ca214 00000000`00000000 : nt!KiPageFault+0x260
fffff800`04310fa8 fffff880`084ca214 : 00000000`00000000 fffff800`04311b18 fffffa80`07229800 fffffa80`06dbc1a0 : nt!MmBuildMdlForNonPagedPool+0x81
fffff800`04310fc0 00000000`00000000 : fffff800`04311b18 fffffa80`07229800 fffffa80`06dbc1a0 fffff880`00000002 : [U][B][COLOR=#ff0000]netr28ux[/COLOR][/B][/U]+0xb214
STACK_COMMAND:  kb
FOLLOWUP_IP: 
  [U][COLOR=#ff0000][B] netr28ux [/B][/COLOR][/U]  +b214
fffff880`084ca214 ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:     [COLOR=#ff0000][U][B]netr28ux[/B][/U][/COLOR]   +b214
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME:    [COLOR=#ff0000][U][B]netr28ux[/B][/U][/COLOR] 
IMAGE_NAME:   [COLOR=#ff0000][U][B]netr28ux  .sys[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4aaf19dd
FAILURE_BUCKET_ID:  X64_0xA_[COLOR=#ff0000][B]netr28ux[/B][/COLOR]+b214
BUCKET_ID:  X64_0xA_[COLOR=#ff0000][B]netr28ux[/B][/COLOR]+b214
Followup: MachineOwner

So update this driver
netr28ux.sys 9/14/2009 Ralink RT2870 series USB802.11n Wireless Adapter Driver or at least with that chipset. From here Ralink-A MEDIATEK COMPANY
Regards
Randy

 

[CryoN86]

I think my problem has been fixed, thank you!

 

[Elmer]

I think my problem has been fixed, thank you!

Cool! Give it a week or so, then you'll know for sure. Keep us updated!