BSOD Randomly on a new PC Windows 7 pro 64-bit

[lsnyman]

I am also getting this error repeatedly but at different times. This is a brand new computer with hardly anything loaded as yet except for the drivers supplied with motherboards and graphics cards etc.
Please can someone assist, it would be very much appreciated.

 

[Skylais]

Ok well software concerns
1. aswTdi.SYS : avast! TDI Filter Driver

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Skyler\AppData\Local\Temp\Rar$DIa0.597\091512-20872-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03258000 PsLoadedModuleList = 0xfffff800`0349c670
Debug session time: Sat Sep 15 11:01:29.874 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:36.733
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
...
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880017ebc3a, fffff8800357dd78, fffff8800357d5d0}

Probably caused by : [COLOR="red"]aswTdi.SYS[/COLOR] ( aswTdi+4c3a )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880017ebc3a, The address that the exception occurred at
Arg3: fffff8800357dd78, Exception Record Address
Arg4: fffff8800357d5d0, Context Record Address

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


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

FAULTING_IP: 
aswTdi+4c3a
fffff880`017ebc3a 48394b18        cmp     qword ptr [rbx+18h],rcx

EXCEPTION_RECORD:  fffff8800357dd78 -- (.exr 0xfffff8800357dd78)
ExceptionAddress: fffff880017ebc3a (aswTdi+0x0000000000004c3a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800357d5d0 -- (.cxr 0xfffff8800357d5d0)
rax=0000000000000000 rbx=fffdfa800ce4b970 rcx=fffffa800d5db190
rdx=fffff880017f1ac0 rsi=fffffa800a868f20 rdi=fffffa800c998c38
rip=fffff880017ebc3a rsp=fffff8800357dfb0 rbp=0000000000000001
 r8=fffffa800a868f20  r9=0000000000000000 r10=fffffa8006a4bc90
r11=fffff8800357e0d8 r12=fffffa800cb61100 r13=0000000000000000
r14=0000000000000000 r15=0000000000000002
iopl=0         nv up ei ng nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010283
aswTdi+0x4c3a:
fffff880`017ebc3a 48394b18        cmp     qword ptr [rbx+18h],rcx ds:002b:fffdfa80`0ce4b988=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003506100
GetUlongFromAddress: unable to read from fffff800035061c0
 ffffffffffffffff 

FOLLOWUP_IP: 
aswTdi+4c3a
fffff880`017ebc3a 48394b18        cmp     qword ptr [rbx+18h],rcx

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffffa800a868f20 to fffff880017ebc3a

STACK_TEXT:  
fffff880`0357dfb0 fffffa80`0a868f20 : 00000000`00000000 fffffa80`0c998c38 fffffa80`0c998bf3 00000000`00003580 : aswTdi+0x4c3a
fffff880`0357dfb8 00000000`00000000 : fffffa80`0c998c38 fffffa80`0c998bf3 00000000`00003580 fffffa80`0d5db190 : 0xfffffa80`0a868f20


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aswTdi+4c3a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswTdi

IMAGE_NAME:  [COLOR="red"]aswTdi.SYS[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  50334f3d

STACK_COMMAND:  .cxr 0xfffff8800357d5d0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_aswTdi+4c3a

BUCKET_ID:  X64_0x7E_aswTdi+4c3a

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

I would try uninstalling avast for now, just until we rule a few things out. I suggest using MSE as your antivirus. it can be downloaded here : Microsoft Security Essentials - Free Antivirus for Windows

2. The rest are not conclusive or beneficial really. They all point to windows drivers which have a very very very very very small chance of being the problem. Check the seating on the graphic card, just to be sure.

Also run this and upload the latest dump file you recieve : Driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[lsnyman]

Thank you for the reply
I am trying that now.

 

[lsnyman]

Here is todays dump. It crashed once in the early hours of today and again this morning. I am going to pick up some extra memory modules today to rule out bad memory.
Any help would be appreciated.

 

[Skylais]

Ok well the previous one before the last one is MBfilt64.sys : Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver)
For this make sure you have the right drivers from the asrock site, etc. If you do then download the correct ones for the realtek hidef audio driver here : Realtek
The latest one was iaStor.sys : Intel Storage drivers
For this one, check the asrock site one last time and make sure you have the right drivers, if you do then use this : http://downloadcenter.intel.com/Default.aspx
*will need java to run*
Also to top this, i would like you to open "device manager" and screenshot or note any that have a yellow mark next to them.

 

[lsnyman]

So yesterday when I opened the case to insert new RAM, I saw that your first intuition was correct and the video card EVGA GTX550Ti was not seated properly, so I corrected this without changing anything. The computer started ok and ran well all day, However when I came in this AM, Blue Screen again. I made the dump and changed the RAM which did not help as it just gave another series of bluescreens again. I could only boot to safe mode and in safemode I created another dump, so the event files (2) are from that safe mode dump.
I will go ahead and update every driver I can find, but it seems the error is different every time. After safe mode it started ok again.

 

[Skylais]

Aha we got something new this time. In 1 of them the audio driver was blamed again. two of them contain literally nothing, and were probably corrupted. Another blames ISCTD64.sys : Intel Smart Connect Technology Driver
Now when put together one of the original ones was :
iaStor.sys : Intel Storage drivers
The new one is
ISCTD64.sys : Intel Smart Connect Technology Driver :
Seems to be an intel problem. Now one thing on the latest one (driver right above this), when looking at the driver reference table it says this is not on the site and to check with the oem. So again double check them drivers and if you have all the right ones try using this :
Update intel drivers: Intel® Driver Update Utility

 

[karlsnooks]

Isnyman,

Please visit this website:
ASRock > Z77 Pro3

There you will find the latest drivers which are SPECIFICALLY for your motherboard.

Take close note that the VIDEO driver was updated recently, 7 July of this year.

 

[karlsnooks]

Lysnman,
To save me and passerbys who just might have an idea for you,
then:
Help us to Help You.

Completely and fully fill in your system specs and here is how:
Update your SevenForums System Specs
User CP (located on the top menu bar) |
Your Profile | Edit System Spec (left-hand column)

To gather info, use Speccy (my favorite) or SIW or System Info

In the System Manufacturer Block, enter:
Ø Manufacturer and Model OR Custom build.
Ø ADD the word laptop, desktop, netbook or tablet.
For example:
Toshiba Satellite L305D notebook.

Provide full windows version info, for example:
MS Windows 7 Ultimate SP1 64-bit

Use the “Other Info” block for Optical Reader,
Mouse, touchpad, wifi adapter, speakers, monitor, etc

Scroll down and click on SAVE CHANGES.

With Speccy, you can select with your mouse/touchpad info from the display
and paste that info into your specs.

SIW is a marvelous program, but the free version does not offer
this capability.
=====================================

In case, your wondering I would like to check on a couple of your system components and those filled in specs will do the job for me.

 

[lsnyman]

Thanks
I have updated the Profile specs. I have also updated all the drivers I could find.
It is running mnuch better but still there is a driver crashing when it is stressed by the driver verifier.
I have attached the dump from this morning.
Thanks again for your help.

 

[karlsnooks]

go to an elevated command prompt

run following commands:

verifier /reset
exit

You just turned off driver verifier and returned from the command shell.

Now, let us see if you are still getting bsods.

Go To an Elevated Command Prompt


Elevated command prompt = Run CMD.EXE as administrator

WIN | type CMD.EXE | do not hit Enter |
in the PROGRAMS list, right-click on CMD.EXE |
choose "Run as administrator" |
Click on the YES button (if such appears)

WIN key = key with Microsoft log on top

for the guru:
WIN | type CMD.EXE | CTRL+SHIFT+ENTER key combo | ALT+Y keycombo

 

[lsnyman]

Well i disabled the verifier and it has been running just fine for the last few days, and just when I was going to report back and say it seems to be solved, it went BSOD again today right in the middle of typing an email.
Attached is the logs. I dont know if it is related to previous BSOD or not.
thanks again.

 

[Xyreon]

I have the same boards and BSOD happens often. Gave it some search and found this
Solution for Asrock BSOD on Extreme or Pro boards - asrock - Motherboards-Memory

see if it solves your problem I disabled mine. Will test for a week for result. Good luck, for both of us.
And to troubleshooters in this forum, please take note of Asrock boards with this optiong "STAT Aggressive..." causing BSODs.

Thanks.