Blue Screen of Death ;_;

YukiNeko · 02 Nov 2010

Running Windows 7 Ultimate (32-bit) - OEM/TechNet. This is the original OS (last re-installed to fresh hard drive around August 2010 (after original OSRAID became corrupted). Hardware age is 2 years (OS HDD is about 1 year old, was previously used for backups). RAM was recently replaced beginning of October (thought that was the original source of the BSOD's...)

In the perf-monitor, it indicates the dirty bit is set on a disk. That's the old windows installation disk. It won't boot Windows any more, but the data is still intact, so it's used for looking up old information till I permanently remove it.

The driver failure is more than likely the MotionJoy 6 driver (Bluetooth/USB driver for PS3 controller), or my old scanner (Memorex 6136u).

Thanks for looking into this error ;_;

zigzag3143 · 02 Nov 2010

YukiNeko said:

Running Windows 7 Ultimate (32-bit) - OEM/TechNet. This is the original OS (last re-installed to fresh hard drive around August 2010 (after original OSRAID became corrupted). Hardware age is 2 years (OS HDD is about 1 year old, was previously used for backups). RAM was recently replaced beginning of October (thought that was the original source of the BSOD's...)

In the perf-monitor, it indicates the dirty bit is set on a disk. That's the old windows installation disk. It won't boot Windows any more, but the data is still intact, so it's used for looking up old information till I permanently remove it.

The driver failure is more than likely the MotionJoy 6 driver (Bluetooth/USB driver for PS3 controller), or my old scanner (Memorex 6136u).

Thanks for looking into this error ;_;

RUNNING THEM NOW bE BACK IN 10

There are several causes

1- ASACPI.SYS 2005 invariably causes hardware issues

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

2- Old drivers

Code:

ASACPI.sys        0x8e410420    0x00001420    0x411c2d04    8/12/2004 22:52:52            0x8e40f000                
xusb21.sys        0x8dbfec80    0x0000cc80    0x45d666e4    2/16/2007 22:22:28            0x8dbf2000                
yk62x86.sys        0x8ddee000    0x00050000    0x49a2b642    2/23/2009 10:44:18            0x8dd9e000                
iaStorV.sys        0x88d06000    0x000db000    0x49dcd6e2    4/8/2009 12:54:58            0x88c2b000                
spldr.sys        0x893e6000    0x00008000    0x4a084ebb    5/11/2009 12:13:47            0x893de000                
amdxata.sys        0x88d45000    0x00009000    0x4a12f30f    5/19/2009 13:57:35            0x88d3c000

3-Memory corruption Run memtest
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

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\110210-148434-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a3b000 PsLoadedModuleList = 0x82b83810
Debug session time: Tue Nov  2 13:29:46.508 2010 (GMT-4)
System Uptime: 3 days 19:09:31.006
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {bbee405f, 0, 0, 82aad631}

Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1e5 )

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: bbee405f, memory referenced
Arg2: 00000000, IRQL
Arg3: 00000000, 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: 82aad631, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82ba3718
Unable to read MiSystemVaType memory at 82b83160
 bbee405f 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiAgeWorkingSet+1e5
82aad631 0fb6460f        movzx   eax,byte ptr [esi+0Fh]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  8df50a2c -- (.trap 0xffffffff8df50a2c)
ErrCode = 00000000
eax=00000000 ebx=8c825964 ecx=ffffffff edx=82b6f300 esi=bbee4050 edi=c0794788
eip=82aad631 esp=8df50aa0 ebp=8df50c10 iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
nt!MiAgeWorkingSet+0x1e5:
82aad631 0fb6460f        movzx   eax,byte ptr [esi+0Fh]     ds:0023:bbee405f=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82aad631 to 82a8182b

STACK_TEXT:  
8df50a2c 82aad631 badb0d00 82b6f300 00000000 nt!KiTrap0E+0x2cf
8df50c10 82aae61b 82b6f300 00000001 00000001 nt!MiAgeWorkingSet+0x1e5
8df50c5c 82aae2e0 00000002 00000001 00000000 nt!MiProcessWorkingSets+0x25b
8df50c88 82ac421f 00000000 855d5988 00000000 nt!MmWorkingSetManager+0xa4
8df50d50 82c496d3 00000000 bdd8c810 00000000 nt!KeBalanceSetManager+0x1af
8df50d90 82afb0f9 82ac4070 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+1e5
82aad631 0fb6460f        movzx   eax,byte ptr [esi+0Fh]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiAgeWorkingSet+1e5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiAgeWorkingSet+1e5

BUCKET_ID:  0xA_nt!MiAgeWorkingSet+1e5

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