BSOD problem

uvedenrode · 25 Aug 2014

Hi. i am new here and this is my first attempt to find a solution to my BSOD problem, so if i am posting in the wrong place, please excuse me. my bosd-s startet the same, randomly, once/day, i downloaded the log collector and i obtained the zip attached. if anyone can help me with this i will be greatful.
Thanks!

koolkat77 · 25 Aug 2014

Welcome to the forum uvedenrode,

Update these drivers:

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to Clean Left Over Driver Files with Driver Sweeper

Drivers - Clean Left over Files after Uninstalling

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Perform a Clean boot:

Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Make scans with the following:

Kaspersky TDSSKiller

Anti-rootkit utility TDSSKiller

ESET online scanner:

Free Online Virus Scanner | ESET

Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

How to Run Disk Check in Windows 7

Upload a screenshot of your hard disk using Crystal Disk Info:

Code:


Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\OVIDIU-PC-25-Aug-14_194650_28\082514-22869-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e5d000 PsLoadedModuleList = 0xfffff800`030a0890
Debug session time: Mon Aug 25 21:23:28.623 2014 (UTC + 6:00)
System Uptime: 0 days 6:43:07.497
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {c0f4, 2, 1, fffff880056b81bc}

*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
Probably caused by : NETwNs64.sys ( NETwNs64+951bc )

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

0: 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: 000000000000c0f4, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880056b81bc, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a100
GetUlongFromAddress: unable to read from fffff8000310a1c0
 000000000000c0f4 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
NETwNs64+951bc
fffff880`056b81bc ff4074          inc     dword ptr [rax+74h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9c550 -- (.trap 0xfffff80000b9c550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000c080 rbx=0000000000000000 rcx=fffffa80096801c0
rdx=fffffa8009680020 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880056b81bc rsp=fffff80000b9c6e0 rbp=0000000000000000
 r8=fffff80000b9c7a8  r9=0000000000000000 r10=fffff88005e15b00
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
NETwNs64+0x951bc:
fffff880`056b81bc ff4074          inc     dword ptr [rax+74h] ds:00000000`0000c0f4=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed2169 to fffff80002ed2bc0

STACK_TEXT:  
fffff800`00b9c408 fffff800`02ed2169 : 00000000`0000000a 00000000`0000c0f4 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c410 fffff800`02ed0de0 : 00000000`00000000 00000000`00000000 fffffa80`08ba1580 fffffa80`075f87a0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c550 fffff880`056b81bc : fffffa80`08ba1580 fffffa80`0977ffc8 fffffa80`08ba1580 fffffa80`0752dd60 : nt!KiPageFault+0x260
fffff800`00b9c6e0 fffffa80`08ba1580 : fffffa80`0977ffc8 fffffa80`08ba1580 fffffa80`0752dd60 00000000`00002800 : NETwNs64+0x951bc
fffff800`00b9c6e8 fffffa80`0977ffc8 : fffffa80`08ba1580 fffffa80`0752dd60 00000000`00002800 00000000`000000cf : 0xfffffa80`08ba1580
fffff800`00b9c6f0 fffffa80`08ba1580 : fffffa80`0752dd60 00000000`00002800 00000000`000000cf 00000000`00000000 : 0xfffffa80`0977ffc8
fffff800`00b9c6f8 fffffa80`0752dd60 : 00000000`00002800 00000000`000000cf 00000000`00000000 fffff880`05632e59 : 0xfffffa80`08ba1580
fffff800`00b9c700 00000000`00002800 : 00000000`000000cf 00000000`00000000 fffff880`05632e59 00000000`00000030 : 0xfffffa80`0752dd60
fffff800`00b9c708 00000000`000000cf : 00000000`00000000 fffff880`05632e59 00000000`00000030 ffff0080`051b45ac : 0x2800
fffff800`00b9c710 00000000`00000000 : fffff880`05632e59 00000000`00000030 ffff0080`051b45ac 00000000`00002800 : 0xcf


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETwNs64+951bc
fffff880`056b81bc ff4074          inc     dword ptr [rax+74h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETwNs64+951bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETwNs64

IMAGE_NAME:  NETwNs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d10df1b

FAILURE_BUCKET_ID:  X64_0xD1_NETwNs64+951bc

BUCKET_ID:  X64_0xD1_NETwNs64+951bc

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

0: kd> lmvm NETwNs64
start             end                 module name
fffff880`05623000 fffff880`05e8e000   NETwNs64 T (no symbols)           
    Loaded symbol image file: NETwNs64.sys
    Image path: \SystemRoot\system32\DRIVERS\NETwNs64.sys
    Image name: NETwNs64.sys
    Timestamp:        Tue Dec 21 23:08:43 2010 (4D10DF1B)
    CheckSum:         00823168
    ImageSize:        0086B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4