bsod minidump

[ttran]

BSODs (worst nightmare if stay unsolved) :devil2:
WISH YOU LUCK TOo

Best regard
Group of Bsods victims

 

[CarlTR6]

Here's hoping your problem is solved.

 

[bobmane]

update

actions taken:

a few days ago installed fresh W7 and got BSOB (dump attached)

decided to go over to mac side to rule out windows issues

installed fresh most current os x > consistent screen freezes

did all major troubleshooting tasks and re-seated RAM (details here: Unexplained Crashes and Screen locks - macosx.com'

now I will see how it goes in os x for the next day. hopefully I can resolve and get back to W7 full time (i happen to prefer the usability)

 

[CarlTR6]

This dump shows stop error code 50.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

The bug check does not point to anything specific.

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp2_dump.zip\070510-32604-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL]http://msdl.microsoft.com/download/symbols[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e50
Debug session time: Mon Jun 14 16:29:19.583 2010 (GMT-4)
System Uptime: 0 days 0:09:43.394
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff30015ba7010, 1, fffff80002adb130, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40edb )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff30015ba7010, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002adb130, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0f0e0
 fffff30015ba7010 

FAULTING_IP: 
nt!memset+b0
fffff800`02adb130 480fc311        movnti  qword ptr [rcx],rdx

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008ec6550 -- (.trap 0xfffff88008ec6550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff30015ba7010 rbx=0000000000000000 rcx=fffff30015ba7010
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002adb130 rsp=fffff88008ec66e8 rbp=0000000000000001
 r8=0000000000000030  r9=00000015ffd001bf r10=ffffffffffffffff
r11=0000000000000040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!memset+0xb0:
fffff800`02adb130 480fc311        movnti  qword ptr [rcx],rdx ds:0001:fffff300`15ba7010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b56b19 to fffff80002ad8f00

STACK_TEXT:  
fffff880`08ec63e8 fffff800`02b56b19 : 00000000`00000050 fffff300`15ba7010 00000000`00000001 fffff880`08ec6550 : nt!KeBugCheckEx
fffff880`08ec63f0 fffff800`02ad6fee : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`010e523f : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`08ec6550 fffff800`02adb130 : fffff800`02e35a73 00000000`00000000 00000000`00009bad 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`08ec66e8 fffff800`02e35a73 : 00000000`00000000 00000000`00009bad 00000000`00000000 00000000`00000000 : nt!memset+0xb0
fffff880`08ec66f0 fffff800`02dd1555 : fffffa80`0bccb2a0 00000000`00000000 00000000`00000002 fffff880`08ec69a0 : nt! ?? ::NNGAKEGL::`string'+0x5023a
fffff880`08ec6920 fffff800`02dc6893 : fffff880`08ec6b80 00000000`00000000 00000000`00000000 fffff880`08ec6b78 : nt!MmCreateSection+0x7a9
fffff880`08ec6b30 fffff800`02ad8153 : fffffa80`0ebf7760 00000000`0519e108 fffff880`08ec6bc8 00000000`0519e3b8 : nt!NtCreateSection+0x162
fffff880`08ec6bb0 00000000`7762035a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0519e0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7762035a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+40edb
fffff800`02b56b19 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+40edb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40edb

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40edb

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

It appears that you have a definite hardware or hardware related problem(s). I suggest that you follow Rich's advice and go down the list in this thread:

[2-Int] Stop 0x124 - what it means and what to try

You are going to have to do some serious troubleshooting.

 

[bobmane]

this issue was solved by re-seating my RAM...thanks for all the help!

 

[CarlTR6]

Very good. I am glad you found a relatively simple solution. Thank you for posting your solution. Happy computing.