Random BSOD

Hallo. I get random BSOD.

System SPEC.
x86
retail
system old ~4 yers
OS installation old 2 days

Problem Devices:

Code:

Null	ROOT\LEGACY_NULL\0000	This device is not present, is not working properly, or does not have all its drivers installed.

Antivirus Software:

Code:

avgnt.exe	c:\program files\avira\antivir desktop\avgnt.exe	744	8	200	1380	2012.03.06 11:55	12.1.0.17	252,45 KB (258.512 bytes)	2012.03.05 18:59
avguard.exe	c:\program files\avira\antivir desktop\avguard.exe	1804	8	200	1380	2012.03.06 11:55	12.1.0.18	107,45 KB (110.032 bytes)	2012.03.05 18:59
avshadow.exe	c:\program files\avira\antivir desktop\avshadow.exe	2284	8	200	1380	2012.03.06 11:56	12.1.0.10	78,45 KB (80.336 bytes)	2012.03.05 18:59
sched.exe	c:\program files\avira\antivir desktop\sched.exe	1496	8	200	1380	2012.03.06 11:55	12.1.0.18	84,20 KB (86.224 bytes)	2012.03.05 18:59

Possible out of date drivers:

Code:

HECI	8fb7c000	8fb86d80	Mon Jul 09 11:40:18 2007 (46927302)	00012d46		HECI.sys
stwrt	94f0c000	94f71000	Thu Mar 12 11:59:45 2009 (49b94d91)	00066609		stwrt.sys
e1e6032	8fb87000	8fbbf000	Tue Mar 24 12:16:11 2009 (49c9236b)	0003ff3e		e1e6032.sys
ssmdrv	8bdf2000	8bdf7a00	Tue May 05 04:05:18 2009 (4a000f5e)	00012cfa		ssmdrv.sys

HECI.sys
stwrt.sys
e1e6032.sys
ssmdrv.sys

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\piktas\bsod\Windows_NT6_BSOD_jcgriff2\030612-23000-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82a39000 PsLoadedModuleList = 0x82b824d0
Debug session time: Tue Mar  6 01:49:42.299 2012 (UTC - 7:00)
System Uptime: 0 days 0:14:02.018
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {90, 2, 1, 82a05839}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000090, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82a05839, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82ba2848
Unable to read MiSystemVaType memory at 82b81e20
 00000090 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+29
82a05839 8902            mov     dword ptr [edx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  89143a68 -- (.trap 0xffffffff89143a68)
ErrCode = 00000002
eax=89143aec ebx=84395d48 ecx=863900c8 edx=00000090 esi=86390094 edi=00000000
eip=82a05839 esp=89143adc ebp=89143af8 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29:
82a05839 8902            mov     dword ptr [edx],eax  ds:0023:00000090=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82a05839 to 82a7a5fb

STACK_TEXT:  
89143a68 82a05839 badb0d00 00000090 84395d48 nt!KiTrap0E+0x2cf
89143ad8 82ac37b1 9beafaf8 89143b38 9beafa08 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29
89143af8 870b8826 00000000 85df4778 00000000 nt!ExIsResourceAcquiredSharedLite+0x4d
89143b14 870c2863 85df4778 9beafaf8 00000000 Ntfs!TxfCheckForFloaterDelete+0x47
89143b9c 82a7058e 00000000 860277e8 860277e8 Ntfs!NtfsFsdClose+0x490
89143bb4 86db720c 85423ed8 860277e8 00000000 nt!IofCallDriver+0x63
89143bd8 86db73cb 89143bf8 85423ed8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
89143c10 82a7058e 85423ed8 860277e8 8543c024 fltmgr!FltpDispatch+0xc5
89143c28 82c6aa1f 8438bde8 85df4760 00000000 nt!IofCallDriver+0x63
89143c6c 82c5b619 85df4778 85df4778 85df4760 nt!IopDeleteFile+0x10c
89143c84 82ab1d40 00000000 000c0000 00000000 nt!ObpRemoveObjectRoutine+0x59
89143c98 82ab1cb0 85df4778 82c60ff9 844c9c10 nt!ObfDereferenceObjectWithTag+0x88
89143ca0 82c60ff9 844c9c10 844c9c38 82ba49c0 nt!ObfDereferenceObject+0xd
89143ccc 82a9af04 844c9c10 00000000 00000000 nt!MiSegmentDelete+0x191
89143d28 82a9b225 84395d48 00000000 00000000 nt!MiProcessDereferenceList+0xdb
89143d50 82c41fda 00000000 9e85d811 00000000 nt!MiDereferenceSegmentThread+0xc5
89143d90 82aea1f9 82a9b15e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTrap0E+2cf
82a7a5fb 833d44d7b98200  cmp     dword ptr [nt!KiFreezeFlag (82b9d744)],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiTrap0E+2cf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea76eb4

FAILURE_BUCKET_ID:  0xA_nt!KiTrap0E+2cf

BUCKET_ID:  0xA_nt!KiTrap0E+2cf

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

Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases. Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

• If you are overclocking any hardware, please stop.
  
  
• Update all Intel drivers with the Intel® Driver Update Utility.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
  
  
• Do the long and short tests with SeaTools | Seagate to test the hard disk.
  
  
• Remove Avira with Start Menu -> Control Panel -> Uninstall a program and then run the Avira RegistryCleaner to remove all remnants. Install
  Microsoft Security Essentials - Free Antivirus for Windows
  or the
  Good and Free system security combination.

All stock settings (no OC).
Drivers are newest from intel page.
Disk checked with HD tune no bad sector.
Windows fresh installed from retail dvd.
Memtest86 3passes no errors.

BIOS now updated to newest.

In forum i saw topick with similar problem and one guy says that this BSOD coused by IDT 92xx driver. So with my audio hardware is everything ok?

All audio drivers look good. You should run Memtest86+ for seven passes. Also, have you removed Avira?

Any new crash reports?

So far so good :)

TY for HELP!

You're welcome. Monitor the system for the next few days and post back how it is responding.