Solved BSOD once, now BSOD everytime on startup when it gets to desktop.

[Pezdspencer]

Hello all, thanks in advance.

I haven't had BSOD problems anytime recently with this computer (Previously had issues with some drivers but I've replaced hardware and drivers long ago and no longer had issues). Tonight I was playing Wildstar and I got a BSOD for my ATI drivers (Which I'd had before, but long ago) and normally a restart would fix it and everything would be fine.

Now everytime the computer boots and gets to the desktop it BSOD's on me.

Currently on said computer in safe mode, no problems currently here.

Here is my dump info for 3 recent BSOD, unfortunately don't have the first ATI one.


Also attaching the .zip as instructed.
==================================================
Dump File : 061714-10155-01.dmp
Crash Time : 6/17/2014 7:27:08 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`038a6622
Parameter 3 : fffff880`06ec1b50
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061714-10155-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 276,296
==================================================

==================================================
Dump File : 061714-10748-01.dmp
Crash Time : 6/17/2014 6:50:48 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`038fe622
Parameter 3 : fffff880`033e06d8
Parameter 4 : fffff880`033dff30
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+a6622
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor : x64
Crash Address : ntoskrnl.exe+a6622
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061714-10748-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 276,296
==================================================

==================================================
Dump File : 061714-10296-01.dmp
Crash Time : 6/17/2014 6:39:39 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff880`0132763c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : fffff880`0132763c
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+f163c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061714-10296-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 276,296
==================================================

 

[Pezdspencer]

Phone won't let me edit original post for whatever reason. Wanted to add more info.

I run an eyefinity 3x1 setup on my 7970. I haven't had any heat issues that I've noticed. Made sure when I bought my fx8350 that I got an aftermarket cooler since they run hot usually. I'll try to think of more odd behavior if it exists.

Edit: Forgot to mention, repair from win 7 disk didn't work, chkdsk found nothing, and system restore fails from multiple points.

 

[PeregrineX]

Hello, and welcome to SevenForums!

Your BSOD is being caused by your Avast! Anti-Virus:

*******************************************************************************
*                                                                             *
*                        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: fffff8800132763c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8800132763c, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003ac6100
GetUlongFromAddress: unable to read from fffff80003ac61c0
 fffff8800132763c Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
Ntfs! ?? ::NNGAKEGL::`string'+2ee0
fffff880`0132763c 55              push    rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

[COLOR="Red"]PROCESS_NAME:  AvastSvc.exe[/COLOR]

TRAP_FRAME:  fffff88007833da0 -- (.trap 0xfffff88007833da0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800132763c rbx=0000000000000000 rcx=fffff88007833f70
rdx=fffff880078354a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800132763c rsp=fffff88007833f38 rbp=fffff88007834070
 r8=fffff880078346f0  r9=fffff88007834070 r10=fffff88007835680
r11=fffff88007833fa8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
Ntfs! ?? ::NNGAKEGL::`string'+0x2ee0:
fffff880`0132763c 55              push    rbp
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000388e169 to fffff8000388ebc0

FAILED_INSTRUCTION_ADDRESS: 
Ntfs! ?? ::NNGAKEGL::`string'+2ee0
fffff880`0132763c 55              push    rbp

STACK_TEXT:  
fffff880`07833c58 fffff800`0388e169 : 00000000`0000000a fffff880`0132763c 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`07833c60 fffff800`0388cde0 : fffffa80`0e1b84d0 fffff800`03e00593 fffffa80`0e1b84d0 fffff880`01287b34 : nt!KiBugCheckDispatch+0x69
fffff880`07833da0 fffff880`0132763c : fffff800`038b9cdc fffffa80`10e72c30 fffff880`07834f00 fffff8a0`0d387740 : nt!KiPageFault+0x260
fffff880`07833f38 fffff800`038b9cdc : fffffa80`10e72c30 fffff880`07834f00 fffff8a0`0d387740 00000000`00016ba3 : Ntfs! ?? ::NNGAKEGL::`string'+0x2ee0
fffff880`07833f40 fffff800`038b975d : fffff880`01287b28 fffff880`078354a0 00000000`00000000 fffff880`01236000 : nt!_C_specific_handler+0x8c
fffff880`07833fb0 fffff800`038b8535 : fffff880`01287b28 fffff880`07834028 fffff880`07834e98 fffff880`01236000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`07833fe0 fffff800`038c94c1 : fffff880`07834e98 fffff880`078346f0 fffff880`00000000 fffff880`07835180 : nt!RtlDispatchException+0x415
fffff880`078346c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x135


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs! ?? ::NNGAKEGL::`string'+2ee0
fffff880`0132763c 55              push    rbp

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Ntfs! ?? ::NNGAKEGL::`string'+2ee0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52e1be8a

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+2ee0

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+2ee0

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

Your best bet would be to uninstall Avast! completely, as it is known to cause problems. Try that, and inform us of the results.

Best of luck,

PeregrineX

 

[Pezdspencer]

Thank you for the reply, it would make sense because Avast had recently said there was an update not long before the first bsod. It probably updated itself and caused it.

Currently working, but I'll try as soon as I'm home. Thank you!

 

[Pezdspencer]

Cold booted fine when I got home, no BSOD or anything so far. I'm still going to look into that Avast! issue though, thanks!