Windows7 recurring BSOD

petapacket

petapacket

petapacket

Associate
Joined
25 Nov 2011
Posts
131
When it BSOD, i get one of the listed messages the driver ntoskrnl.exe is invariably mentioned, sometimes with other system drivers. With each of these event types a bugcheck record and a system shutdown (41) is recorded, the list of correlating error events with the failure type are listed further below in red, this is logged every time this happens.

PAGE_FAULT_IN_NONPAGED_AREA
ATTEMPTED_WRITE_TO_READONLY_MEMORY
DRIVER_IRQL_NOT_LESS_OR_EQUAL
SYSTEM_SERVICE_EXCEPTION
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



7001
The DHCP Client service depends on the Ancillary Function Driver for Winsock service which failed to start because of the following error:
A device attached to the system is not functioning.

The DNS Client service depends on the NetIO Legacy TDI Support Driver service which failed to start because of the following error:
A device attached to the system is not functioning.

The TCP/IP NetBIOS Helper service depends on the Ancillary Function Driver for Winsock service which failed to start because of the following error:
A device attached to the system is not functioning.

The Network Store Interface Service service depends on the NSI proxy service driver. service which failed to start because of the following error:
A device attached to the system is not functioning.

The Workstation service depends on the Network Store Interface Service service which failed to start because of the following error:
The dependency service or group failed to start.

The IP Helper service depends on the Network Store Interface Service service which failed to start because of the following error:
The dependency service or group failed to start.

The SMB MiniRedirector Wrapper and Engine service depends on the Redirected Buffering Sub Sysytem service which failed to start because of the following error:
A device attached to the system is not functioning.

The SMB 1.x MiniRedirector service depends on the SMB MiniRedirector Wrapper and Engine service which failed to start because of the following error:
The dependency service or group failed to start.

The SMB 2.0 MiniRedirector service depends on the SMB MiniRedirector Wrapper and Engine service which failed to start because of the following error:
The dependency service or group failed to start.

The Network Connections service depends on the Network Store Interface Service service which failed to start because of the following error:
The dependency service or group failed to start.

The Network Location Awareness service depends on the Network Store Interface Service service which failed to start because of the following error:
The dependency service or group failed to start.

The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error:
The dependency service or group failed to start.

The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error:
The dependency service or group failed to start.

The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error:
The dependency service or group failed to start.

The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error:
The dependency service or group failed to start.

The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error:
The dependency service or group failed to start.

The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error:
The dependency service or group failed to start.


7026
The following boot-start or system-start driver(s) failed to load:
AFD
AppleCharger
aswRdr
aswSnx
aswSP
aswTdi
DfsC
discache
NetBIOS
NetBT
nsiproxy
Psched
rdbss
spldr
tdx
vwififlt
Wanarpv6
WfpLwf

I'm begging for competent support ASAP before i have to RMA, date closing in...
 
Yes i thought somebody might say that. Sorry, the walls had to bleed!

i73770k x48 blck100.xy
team extreme ddr3 2.4ghz 11-11-11-28 8gb
gaz77xud5h
gtx570n twin frozer 2 800mhz
antec750red
 
WHOCRASHED REPORT:







On Sat 08/09/2012 03:35:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090812-4804-01.dmp
This was probably caused by the following module: iastor.sys (iaStor+0x5DD4A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880012B6D4A, 0xFFFFF88003D616F8, 0xFFFFF88003D60F50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastor.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Google query: iastor.sys Intel Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Sat 08/09/2012 03:35:23 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iastor.sys (iaStor+0x5DD4A)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF880012B6D4A, 0xFFFFF88003D616F8, 0xFFFFF88003D60F50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastor.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Google query: iastor.sys Intel Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED




On Sat 08/09/2012 01:46:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090812-7347-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x5C17)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88006AF8C17, 0xFFFFF88003F46958, 0xFFFFF88003F461B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: aswmonflt.sys AVAST Software SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Fri 07/09/2012 22:59:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090812-7285-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034CDCF2, 0xFFFFF8800BF475B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 06/09/2012 16:51:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090612-7566-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0xAA001448, 0x7, 0x0, 0xFFFFF8800F8EFF45)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 06/09/2012 10:41:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090612-7332-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6A5A)
Bugcheck code: 0xBE (0xFFFFF96000106A5A, 0x3F00001CC8FB021, 0xFFFFF88008A997F0, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 05/09/2012 10:08:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090512-10998-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD0, 0x1, 0xFFFFF800034DA32C, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 05/09/2012 10:04:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090512-9968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD0, 0x1, 0xFFFFF8000348955C, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
 
Thing is i know this i use a similar program that pinpoints these drivers, the questions is why are they malfunctioning. Is it my OC, is it crappy software, should i just delete them, etc etc. I don';t know what to do next, more importantly how to analyze the result. I sent a report to AVAST.
 
I've tried formatting, reinstalling w7, memtest86+, intel cpu diagnostics, removing page file, updating, checking drivers.. etc im sure ive forgotten steps.

The point remains that the failure procedure is identical each time and i need to know what to do >_< it is happening in firefox, netflix every 1hr.
 
Have you got your power settings correct? I had similar problems when the computer was set to sleep after a time, then caused faults with services stop/start, wich in turn caused a BSOD.
 
I've updated my Nvidia drivers, and haven't been using Netflix for a couple of days. BSOD stops until i try to hit 5Ghz. But my games still crash from time to time. The error I'd been working on fr the last few days is the KSOD after welcome screen, it seems to have gone with the Beta Nvidia driver.

As for sleep. it is possible and i had considered it as the timings seem appropriate, although i had thought watching a video is deemed as active behavior, i don't know the protocol's details.
 
petapacket said:
Is it my OC, is it crappy software, should i just delete them, etc etc. I don';t know what to do next, more importantly how to analyze the result.
Click to expand...

It could be any/all, You need to eliminate each possibility. Start with the over-clock, put everything back to stock. If not that try unpluging all USB, Firewire etc (except keyboard & Mouse). Next is remove any expansion cards except video. Also try the How to Show and Access Hidden and Ghost Devices and Drivers in Device Manager
 
I'd done the equivalent, and repeated the steps in the guide, no ghosts.

My PC hasn't done anything dodgy since the nvidia update and w7 updates this morning. I'm going to stress test it a little to see if she blows.
 
You must log in or register to reply here.
Back
Top Bottom