Blue Screen Error, Typically after logging into user account on system

I recently had a custom computer built for me:
Quad Core, Asus p5n-d mother board, 8gb DDR2, (originally had GeForce 6600 and GeForce 5200 cards, NZXT case w/ 400watt PSU installed. Windows Vista Home Premium 64bit.

A few weeks after getting my system, I started seeing Blue Screen errors typically after I would log into my user account. I have tried to reproduce this error by restarting...but sometimes it occurs and sometimes it does not. I have done lots of research on the error codes it was producing. One of the suggestions was video drivers/cards. Yesterday, I installed 2 Ge-Force 9600 GT cards to replace the old ones. I also upgraded my PSU to an 800 watt supply. After the install, I restarted about 4 times sucessfully without any Blue Screens, but... after the next restart... it happend again. I am guessing I can exlude video card from the list of problems. Further getting frustrated, I looked for another solution. I found something about checking the MEMORY.DMP that is produced during the error. I downloaded WinDbg and the symbols. I am not a newbie to computer, but when it comes to errors like this, I am completely lost! I have attached a copy of the Bugcheck Analysis to see if anyone has any other ideas of what could be causing this annoying problem!

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


Loading Dump File [C:\Users\Steve\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18000.amd64fre.longhorn_rtm.080118-1840
Kernel base = 0xfffff800`01a1b000 PsLoadedModuleList = 0xfffff800`01be0db0
Debug session time: Fri May  9 04:28:04.702 2008 (GMT-4)
System Uptime: 0 days 4:20:57.324
Loading Kernel Symbols
...........................................Unable to read NT module Base Name string at 00200065`006c0070 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
.Unable to read KLDR_DATA_TABLE_ENTRY at 00770074`00200074 - NTSTATUS 0xC0000141

Loading unloaded module list
..................................................
Page 6540000 too large to be in the dump file.
WARNING: .reload failed, module list may be incomplete
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff6da6b1b8610, 2, 0, fffff80001a95d84}

Unable to read NT module Base Name string at 00200065`006c0070 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00770074`00200074 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at 00200065`006c0070 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00770074`00200074 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Probably caused by : memory_corruption ( nt!MiDispatchFault+244 )

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: fffff6da6b1b8610, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80001a95d84, address which referenced memory

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

Unable to read NT module Base Name string at 00200065`006c0070 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00770074`00200074 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at 00200065`006c0070 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00770074`00200074 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete

READ_ADDRESS:  fffff6da6b1b8610

CURRENT_IRQL:  2

FAULTING_IP:
nt!MiDispatchFault+244
fffff800`01a95d84 f6450001        test    byte ptr [rbp],1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80001a70390

STACK_TEXT:  
fffffa60`01bbf5f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
nt!MiDispatchFault+244
fffff800`01a95d84 f6450001        test    byte ptr [rbp],1

SYMBOL_NAME:  nt!MiDispatchFault+244

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  479192b7

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiDispatchFault+244

BUCKET_ID:  X64_0xA_nt!MiDispatchFault+244

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

0: kd> lmvm nt
start             end                 module name
fffff800`01a1b000 fffff800`01f33000   nt         (pdb symbols)          C:\Windows\Symbols\exe\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Sat Jan 19 01:03:35 2008 (479192B7)
    CheckSum:         00485FC7
    ImageSize:        00518000
    File version:     6.0.6001.18000
    Product version:  6.0.6001.18000
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.0.6001.18000
    FileVersion:      6.0.6001.18000 (longhorn_rtm.080118-1840)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.



Start Free Trial