Suddenly BSOD is a problem.

johnathangalt · 07 Nov 2010

All,
I'm stumped. Got Windows 7 Ultimate x64 running on my Core 2 Duo Wolfdale, been running it for months without problems. One day I decide its been a while I should reformat. I procrastinate as usual, then a BSOD pops up out of the blue, first time since initial install 6 months prior, and I see it as a sign to get of my butt. Perform fresh reinstall, everything seems fine then, as I'm installing my programming, BSOD starts popping up every few hours. Freaked, I perform another fresh reinstall, before installing ANYTHING, even before I activate, I get another BSOD. I'm not sure if this is a sudden hardware failure, or a software problem. At this point I'm operating beyond my capabilities. Please help. Thanks in advance.

CarlTR6 · 07 Nov 2010

Hi, Johnathan; and welcome to the forum Sorry you are having problems. I will take a look and be back.

Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0285d000 PsLoadedModuleList = 0xfffff800`02a9ae50
Debug session time: Tue Oct 26 07:38:36.659 2010 (GMT-5)
System Uptime: 0 days 20:53:51.205
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa0003b41470, 2, 1, fffff80002913e9f}

Probably caused by : memory_corruption ( nt!MiReferenceControlAreaForCacheManager+167 )

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

1: 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: fffffa0003b41470, 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: fffff80002913e9f, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'udfs' and 'hiber_pciide' overlap

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b050e0
 fffffa0003b41470 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReferenceControlAreaForCacheManager+167
fffff800`02913e9f 48894108        mov     qword ptr [rcx+8],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff88004641440 -- (.trap 0xfffff88004641440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80055a5018 rbx=0000000000000000 rcx=fffffa0003b41468
rdx=0000000080000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002913e9f rsp=fffff880046415d0 rbp=fffff880009e8180
 r8=0000000000000000  r9=fffff880009e8180 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReferenceControlAreaForCacheManager+0x167:
fffff800`02913e9f 48894108        mov     qword ptr [rcx+8],rax ds:fffffa00`03b41470=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028ce469 to fffff800028cef00

STACK_TEXT:  
fffff880`046412f8 fffff800`028ce469 : 00000000`0000000a fffffa00`03b41470 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`04641300 fffff800`028cd0e0 : fffffa80`044a36e0 00000000`00000001 00000000`00000000 fffff800`02bcee46 : nt!KiBugCheckDispatch+0x69
fffff880`04641440 fffff800`02913e9f : fffff880`0371ca00 fffffa80`044a3a80 fffff880`0371ca80 fffff880`012fcce1 : nt!KiPageFault+0x260
fffff880`046415d0 fffff800`02bc6ee8 : 00000000`00000001 00000000`08000000 00000000`00000000 fffff880`0371ca10 : nt!MiReferenceControlAreaForCacheManager+0x167
fffff880`04641630 fffff800`028f6ba5 : fffffa80`057aa838 fffffa80`057aa838 00000000`00000000 fffff880`046418a0 : nt!MmCreateSection+0x13c
fffff880`04641840 fffff880`0130b2b9 : 00000000`00000000 fffffa80`00000000 fffff8a0`036c1101 fffff880`012a9088 : nt!CcInitializeCacheMap+0x745
fffff880`04641920 fffff880`01307247 : fffffa80`0388ccf0 fffff8a0`036c1140 fffff8a0`036c1101 fffff8a0`0827e301 : Ntfs!NtfsCreateInternalAttributeStream+0x2c1
fffff880`04641a10 fffff880`0130ad71 : fffff8a0`036c1140 00000000`00000000 fffff8a0`0827e3c0 fffffa80`0388ccf0 : Ntfs!FindFirstIndexEntry+0x41c
fffff880`04641aa0 fffff880`012f3677 : fffffa80`0388ccf0 fffffa80`0388ccf0 fffff8a0`06da5501 00000000`00000000 : Ntfs!NtfsFindIndexEntry+0x5d
fffff880`04641b10 fffff880`0125cc0d : fffffa80`0388ccf0 fffffa80`04659c10 fffff880`0371d450 fffffa80`0380e400 : Ntfs!NtfsCommonCreate+0x7c7
fffff880`04641cf0 fffff800`028c6d87 : fffff880`0371d3c0 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`04641d20 fffff800`028c6d41 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`0371d290 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReferenceControlAreaForCacheManager+167
fffff800`02913e9f 48894108        mov     qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReferenceControlAreaForCacheManager+167

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReferenceControlAreaForCacheManager+167

BUCKET_ID:  X64_0xA_nt!MiReferenceControlAreaForCacheManager+167

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

The dump blames memory corruption; so we need to find out what is causing the memory corruption. Unfortunately, the dump does not point to a specific cause.

Outdated drivers are one cause and I find the following out of date driver loading on your system. Update this driver.

atikmdag.sys Fri Apr 24 06:51:57 2009 - ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)Global Provider of Innovative Graphics, Processors and Media Solutions | AMD.

I suggest you download and install Microsoft Security Essentials. MSE offers better protection and runs more smoothly with Win 7 than Windows Defender. MSE supersedes Windows Defender and will turn Windows Defender off.

Once you have updated the driver and installed MSE, reboot and let's see how your system does. Post back and let us know. If you get another BSOD, we will go from there.