Bsod

[doubledragon5]

Been having some BSOD lately, so I downloade the windebugger tool, can someone tell me what exactly from all this that I need to be concerned with.. I have had different ones, but I wanted to post this one to see what piece of hard ware or software I having trouble with.. Thanks and sorry for the long post of information..


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


Loading Dump File [C:\Windows\Minidump\123010-19453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\Symbols*Symbol information


Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02858000 PsLoadedModuleList = 0xfffff800`02a95e50
Debug session time: Thu Dec 30 07:04:59.498 2010 (UTC - 6:00)
System Uptime: 0 days 0:13:09.013
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa801621c010, 2, 1, fffff80002986ab7}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+87 )

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: fffffa801621c010, 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: fffff80002986ab7, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b000e0
fffffa801621c010

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiReleaseConfirmedPageFileSpace+87
fffff800`02986ab7 480fb328 btr qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: SearchProtocol

TRAP_FRAME: fffff880081e45a0 -- (.trap 0xfffff880081e45a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800621c010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002986ab7 rsp=fffff880081e4730 rbp=0000000080000000
r8=fffff880081e4760 r9=fffffa800400eb30 r10=0000000fffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x87:
fffff800`02986ab7 480fb328 btr qword ptr [rax],rbp ds:fffffa80`0621c010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800028c7ca9 to fffff800028c8740

STACK_TEXT:
fffff880`081e4458 fffff800`028c7ca9 : 00000000`0000000a fffffa80`1621c010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`081e4460 fffff800`028c6920 : 00000000`01ffbf98 fffffa80`04564060 fffff683`ff7f3450 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`081e45a0 fffff800`02986ab7 : 000007fe`fe2db000 fffffa80`04564060 fffffa80`051726b0 00000000`770c0000 : nt!KiPageFault+0x260
fffff880`081e4730 fffff800`0293be38 : 80000000`00000000 000007fe`fe5ff000 00000000`01ffbf98 000007fe`fe68a000 : nt!MiReleaseConfirmedPageFileSpace+0x87
fffff880`081e47b0 fffff800`028fbdf9 : fffffa80`00000000 000007fe`ff355fff 00000000`00000000 fffff800`02a57888 : nt! ?? ::FNODOBFM::`string'+0x33798
fffff880`081e4970 fffff800`0289b81c : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`081e4a90 fffff800`02baddcf : fffff8a0`031f8a50 00000000`00000001 00000000`00000000 fffffa80`04564060 : nt!MmCleanProcessAddressSpace+0x228
fffff880`081e4ae0 fffff800`02b8585b : 00000000`00000000 00000000`00000001 000007ff`fffdc000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`081e4ba0 fffff800`028c7993 : fffffa80`0400eb30 000007fe`00000000 00000000`00303f01 fffffa80`04564060 : nt!NtTerminateProcess+0x25b
fffff880`081e4c20 00000000`7732001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0021fcd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7732001a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiReleaseConfirmedPageFileSpace+87
fffff800`02986ab7 480fb328 btr qword ptr [rax],rbp

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiReleaseConfirmedPageFileSpace+87

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87

BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87

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

0: kd> lmvm nt
start end module name
fffff800`02858000 fffff800`02e34000 nt (pdb symbols) c:\symbols\ntkrnlmp.pdb\30092BE745B24FE2A311A936E7B7486F2\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: c:\symbols\ntoskrnl.exe\4C1C44A95dc000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Fri Jun 18 23:16:41 2010 (4C1C44A9)
CheckSum: 005489D7
ImageSize: 005DC000
File version: 6.1.7600.16617
Product version: 6.1.7600.16617
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.1.7600.16617
FileVersion: 6.1.7600.16617 (win7_gdr.100618-1621)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
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: fffffa801621c010, 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: fffff80002986ab7, address which referenced memory

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


WRITE_ADDRESS: fffffa801621c010

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiReleaseConfirmedPageFileSpace+87
fffff800`02986ab7 480fb328 btr qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: SearchProtocol

TRAP_FRAME: fffff880081e45a0 -- (.trap 0xfffff880081e45a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800621c010 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002986ab7 rsp=fffff880081e4730 rbp=0000000080000000
r8=fffff880081e4760 r9=fffffa800400eb30 r10=0000000fffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x87:
fffff800`02986ab7 480fb328 btr qword ptr [rax],rbp ds:fffffa80`0621c010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800028c7ca9 to fffff800028c8740

STACK_TEXT:
fffff880`081e4458 fffff800`028c7ca9 : 00000000`0000000a fffffa80`1621c010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`081e4460 fffff800`028c6920 : 00000000`01ffbf98 fffffa80`04564060 fffff683`ff7f3450 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`081e45a0 fffff800`02986ab7 : 000007fe`fe2db000 fffffa80`04564060 fffffa80`051726b0 00000000`770c0000 : nt!KiPageFault+0x260
fffff880`081e4730 fffff800`0293be38 : 80000000`00000000 000007fe`fe5ff000 00000000`01ffbf98 000007fe`fe68a000 : nt!MiReleaseConfirmedPageFileSpace+0x87
fffff880`081e47b0 fffff800`028fbdf9 : fffffa80`00000000 000007fe`ff355fff 00000000`00000000 fffff800`02a57888 : nt! ?? ::FNODOBFM::`string'+0x33798
fffff880`081e4970 fffff800`0289b81c : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`081e4a90 fffff800`02baddcf : fffff8a0`031f8a50 00000000`00000001 00000000`00000000 fffffa80`04564060 : nt!MmCleanProcessAddressSpace+0x228
fffff880`081e4ae0 fffff800`02b8585b : 00000000`00000000 00000000`00000001 000007ff`fffdc000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`081e4ba0 fffff800`028c7993 : fffffa80`0400eb30 000007fe`00000000 00000000`00303f01 fffffa80`04564060 : nt!NtTerminateProcess+0x25b
fffff880`081e4c20 00000000`7732001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0021fcd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7732001a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiReleaseConfirmedPageFileSpace+87
fffff800`02986ab7 480fb328 btr qword ptr [rax],rbp

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiReleaseConfirmedPageFileSpace+87

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87

BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87

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

[glc]

Have you run memory and hard drive diagnostics yet? Have you updated all your drivers?

[doubledragon5]

All drivers are updated, I haven't ran the other two yet.. I will tomorrow after I return from work. So I will let you know tomorrow thanks glc.

[doubledragon5]

Ran test on ram, and hd both passed.. I will post another one of these that I have, it will be differnet maybe you can tell what that might mean as well..

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


Loading Dump File [C:\Windows\Minidump\122010-21406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\Symbols*Symbol information


Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02807000 PsLoadedModuleList = 0xfffff800`02a44e50
Debug session time: Mon Dec 20 15:46:11.529 2010 (UTC - 6:00)
System Uptime: 0 days 2:34:09.044
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800870a360, 2, 0, fffff88005933fc0}

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

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8800870a360, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88005933fc0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aaf0e0
fffff8800870a360

CURRENT_IRQL: 2

FAULTING_IP:
nvmcp64+80fc0
fffff880`05933fc0 410fbf00 movsx eax,word ptr [r8]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: iexplore.exe

TRAP_FRAME: fffff88002f22ae0 -- (.trap 0xfffff88002f22ae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000f3 rbx=0000000000000000 rcx=000000000000003c
rdx=000000000000003d rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005933fc0 rsp=fffff88002f22c70 rbp=00000000000001e6
r8=fffff8800870a360 r9=fffffa80062c9a90 r10=0000000000000002
r11=000000000000000f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nvmcp64+0x80fc0:
fffff880`05933fc0 410fbf00 movsx eax,word ptr [r8] ds:8c30:fffff880`0870a360=????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002876ca9 to fffff80002877740

STACK_TEXT:
fffff880`02f22998 fffff800`02876ca9 : 00000000`0000000a fffff880`0870a360 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f229a0 fffff800`02875920 : fffffa80`072fcbc8 fffffa80`0629d000 fffffa80`040f5d10 fffff880`05604773 : nt!KiBugCheckDispatch+0x69
fffff880`02f22ae0 fffff880`05933fc0 : 00000000`00000000 fffff880`05936333 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02f22c70 00000000`00000000 : fffff880`05936333 00000000`00000000 00000000`00000000 00000000`00000013 : nvmcp64+0x80fc0


STACK_COMMAND: kb

FOLLOWUP_IP:
nvmcp64+80fc0
fffff880`05933fc0 410fbf00 movsx eax,word ptr [r8]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nvmcp64+80fc0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvmcp64

IMAGE_NAME: nvmcp64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 42e643af

FAILURE_BUCKET_ID: X64_0xD1_nvmcp64+80fc0

BUCKET_ID: X64_0xD1_nvmcp64+80fc0

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

[glc]

You have a video driver problem. The clue is nvmcp64.sys.

[doubledragon5]

Thanks glc, I will see if they are indeed updated. I thought they were, but will see if Nvidia has any newer ones..

[Panama Red]

Originally Posted by doubledragon5 Thanks glc, I will see if they are indeed updated. I thought they were, but will see if Nvidia has any newer ones..

Just don't use the drivers from Windows Update. I've had consistent issues with video drivers from WU - both ATI & Nvidia.

[doubledragon5]

Originally Posted by Panama Red Just don't use the drivers from Windows Update. I've had consistent issues with video drivers from WU - both ATI & Nvidia.

Red I used the drivers from nvidia, just like I did after my first install.. Also looked to see if any were available for the MB, but none.

[Nuclear Krusader]

Uninstall the drivers. Then delete that file so that Windows won't automatically install it the next time you boot. Then proceed to manually install the newest drivers from nVidia.

[doubledragon5]

So now my computer doesn't shut down properly it just hangs.. I rand memtest86 yesterday and their did not find any errors. So today I ran the windows memory diagnostic test, and it says there is a memory problem.. So do I just call Corsair, or what? I have had these 4 1gig sticks one pair of 4 yrs, and the other two for about 2yrs..

[glc]

Corsair ram has a lifetime warranty. Determine which module or modules are bad and contact them for a RMA. If you bought dual channel kits, both modules must go back.

[Nuclear Krusader]

What about a nuke and pave? Or maybe you have a spare HDD you can install Windows onto just for testing? I had a machine last December that sometimes failed memory tests and it ended up being a corrupt Windows installation.

[doubledragon5]

Nuke I could try that as well.. First I going to test each set in pairs.. I will have to do all that my next days off, which won't be until 24th my b-day of all days. One thing I did notice in memtest 86 it shows the voltage as 2.60 there suppose to be 2.75. And the timings as 3-3-3-7 they are suppose to be 2-3-3-6. Now I do not know if that means anything, but I have not changed settings at all set installing this board..

[Nuclear Krusader]

Hmm, go into the BIOS setup and check the voltages. Don't change anything, just take note of what their values are. Boot and see if you can use Asusprobe or some probing software to find out what your voltage values are reported under Windows.

I remember that when I built my current workstation everything was working fine, but starting a 3D game would bring up all kinds of weird colours and artifacts on the screen and I had to reboot a lo bruto. I even opened a ticket to RMA the video card but then decided to run Asus Probe and found out that some voltages were out of whack (and those were the Asus defaults!! The video card had nothing to do with it); setting them to their right values solved the problem and the machine has performed flawlessly ever since.

After this probing you can then go into the BIOS again and manually set the voltages to their right values and reboot. See if the problem goes away. If it comes back, check the voltages again. If they're out of whack again, then either some SW is changing them somehow, or you have an ailing mobo.

[glc]

If the ram is rated for 2.75, manually set the ram voltage to 2.75 and leave everything else in auto.

[doubledragon5]

I called Corsair today, this is what they told me about the voltage and timings.. He said the timing should be between 2.60-2.75, and the timings reading they way they are because I'm running 2gig pairs 4 gig total ????? But I will do as suggested and run a probing software, and see what it says...

[doubledragon5]

Ok I down loaded SiS Sandra, it reports memory fine, but it reports my cpu like this.

Warning 235: Vcore less than rated minimum. In bios this is what I found

CPu Core Voltage 1.35v
LDT Bus Voltage 1.22v
Chip Set Voltage 1.54v
Dram 2,5Voltage 2.80v

So are these right? CPU is AMD Athlon 64X2 4800+

[glc]

1.35 Vcore is correct. Your dram voltage is too high though.

[doubledragon5]

What should it be glc, so I can change it..

[Devastator]

Originally Posted by glc If the ram is rated for 2.75, manually set the ram voltage to 2.75 and leave everything else in auto.

Set it to 2.75 as above.

[doubledragon5]

Problem found.. First called Corsair, their tech support had me manually set ram settings. CAS 2 5-3-3-7 Dram V 2.80. Then after running each stick individually the fourth one failed during the sixth test.. Now will call them tomorrow, and get RMA and send back two..