BSOD 0x0A

Hello!

Please give me some hints on my problem: i've got many bsod's recently, but after I've updated driver, tested memory, removed avast etc - it seems that only one type of bsod left - it's 0x0000000a. Could you tell me please what i should do next?

Thanks in advance!

VictorL said:

Hello!

Please give me some hints on my problem: i've got many bsod's recently, but after I've updated driver, tested memory, removed avast etc - it seems that only one type of bsod left - it's 0x0000000a. Could you tell me please what i should do next?

Thanks in advance!

Your newest crash was still caused by memory_corruption.

What did you use for memory testing? How long did it run?

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\110910-14679-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20738.x86fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0x82c1b000 PsLoadedModuleList = 0x82d64890
Debug session time: Tue Nov  9 15:42:45.083 2010 (GMT-5)
System Uptime: 0 days 5:48:43.878
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {c1013f2a, 2, 1, 82c9dd43}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: 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: c1013f2a, 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: 82c9dd43, address which referenced memory

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

You still have drivers older than I can imagine

Code:

HASPNT.SYS is a HASP Kernel Device Driver for Windows  NT Aladdin Knowledge Systems. Manufacturer: Aladdin Knowledge Systems   www.aladdin.com.

TBPanel.SYS        0x9b9762c0    0x000012c0    7/26/2002 18:01:04            0x3d41d4b0    0x9b975000

Ok, guys! Thank's for the help.
I used memtest+ and runed it overnight. No mistakes, but i'll do it once again.