Random BSOD's when using computer

Torian · 27 Mar 2012

I keep repeatedly Bsoding, and I really want to find out why.

Is Windows 7 . . .
- x86 (32-bit) or x64 ?
- the original installed OS on the system? Yes.
- an OEM or full retail version? Full Retail
- What is the age of system (hardware)? About 1-2 years old
- What is the age of OS installation (have you re-installed the OS?) Almost 1 year ago.

writhziden · 28 Mar 2012

Security Software:

Code:

mbamgui.exe	c:\program files (x86)\malwarebytes' anti-malware\mbamgui.exe	1392	8	200	1380	3/27/2012 5:07 PM	Not Available	Not Available	Not Available
mbamservice.exe	c:\program files (x86)\malwarebytes' anti-malware\mbamservice.exe	4960	8	80	80	3/27/2012 5:10 PM	Not Available	Not Available	Not Available

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Torian\Windows_NT6_BSOD_jcgriff2\032712-41059-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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03265000 PsLoadedModuleList = 0xfffff800`034aa670
Debug session time: Tue Mar 27 15:04:40.911 2012 (UTC - 6:00)
System Uptime: 0 days 2:16:26.269
Loading Kernel Symbols
..............................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {80, 2, 1, fffff800032ebc1f}

Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+5f )

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: 0000000000000080, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800032ebc1f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003514100
 0000000000000080 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!KeAcquireInStackQueuedSpinLock+5f
fffff800`032ebc1f 488717          xchg    rdx,qword ptr [rdi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from fffff800032eb4a9 to fffff88001202c61

STACK_TEXT:  
fffff800`00b9cc98 fffff800`032eb4a9 : 00000000`0027dc50 fffffa80`04f2e2d0 fffff800`03457e80 00000000`00000001 : 0xfffff880`01202c61
fffff800`00b9cca0 fffff800`032d993c : fffff800`03457e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!KeAcquireInStackQueuedSpinLock+5f
fffff800`032ebc1f 488717          xchg    rdx,qword ptr [rdi]

SYMBOL_NAME:  nt!KeAcquireInStackQueuedSpinLock+5f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f

BUCKET_ID:  X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f

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

There is a lot of corruption going on with your system.

If you are overclocking any hardware, please stop.
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.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
Run the Hitachi Drive Fitness Test to check whether your Hitachi hard disk is working properly. Run the short and long tests with SeaTools to check your Samsung hard disk.
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.