New PC, First BSOD

Had this PC for a few days now, and just randomly received this BSOD this morning. Not sure what triggered it. I believe this is the correct file im attaching. If not please steer me in the right direction. Thanks for the help.

-DG

Deathgazer said:

Had this PC for a few days now, and just randomly received this BSOD this morning. Not sure what triggered it. I believe this is the correct file im attaching. If not please steer me in the right direction. Thanks for the help.

-DG

DG


Welcome

This crash was probably caused by your nvidea video driver.
I would un-install this version and download and install a freash copy.

Also run a system file check too verify and repair your system files
Type cmd in search>right click and run as admin>SFC /SCANNOW

If you are overclocking stop

Let us know if you need help with this



Ken

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\022210-19796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
Debug session time: Mon Feb 22 07:34:10.111 2010 (GMT-5)
System Uptime: 1 days 9:30:10.219
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D0, {fffffa80200ca78b, 2, 0, fffff80002bb1bcb}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+19bf48 )

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

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

DRIVER_CORRUPTED_MMPOOL (d0)
Arguments:
Arg1: fffffa80200ca78b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002bb1bcb, address which referenced memory
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is
    caused by drivers that have corrupted the system pool.  Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.  You can also set
    HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ProtectNonPagedPool
    to a DWORD 1 value and reboot.  Then the system will unmap freed nonpaged pool,
    preventing drivers (although not DMA-hardware) from corrupting the pool.

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb80e0
 fffffa80200ca78b 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiAllocatePoolPages+7c2
fffff800`02bb1bcb f6471b10        test    byte ptr [rdi+1Bh],10h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD0

PROCESS_NAME:  System

TRAP_FRAME:  fffff880030cafa0 -- (.trap 0xfffff880030cafa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000200ca770
rdx=000000000557713d rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002bb1bcb rsp=fffff880030cb130 rbp=fffff880030cb180
 r8=0000000000003200  r9=fffff6fd4009f798 r10=0000000000000000
r11=fffff6fb7ea004f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiAllocatePoolPages+0x7c2:
fffff800`02bb1bcb f6471b10        test    byte ptr [rdi+1Bh],10h ds:00000000`0000001b=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a81469 to fffff80002a81f00

STACK_TEXT:  
fffff880`030cae58 fffff800`02a81469 : 00000000`0000000a fffffa80`200ca78b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`030cae60 fffff800`02a800e0 : 00000000`2c4ad963 00000000`04388963 fffffa80`0084de60 00000000`0002c4a2 : nt!KiBugCheckDispatch+0x69
fffff880`030cafa0 fffff800`02bb1bcb : 2aaaaaaa`aaaaaaab fffff880`030cb180 00000000`0000601b fffffa80`0087b1f0 : nt!KiPageFault+0x260
fffff880`030cb130 fffff800`02a94860 : 00000000`0601b000 fffff800`02c0f880 00000000`00000000 fffffa80`03cffd70 : nt!MiAllocatePoolPages+0x7c2
fffff880`030cb280 fffff800`02bb4bfe : 00000000`00000000 fffff800`02bb44d3 00000000`00000000 fffff800`02c0f880 : nt!ExpAllocateBigPool+0xb0
fffff880`030cb370 fffff880`0ffe2f48 : 00000000`00000000 fffffa80`0601a7d0 00000000`00000000 00000000`000007ff : nt!ExAllocatePoolWithTag+0x82e
fffff880`030cb460 00000000`00000000 : fffffa80`0601a7d0 00000000`00000000 00000000`000007ff 00000000`00000000 : nvlddmkm+0x19bf48


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+19bf48
fffff880`0ffe2f48 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  nvlddmkm+19bf48

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4c080b

FAILURE_BUCKET_ID:  X64_0xD0_nvlddmkm+19bf48

BUCKET_ID:  X64_0xD0_nvlddmkm+19bf48

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

In the event viewer it also has:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041790, 0xfffffa80006cbcd0, 0x000000000000ffff, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030410-21216-01.

Although that .dmp file is 458 MB (70 .rar'd)

Been getting more BSOD, here's an updated .rar. If you need any more info just let me know.

Deathgazer said:

Been getting more BSOD, here's an updated .rar. If you need any more info just let me know.

Code:

030410-19843-01.dmp    3/4/2010 8:43:57 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff8a0`28b40c48    00000000`00000001    fffff880`10b58986    00000000`00000002    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
030410-27222-01.dmp    3/4/2010 8:29:53 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff8a0`1701b140    00000000`00000000    fffff880`0421d586    00000000`00000002    dxgmms1.sys    dxgmms1.sys+1011b        x64    
030310-18501-01.dmp    3/3/2010 9:29:35 PM    NO_MORE_IRP_STACK_LOCATIONS    0x00000035    fffffa80`04804ca0    00000000`00000000    00000000`00000000    00000000`00000000    win32k.sys    win32k.sys+8555        x64    
030410-21216-01.dmp    3/4/2010 9:24:13 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`006cbcd0    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
022710-21621-01.dmp    2/27/2010 10:11:00 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    fffffa86`00703808    00000000`00000002    00000000`00000001    fffff800`02ce2b74    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
030510-20623-01.dmp    3/5/2010 6:36:10 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    00000000`20000000    00000000`00000002    00000000`00000000    fffff800`02ce0921    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
022210-19796-01.dmp    2/22/2010 6:35:47 AM    DRIVER_CORRUPTED_MMPOOL    0x000000d0    fffffa80`200ca78b    00000000`00000002    00000000`00000000    fffff800`02bb1bcb    ntoskrnl.exe    ntoskrnl.exe+71f00        x64    
022610-20264-01.dmp    2/26/2010 1:20:05 PM    BAD_POOL_HEADER    0x00000019    00000000`00000003    fffffa80`03c5f6c0    00000000`00000001    fffffa80`01c5f6c0    ntoskrnl.exe    ntoskrnl.exe+71f00        x64

hi there and welcome.

You have several different causes for these crashes. With this many causes one has to suspect hardware.

I would start by checking your ram. download memtestx86 and run it for 5 passes. this will take a really long time, but is necessary to check the ram and see if there is a heat issue.

If you are overclocking STOP

Let us know the results


Ken

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\New folder (3)\022710-21621-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c50000 PsLoadedModuleList = 0xfffff800`02e8de50
Debug session time: Sat Feb 27 23:09:13.796 2010 (GMT-5)
System Uptime: 1 days 8:49:33.904
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8600703808, 2, 1, fffff80002ce2b74}

Probably caused by : win32k.sys ( win32k!memset+b0 )

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

6: 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: fffffa8600703808, 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: fffff80002ce2b74, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef80e0
 fffffa8600703808 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiUnlinkFreeOrZeroedPage+1ca
fffff800`02ce2b74 48893cc2        mov     qword ptr [rdx+rax*8],rdi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff88009730ee0 -- (.trap 0xfffff88009730ee0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c5e00000 rbx=0000000000000000 rcx=fffff900c619b000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000123ad0 rsp=fffff88009731078 rbp=0000000000000001
 r8=0000000000000028  r9=00000000000003a8 r10=000000000000007f
r11=0000000000000034 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
win32k!memset+0xb0:
fffff960`00123ad0 480fc311        movnti  qword ptr [rcx],rdx ds:0001:fffff900`c619b000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc1469 to fffff80002cc1f00

STACK_TEXT:  
fffff880`09730718 fffff800`02cc1469 : 00000000`0000000a fffffa86`00703808 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09730720 fffff800`02cc00e0 : 00000000`00000068 fffffa80`00d4e800 00000000`00000000 fffff880`097308d0 : nt!KiBugCheckDispatch+0x69
fffff880`09730860 fffff800`02ce2b74 : fffffa80`01f0c7d0 fffff800`02ce752e 00000000`00000000 fffff880`097309b8 : nt!KiPageFault+0x260
fffff880`097309f0 fffff800`02ce7818 : fffff880`09730ac0 00000000`00046f80 fffffa80`00d4e800 fffffa80`016de7d0 : nt!MiUnlinkFreeOrZeroedPage+0x1ca
fffff880`09730a60 fffff800`02cdfa97 : 00000000`00000002 fffff880`00000002 fffff880`02b65c00 00000000`00000000 : nt!MiRemoveAnyPage+0x1d8
fffff880`09730b80 fffff800`02cde482 : 00000000`00000001 fffff900`c619b000 fffff880`09730ee0 fffff6fc`80630cd8 : nt!MiResolveDemandZeroFault+0x577
fffff880`09730c70 fffff800`02cdc4d1 : 00000000`0008a752 00000000`00000000 00000000`00000000 fffff900`c1c55350 : nt!MiDispatchFault+0x8c2
fffff880`09730d80 fffff800`02cbffee : 00000000`00000001 fffff900`c5e00000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x8f1
fffff880`09730ee0 fffff960`00123ad0 : fffff960`00112902 fffff900`c06bebe0 00000000`00000000 fffff960`00256fb4 : nt!KiPageFault+0x16e
fffff880`09731078 fffff960`00112902 : fffff900`c06bebe0 00000000`00000000 fffff960`00256fb4 fffff960`001240d1 : win32k!memset+0xb0
fffff880`09731080 fffff960`00113e0f : 00000000`00000000 fffff880`09731220 00000000`00000001 fffff960`001114ee : win32k!AllocateObject+0xf2
fffff880`097310c0 fffff960`000eb48c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`097311b0 fffff960`000eb006 : 000002ee`00000500 00000000`000002ee 00000000`01080030 00000000`00000500 : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`09731280 fffff800`02cc1153 : fffffa80`07c6b5f0 fffff880`097313e0 00000000`00000000 fffff900`c00bf010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`09731360 00000000`75692dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0035ccf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75692dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!memset+b0
fffff960`00123ad0 480fc311        movnti  qword ptr [rcx],rdx

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  win32k!memset+b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

FAILURE_BUCKET_ID:  X64_0xA_win32k!memset+b0

BUCKET_ID:  X64_0xA_win32k!memset+b0

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

6: 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: fffffa8600703808, 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: fffff80002ce2b74, address which referenced memory

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


WRITE_ADDRESS:  fffffa8600703808 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiUnlinkFreeOrZeroedPage+1ca
fffff800`02ce2b74 48893cc2        mov     qword ptr [rdx+rax*8],rdi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff88009730ee0 -- (.trap 0xfffff88009730ee0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c5e00000 rbx=0000000000000000 rcx=fffff900c619b000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000123ad0 rsp=fffff88009731078 rbp=0000000000000001
 r8=0000000000000028  r9=00000000000003a8 r10=000000000000007f
r11=0000000000000034 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
win32k!memset+0xb0:
fffff960`00123ad0 480fc311        movnti  qword ptr [rcx],rdx ds:0001:fffff900`c619b000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc1469 to fffff80002cc1f00

STACK_TEXT:  
fffff880`09730718 fffff800`02cc1469 : 00000000`0000000a fffffa86`00703808 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09730720 fffff800`02cc00e0 : 00000000`00000068 fffffa80`00d4e800 00000000`00000000 fffff880`097308d0 : nt!KiBugCheckDispatch+0x69
fffff880`09730860 fffff800`02ce2b74 : fffffa80`01f0c7d0 fffff800`02ce752e 00000000`00000000 fffff880`097309b8 : nt!KiPageFault+0x260
fffff880`097309f0 fffff800`02ce7818 : fffff880`09730ac0 00000000`00046f80 fffffa80`00d4e800 fffffa80`016de7d0 : nt!MiUnlinkFreeOrZeroedPage+0x1ca
fffff880`09730a60 fffff800`02cdfa97 : 00000000`00000002 fffff880`00000002 fffff880`02b65c00 00000000`00000000 : nt!MiRemoveAnyPage+0x1d8
fffff880`09730b80 fffff800`02cde482 : 00000000`00000001 fffff900`c619b000 fffff880`09730ee0 fffff6fc`80630cd8 : nt!MiResolveDemandZeroFault+0x577
fffff880`09730c70 fffff800`02cdc4d1 : 00000000`0008a752 00000000`00000000 00000000`00000000 fffff900`c1c55350 : nt!MiDispatchFault+0x8c2
fffff880`09730d80 fffff800`02cbffee : 00000000`00000001 fffff900`c5e00000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x8f1
fffff880`09730ee0 fffff960`00123ad0 : fffff960`00112902 fffff900`c06bebe0 00000000`00000000 fffff960`00256fb4 : nt!KiPageFault+0x16e
fffff880`09731078 fffff960`00112902 : fffff900`c06bebe0 00000000`00000000 fffff960`00256fb4 fffff960`001240d1 : win32k!memset+0xb0
fffff880`09731080 fffff960`00113e0f : 00000000`00000000 fffff880`09731220 00000000`00000001 fffff960`001114ee : win32k!AllocateObject+0xf2
fffff880`097310c0 fffff960`000eb48c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`097311b0 fffff960`000eb006 : 000002ee`00000500 00000000`000002ee 00000000`01080030 00000000`00000500 : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`09731280 fffff800`02cc1153 : fffffa80`07c6b5f0 fffff880`097313e0 00000000`00000000 fffff900`c00bf010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`09731360 00000000`75692dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0035ccf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75692dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!memset+b0
fffff960`00123ad0 480fc311        movnti  qword ptr [rcx],rdx

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  win32k!memset+b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

FAILURE_BUCKET_ID:  X64_0xA_win32k!memset+b0

BUCKET_ID:  X64_0xA_win32k!memset+b0

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

[

Hey thanks again. I ran memtest for 9 passes and it came up with 20 errors .

Deathgazer said:

Hey thanks again. I ran memtest for 9 passes and it came up with 20 errors .

If you are inclined you can find which stick is at fault. Or just return them if they are in warranty.

Ken