BSOD in NETIO.sys when running uTorrent

[eckert]

Windows 7 Ultimate . . .
- x64
- upgraded OS - Feb
- OEM
- Hardware ~1year
- Asus P8P67 Deluxe
- Intel Core i7 2600k
- 8Gb Corsair ram
- Nvidia GeForce GTX 560 Ti
- Corsair F120 SSD (system disk)

 

[zigzag3143]

It simple.. Your McAfee.

McAfee is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST!

http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

Microsoft Security Essentials - Free Antivirus for Windows


* Did you run a FULL SYSTEM scan with Malwarebytes?

 

[eckert]

Tried...

I removed McAfee completely and didn't experience any bsod until 23.11 (several hours later) so that's a success! But something is still wrong, the scan with Malwarebytes came up empty so I attached the latest dmp-file

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\eckert\031712-7519-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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03c14000 PsLoadedModuleList = 0xfffff800`03e58650
Debug session time: Sat Mar 17 16:10:20.983 2012 (UTC - 6:00)
System Uptime: 0 days 13:46:05.811
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff9600025dbdb, fffff8800b5f15b0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600025dbdb, Address of the instruction which caused the bugcheck
Arg3: fffff8800b5f15b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!GreSetStretchBltMode+3
fffff960`0025dbdb 48895808        mov     qword ptr [rax+8],rbx

CONTEXT:  fffff8800b5f15b0 -- (.cxr 0xfffff8800b5f15b0)
rax=0000000000000001 rbx=fffff900c07cb590 rcx=ffffffffc401121d
rdx=0000000000000003 rsi=0000000000000000 rdi=000000003e050061
rip=fffff9600025dbdb rsp=fffff8800b5f1f98 rbp=ffffffffc401121d
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000017
r11=fffff900c0b04630 r12=0000000000000010 r13=0000000000000004
r14=00000000000004c5 r15=0000000000f0f0f0
iopl=0         nv up ei pl nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010212
win32k!GreSetStretchBltMode+0x3:
fffff960`0025dbdb 48895808        mov     qword ptr [rax+8],rbx ds:002b:00000000`00000009=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  uTorrent.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff9600012e090 to fffff9600025dbdb

STACK_TEXT:  
fffff880`0b5f1f98 fffff960`0012e090 : fffff900`c07cb590 00000000`00000001 fffff880`0b5f2090 fffff960`000ae60f : win32k!GreSetStretchBltMode+0x3
fffff880`0b5f1fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!BltIcon+0x90


CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
    fffff9600025dbda - win32k!GreSetStretchBltMode+2
	[ c4:e4 ]
1 error : !win32k (fffff9600025dbda)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff8800b5f15b0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Points to Memory problems... Other possible causes include Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...


Check your memory for errors:

• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.