Win 7 0x00000050

biasedgnosis · 29 Jun 2014

Win 7 will randomly decided that a BSOD is necessary every other boot up. It has also happened once in xbmc. It's usually pretty stable when it doesn't decide the bluescreen, normal, bluescreeen, normal, etc. Event viewer says its 0x00000050 with a bugcheck error code 1001

I have attached the zipfile from your program

please help

koolkat77 · 29 Jun 2014

Welcome to the forum biasedgnosis,

Perform a System File Check:

Click on the start
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it:

Disk Check

Code:

OS Name	Microsoft Windows 7 Ultimate
Version	6.1.7600 Build 7600

Install all windows updates including Service Pack One:

Learn how to install Windows 7 Service Pack 1 (SP1)

Make scans with the following:

Kaspersky TDSSKiller:

Anti-rootkit utility TDSSKiller

ESET online scanner:

Free Online Virus Scanner | ESET

Code:

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


Loading Dump File [C:\Users\admin\Downloads\SF_29-06-2014\SF_29-06-2014\062914-50045-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 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`01810000 PsLoadedModuleList = 0xfffff800`01a4de50
Debug session time: Mon Jun 30 00:05:36.563 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:48.282
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffffa800823, 1, fffffa800823aaf0, 2}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+5a0b7e )

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

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: fffffffffa800823, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffffa800823aaf0, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001ab80e0
GetUlongFromAddress: unable to read from fffff80001ab8198
 fffffffffa800823 

FAULTING_IP: 
+0
fffffa80`0823aaf0 00ab230880fa    add     byte ptr [rbx-57FF7DDh],ch

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88001d69990 -- (.trap 0xfffff88001d69990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88001d69bb4 rbx=0000000000000000 rcx=fffffa80077dd2a0
rdx=fffffa800823c010 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa800823aaf0 rsp=fffff88001d69b28 rbp=fffff88001d69bb0
 r8=fffff88001d69b88  r9=fffff88001d69bb0 r10=fffffa80073ca430
r11=fffffa800613e738 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
fffffa80`0823aaf0 00ab230880fa    add     byte ptr [rbx-57FF7DDh],ch ds:ffffffff`fa800823=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800018ffbc2 to fffff80001881f00

STACK_TEXT:  
fffff880`01d69828 fffff800`018ffbc2 : 00000000`00000050 ffffffff`fa800823 00000000`00000001 fffff880`01d69990 : nt!KeBugCheckEx
fffff880`01d69830 fffff800`0187ffee : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f90
fffff880`01d69990 fffffa80`0823aaf0 : fffff880`03003b7e 00000000`00000001 fffff880`02bab987 fffffa80`077dd2a0 : nt!KiPageFault+0x16e
fffff880`01d69b28 fffff880`03003b7e : 00000000`00000001 fffff880`02bab987 fffffa80`077dd2a0 fffffa80`073ba3a0 : 0xfffffa80`0823aaf0
fffff880`01d69b30 00000000`00000001 : fffff880`02bab987 fffffa80`077dd2a0 fffffa80`073ba3a0 00000000`00000000 : nvlddmkm+0x5a0b7e
fffff880`01d69b38 fffff880`02bab987 : fffffa80`077dd2a0 fffffa80`073ba3a0 00000000`00000000 fffffa80`077dd2a0 : 0x1
fffff880`01d69b40 fffffa80`077dd2a0 : fffffa80`073ba3a0 00000000`00000000 fffffa80`077dd2a0 fffffa80`080b2840 : nvlddmkm+0x148987
fffff880`01d69b48 fffffa80`073ba3a0 : 00000000`00000000 fffffa80`077dd2a0 fffffa80`080b2840 fffffa80`073ca430 : 0xfffffa80`077dd2a0
fffff880`01d69b50 00000000`00000000 : fffffa80`077dd2a0 fffffa80`080b2840 fffffa80`073ca430 fffffa80`073ca430 : 0xfffffa80`073ba3a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+5a0b7e
fffff880`03003b7e ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+5a0b7e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0c8387

FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+5a0b7e

BUCKET_ID:  X64_0x50_nvlddmkm+5a0b7e

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

kd> lmvm nvlddmkm
start             end                 module name
fffff880`02a63000 fffff880`0356ab00   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri May 15 02:48:07 2009 (4A0C8387)
    CheckSum:         00B1940A
    ImageSize:        00B07B00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the NVIDIA Video Card Drivers:

nvm62x64.sys Sat Oct 18 03:01:06 2008 (48F8FD12)
nVidia Ethernet Networking Driver (nForce chipset driver)
Driver Reference Table - nvm62x64.sys

nvlddmkm.sys Fri May 15 02:48:07 2009 (4A0C8387)
nVidia Video drivers
Driver Reference Table - nvlddmkm.sys

amdxata.sys Tue May 19 23:56:59 2009 (4A12F2EB)
AMD storage controller driver - usually from the Windows 7 DVD
Driver Reference Table - amdxata.sys

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to Clean Left Over Driver Files with Driver Sweeper

Drivers - Clean Left over Files after Uninstalling

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems