Multiple BSOD

[the dirt knot]

Hello,

After numerous crashes I am starting to regret building my own pc. The pc was running smoothly after installing windows. Ran Prime95 with no problems. Was about to try and run memtest86 when problems arose. I have been experiencing multiple crashes upon start up right after logging on. This is a clean install of win 7 64 bit. The computer was just built over the last week. I appreciate any help you can provide.

Thanks,
Brad

 

[the dirt knot]

Anybody???

 

[nickle]

This looks like a hard drive problem. Run a hard drive diagnostic from the manufacturer of the hard drive. Burn the diagnostic to a bootable cd since your computer will not start.

Also if you can , do a memtest86+ since a few of the dumps show a memory management error (1a).

If you can get to an administrative command prompt try running chkdsk /r.

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


Loading Dump File [C:\Users\Nickle\AppData\Local\Temp\Rar$DI00.837\032210-30342-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03049e50
Debug session time: Mon Mar 22 19:03:53.761 2010 (GMT-4)
System Uptime: 0 days 0:00:40.165
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88006810f08, fffff88006810760, fffff8800124b9e6}

Probably caused by : Ntfs.sys ( Ntfs!NtfsNonCachedIo+bc4 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88006810f08
Arg3: fffff88006810760
Arg4: fffff8800124b9e6

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


EXCEPTION_RECORD:  fffff88006810f08 -- (.exr 0xfffff88006810f08)
ExceptionAddress: fffff8800124b9e6 (Ntfs!NtfsNonCachedIo+0x0000000000000bc4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000080000000000
Attempt to read from address 0000080000000000

CONTEXT:  fffff88006810760 -- (.cxr 0xfffff88006810760)
rax=fffff88006811440 rbx=0000080000000000 rcx=0000000000000002
rdx=0000000000000002 rsi=0000000000000000 rdi=fffffa8005530a70
rip=fffff8800124b9e6 rsp=fffff88006811140 rbp=fffff880068111e0
 r8=0000000000000001  r9=0000000000000200 r10=fffff88006271c36
r11=0000000000000000 r12=fffff88006811190 r13=fffff880068114e0
r14=0000000000000000 r15=fffffa80062bcc10
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
Ntfs!NtfsNonCachedIo+0xbc4:
fffff880`0124b9e6 488b3b          mov     rdi,qword ptr [rbx] ds:002b:00000800`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000080000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b40e0
 0000080000000000 

FOLLOWUP_IP: 
Ntfs!NtfsNonCachedIo+bc4
fffff880`0124b9e6 488b3b          mov     rdi,qword ptr [rbx]

FAULTING_IP: 
Ntfs!NtfsNonCachedIo+bc4
fffff880`0124b9e6 488b3b          mov     rdi,qword ptr [rbx]

BUGCHECK_STR:  0x24

TRAP_FRAME:  fffff88006811a20 -- (.trap 0xfffff88006811a20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff98003f94c00 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000034 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031815f1 rsp=fffff88006811bb0 rbp=0000000000000000
 r8=0000000000000012  r9=0000000000000000 r10=00000000fffffff9
r11=0000000000d14c00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!CcMapData+0x111:
fffff800`031815f1 0fb600          movzx   eax,byte ptr [rax] ds:fffff980`03f94c00=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8800124e526 to fffff8800124b9e6

STACK_TEXT:  
fffff880`06811140 fffff880`0124e526 : fffff880`068114e0 fffffa80`062bcc10 fffffa80`05530a70 fffff880`012db6ef : Ntfs!NtfsNonCachedIo+0xbc4
fffff880`06811310 fffff880`01250f78 : fffff880`068114e0 fffffa80`062bcc10 fffff880`06811601 fffffa80`054e7401 : Ntfs!NtfsCommonRead+0x7a6
fffff880`068114b0 fffff880`0105423f : fffffa80`062bcfb0 fffffa80`062bcc10 fffffa80`054e7440 00000800`00000000 : Ntfs!NtfsFsdRead+0x1b8
fffff880`068116b0 fffff880`010526df : fffffa80`05530200 fffffa80`062bcc10 fffffa80`05530200 fffffa80`062bcc10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`06811740 fffff800`02e6fa52 : fffffa80`062bcc30 fffffa80`05538230 00000000`00000043 fffff980`03f94c00 : fltmgr!FltpDispatch+0xcf
fffff880`068117a0 fffff800`02e6fd55 : 00000000`00100000 00000000`00100000 fffff880`06811860 fffff800`03170990 : nt!IoPageRead+0x252
fffff880`06811830 fffff800`02e98da4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff8a0`01e9c540 : nt!MiIssueHardFault+0x255
fffff880`068118c0 fffff800`02e7bfee : 00000000`00000000 00000000`0000000e fffffa80`062c0800 00000000`00000000 : nt!MmAccessFault+0x11c4
fffff880`06811a20 fffff800`031815f1 : 00000000`06d00000 00000000`06d14c00 fffff880`06811c78 fffff880`06811c70 : nt!KiPageFault+0x16e
fffff880`06811bb0 fffff880`012fc522 : fffff880`0002b400 fffffa80`039af010 fffff880`06812204 fffff8a0`0000000e : nt!CcMapData+0x111
fffff880`06811c70 fffff880`012f24dc : fffffa80`05a99e40 fffffa80`04da8180 fffff8a0`02042b48 00000000`00000801 : Ntfs!NtfsReadMftRecord+0xb2
fffff880`06811d20 fffff880`012c14aa : fffff8a0`02042b44 fffff8a0`02042b00 fffffa80`062bc010 00000000`00000000 : Ntfs!NtfsLookupInFileRecord+0x6c
fffff880`06811db0 fffff880`012c3df2 : fffffa80`05a99e40 fffff8a0`02042b44 fffffa80`05a99e40 fffff8a0`02042b40 : Ntfs!NtfsUpdateFcbInfoFromDisk+0xaa
fffff880`06811f00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsOpenFile+0x2c6


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsNonCachedIo+bc4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff88006810760 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsNonCachedIo+bc4

BUCKET_ID:  X64_0x24_Ntfs!NtfsNonCachedIo+bc4

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

 

[the dirt knot]

Nickle,

Thanks for taking a look. I'll try to complete these steps after work.

 

[the dirt knot]

Well, three passes with memtest86 discovered zero errors. Used Samsung es-tool checked hdd again no errors. I did notice however that upon logging into windows I now get a pop up that states there is some sort of error with dxgi.dll.

At this point could the board be the culprit?? Seems after the install the system ran fine, but once I tried installing USB network adapter all went wrong. Somebody stated that the had something similar to this on their newegg review of the board. I had this happen twice so far after two installs of windows. Also, I have tried different adapters with the same result.

I am thinking I should just rma it before my thirty days is up.

Suggestions?

 

[nickle]

A literal interpretation of your most current dump is as follows:

A page fault occured and ntfs.sys was called to read or write a page from/to the hard disk. Ntfs.sys was not able to perform the read/write operation and an exception (0x24) was generated.

A page fault occurs when the memory manager determines that an address has been accessed which is not in physical memory and must be fetched from virtual memory on the hard drive. Pages are 4k blocks of memory (virtual or physical).

The memory manager relied on ntfs.sys to fetch the virtual memory block which was unsuccessful.

This leads one to believe that either the hard drive has physical defects (bad blocks) which can not be read or the actual file system which exists on the drive is corrupted. In the latter case a chkdsk /r should be able to resolve the problem.

Make sure you have the most current bios for the motherboard installed.

If you are using a raid configuration get rid of it for the purposes of this debugging session.

All of your drivers look to be current, however you may try to run driver verifier anyway: http://support.microsoft.com/kb/244617 before exchanging hardware.

Upload any additional bsods that you may get.

Edit: Try disabling(uninstalling) any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system.

 

[the dirt knot]

OK, I updated the bios on my board and haven't had a BSOD since. I have shutdown/restarted several times without the BSOD.

I am however now getting these two popups upon logging into windows:

 

[the dirt knot]

Evidently I am not out of the woods. I turned on the computer this morning and was greeted with two different blue screens. I am really at a loss right now.

 

[nickle]

This dump after the bios was updated only reinforces the fact that a problem is occuring during the paging process involving ntfs.sys which is a Microsoft driver. See highlighted area in the code box.

I have looked at your motherboard manual and noticed a section(download center) which allows you to download the most current drivers available for your system. I would update your drivers from there if you have not already done so.

I also looked at the Gigabyte site and found a page for your motherboard. DOn't know if anything additional there. GA-MA785GMT-UD2H (rev. 1.1) - GIGABYTE - Support&Download - Motherboard - Driver. There are two revision numbers 1.0 and 1.1. Make sure you are downloading the right one. The chipset and Sata drivers are the most important because they are in play as regards the dump.

It may be a good idea to reinstall windows now that the bios is updated to the current version. Especially if you cannot get past the login.

Also to make sure your copy of windows is not corrupted run it the Windows 7 verifier from here: Windows 7 ISO Verifier, for your downloading pleasure – istartedsomething

Are you sure that the motherboard is compatible with Windows 7? Have you heard of others using it with Windows 7? Could be a problem with your particular configuration and Windows 7.

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


Loading Dump File [C:\Users\Nickle\AppData\Local\Temp\Rar$DI00.444\032510-26192-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`03051e50
Debug session time: Thu Mar 25 06:55:48.871 2010 (GMT-4)
System Uptime: 0 days 0:01:36.525
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88005dd36d8, fffff88005dd2f30, fffff880012530fd}

[COLOR=Blue]Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireFcbWithPaging+12d )[/COLOR]

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88005dd36d8
Arg3: fffff88005dd2f30
Arg4: fffff880012530fd

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


EXCEPTION_RECORD:  fffff88005dd36d8 -- (.exr 0xfffff88005dd36d8)
ExceptionAddress: fffff880012530fd (Ntfs!NtfsAcquireFcbWithPaging+0x000000000000012d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000058
Attempt to read from address 0000000000000058

CONTEXT:  fffff88005dd2f30 -- (.cxr 0xfffff88005dd2f30)
rax=fffffa80065f8b01 rbx=0000000000000009 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000008 rdi=fffffa8006630790
rip=fffff880012530fd rsp=fffff88005dd3910 rbp=0000000000000000
 r8=0000000000000702  r9=0000000000000008 r10=0000000000020000
r11=fffff88005dd3968 r12=fffff8a003e07b40 r13=00000000c00000d8
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010283
Ntfs!NtfsAcquireFcbWithPaging+0x12d:
fffff880`012530fd 488b4958        mov     rcx,qword ptr [rcx+58h] ds:002b:00000000`00000058=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000058

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc0e0
 0000000000000058 

FOLLOWUP_IP: 
Ntfs!NtfsAcquireFcbWithPaging+12d
fffff880`012530fd 488b4958        mov     rcx,qword ptr [rcx+58h]

FAULTING_IP: 
Ntfs!NtfsAcquireFcbWithPaging+12d
fffff880`012530fd 488b4958        mov     rcx,qword ptr [rcx+58h]

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff880012c761d to fffff880012530fd

STACK_TEXT:  
fffff880`05dd3910 fffff880`012c761d : 00000000`00000000 fffffa80`04ee5010 fffffa80`06630790 00040000`00023201 : Ntfs!NtfsAcquireFcbWithPaging+0x12d
fffff880`05dd3970 fffff880`012eab04 : fffff880`03148490 fffffa80`04ee5010 fffffa80`06630790 00000000`00000000 : Ntfs!NtfsOpenFile+0xaf1
fffff880`05dd3b50 fffff880`01253c0d : fffffa80`06630790 fffffa80`04ee5010 fffff880`03148490 fffffa80`065f8b00 : Ntfs!NtfsCommonCreate+0xc54
fffff880`05dd3d30 fffff800`02e7dd87 : fffff880`03148400 00000000`00000000 00000000`00000000 fffff800`02e64486 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`05dd3d60 fffff800`02e7dd41 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`031482d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsAcquireFcbWithPaging+12d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff88005dd2f30 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireFcbWithPaging+12d

BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireFcbWithPaging+12d

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

 

[the dirt knot]

Nickle,
I am nearly 100% certain the board is compatible with win 7. Since most of your helpful input has pointed to this being a hard drive issue I decided to head out and buy a new drive. I installed windows again and so far I have been trouble free. I don't want to get excited just yet, so I will continue to monitor the situation. At any rate thanks so much for all your help. I really appreciated it.

Brad

 

[the dirt knot]

Well it's at it again. I have been experiencing more BSOD fun. I have
tried chkdsk/r and found no errors. I disabled microsoft security
essentials and ran smooth for awhile and then the BSOD started again.
I really haven't installed much if anything in fear of having to
install windows again. I have uploaded the latest dump for review.
Also, The BSOD has occurred while starting windows normally as well as
booting in safe mode. It's a real toss up. Sometimes it works
sometimes it doesn't

 

[the dirt knot]

Wondering if anybody had a chance to look at this yet. In the meantime I have read from other sources that people have been having some issues with this board. Thinking contacting gigabyte may be the best option.

 

[Jonathan_King]

I suggest running a system files check.

Also, you should probably run Memtest for at least 5 passes, more if you have a lot of RAM.

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


Loading Dump File [C:\Users\Jonathan\Desktop\033110-18657-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`0309de50
Debug session time: Wed Mar 31 05:48:37.055 2010 (GMT-4)
System Uptime: 0 days 0:00:35.709
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff781c0000000, 6290, 6a8ffffffffe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29fc2 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005002, The subtype of the bugcheck.
Arg2: fffff781c0000000
Arg3: 0000000000006290
Arg4: 00006a8ffffffffe

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


BUGCHECK_STR:  0x1a_5002

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  lsm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880024be720 -- (.trap 0xfffff880024be720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0030ce000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030046fb rsp=fffff880024be8b0 rbp=fffffa800395a140
 r8=0000000000000000  r9=0000000000004a3a r10=0000000000000000
r11=fffff880024be880 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ExAllocatePoolWithTag+0x32b:
fffff800`030046fb 448928          mov     dword ptr [rax],r13d ds:fffff8a0`030ce000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f419f3 to fffff80002ed1f00

STACK_TEXT:  
fffff880`024be3b8 fffff800`02f419f3 : 00000000`0000001a 00000000`00005002 fffff781`c0000000 00000000`00006290 : nt!KeBugCheckEx
fffff880`024be3c0 fffff800`02eee482 : 00000000`00000001 fffff8a0`030ce000 fffff880`024be720 fffff6fc`50018670 : nt! ?? ::FNODOBFM::`string'+0x29fc2
fffff880`024be4b0 fffff800`02eec4d1 : 00000000`00000001 fffff800`031c7dbc fffffa80`0628c730 00000000`00000001 : nt!MiDispatchFault+0x8c2
fffff880`024be5c0 fffff800`02ecffee : 00000000`00000001 fffffa80`0395b280 00000000`e56b6f00 00000000`00000002 : nt!MmAccessFault+0x8f1
fffff880`024be720 fffff800`030046fb : fffffa80`0395b280 00000000`00001000 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`024be8b0 fffff800`031c8034 : 00000000`00000001 fffffa80`03967f30 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x32b
fffff880`024be9a0 fffff800`031cae9b : 00000000`00000001 fffffa80`03a18201 00000000`000002c4 fffff880`024bea38 : nt!ObpAllocateObject+0xc4
fffff880`024bea00 fffff800`031a3994 : 00000000`00c6ee70 00000000`00000002 fffff8a0`019f8e80 fffff8a0`02848060 : nt!ObCreateObject+0xdb
fffff880`024bea70 fffff800`031782bf : 00000000`02000000 00000000`00c6ef00 00000000`00000000 00000000`00000001 : nt!SepDuplicateToken+0xf4
fffff880`024beb10 fffff800`02ed1153 : fffffa80`062bf760 00000000`00c6ee48 fffff880`024bebc8 00000000`ff146301 : nt!NtDuplicateToken+0x147
fffff880`024bebb0 00000000`76ea02da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c6ee28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ea02da


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+29fc2
fffff800`02f419f3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+29fc2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+29fc2

BUCKET_ID:  X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+29fc2

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

 

[the dirt knot]

Thanks for the reply Jonathan. I ran memtest overnight for 9 passes and found no errors. I will try the system file check now and post back with any results. Thanks again.

 

[the dirt knot]

System file check didn't find any issues. I posted over at the gigabyte forums and was told to boost my ram voltage and to disable my integrated graphics. This worked fine all day Monday. Yesterday after work though I was greeted with a referenced memory not found pop-up upon logging into windows. Despite this windows ran for about 20-30 minutes then I was greeted with a memory management bsod. I didn't have the patience to restart and get the minidump. I'll do so tonite after work.