Persistent 0x50 BSOD upon restart, fresh install.


  1. Posts : 4
    Window 7 Home Premium 64 bit
       #1

    Persistent 0x50 BSOD upon restart, fresh install.


    Hello guys, I've got an annoying BSOD on a nearly new computer, and I've tried to exhaust possibilities but can't seem to nail it down.

    Windows 7 x64 OS
    AMD Athlon ii x2 250 Processor @3 ghz
    Gigabyte GA-M68MT-SP2 F1 (w/ onboard Nvidia GeForce 7025/630a Graphics)
    ATI Radeon HD 5400 1 GB Graphics
    8GB 1333mhz PKR RAM (replaced 4GB Kingston, replaced to rule out RAM fault)
    500 GB Seagate Harddisk
    It's a custom build from Ginger6

    The BSOD keeps occurring even on a fresh OS; I reinstalled last night and it begins happening from the first windows update restart, or sometimes when installing programs.

    I've tried to rule out graphics - BSOD occurs both with ATI graphics card installed and also on the onboard Nvidia Graphics - I've used their respective online tools to find the right drivers, so I think they're up to date

    I've also tried to rule out Ram faults - I tested the original kingston Ram numerous times on Memtest and Windows Memory debugging - no faults came back but to be safe I replaced with the 8GB PKR

    I've ran chkdsk on the hard disk and it came back with no errors - in previous attempts I formatted the drive before a fresh OS install - no joy there

    Bluescreen view points to ntoskrnl.exe, and I've tried using the MS debugging but I'm not sure I'm doing it right

    So, all in all, I'm at a loss as to what to try next - I figured the experts here might be able to help me out. Thanks for your time, much appreciated

    David
    Persistent 0x50 BSOD upon restart, fresh install. Attached Files
    Last edited by daveydave43; 22 Apr 2012 at 10:11. Reason: to add BSOD attachments
      My Computer


  2. Posts : 4
    Window 7 Home Premium 64 bit
    Thread Starter
       #2

    Any help with this guys? Cheers :)

    David
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #3

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\daveydave43\Windows_NT6_BSOD_jcgriff2\042212-45037-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
    Machine Name:
    Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02ca6650
    Debug session time: Sun Apr 22 01:35:15.904 2012 (UTC - 6:00)
    System Uptime: 0 days 0:00:49.231
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ffffe88003820b12, 1, fffff80002ddc196, 7}
    
    
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt!IopParseDevice+a06 )
    
    Followup: MachineOwner
    ---------
    
    1: 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: ffffe88003820b12, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002ddc196, 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 fffff80002d10100
     ffffe88003820b12 
    
    FAULTING_IP: 
    nt!IopParseDevice+a06
    fffff800`02ddc196 6641894502      mov     word ptr [r13+2],ax
    
    MM_INTERNAL_CODE:  7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff880038204b0 -- (.trap 0xfffff880038204b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000000000d8 rbx=0000000000000000 rcx=000000000000001c
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ddc196 rsp=fffff88003820640 rbp=fffffa800958e1c8
     r8=0000000000000000  r9=0000000000000000 r10=fffff80002c68348
    r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!IopParseDevice+0xa06:
    fffff800`02ddc196 6641894502      mov     word ptr [r13+2],ax ds:00000000`00000002=????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a89ba7 to fffff80002adec80
    
    STACK_TEXT:  
    fffff880`03820348 fffff800`02a89ba7 : 00000000`00000050 ffffe880`03820b12 00000000`00000001 fffff880`038204b0 : nt!KeBugCheckEx
    fffff880`03820350 fffff800`02adcdae : 00000000`00000001 ffffe880`03820b12 00000000`00001000 00000000`00000045 : nt! ?? ::FNODOBFM::`string'+0x43cc1
    fffff880`038204b0 fffff800`02ddc196 : 00000000`00000045 00000000`00000045 fffffa80`0958e1c8 fffff880`03820690 : nt!KiPageFault+0x16e
    fffff880`03820640 fffff800`02dd85d8 : fffffa80`0799c940 fffff800`00000000 fffffa80`0958e010 00000000`00000001 : nt!IopParseDevice+0xa06
    fffff880`038207d0 fffff800`02dd97f6 : 00000000`00000000 fffffa80`0958e010 00000000`00000000 fffffa80`06a20600 : nt!ObpLookupObjectName+0x588
    fffff880`038208c0 fffff800`02db9736 : fffffa80`08eb0550 00000000`00f6f2a0 fffff8a0`01f10001 fffffa80`076f2010 : nt!ObOpenObjectByName+0x306
    fffff880`03820990 fffff800`02addf13 : fffffa80`08eb0550 fffff880`03820ca0 fffffa80`08eb0550 fffffa80`08ea3ec0 : nt!NtQueryAttributesFile+0x145
    fffff880`03820c20 00000000`76e916ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00f6f268 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e916ea
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!IopParseDevice+a06
    fffff800`02ddc196 6641894502      mov     word ptr [r13+2],ax
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!IopParseDevice+a06
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!IopParseDevice+a06
    
    BUCKET_ID:  X64_0x50_nt!IopParseDevice+a06
    
    Followup: MachineOwner
    ---------
    The above crash usually indicates memory problems. Also, make sure you do not have ATI and NVIDIA software installed at the same time; it can conflict and cause crashes.

    The below information is to help you install the latest driver for the graphics device you are currently using, and it is also provided to help you remove the software the device you are not using.
    1. Download the latest drivers for your display card(s)
    2. Click Start Menu
    3. Click Control Panel
    4. Click Uninstall a program
    5. For NVIDIA:
      • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
      • Restart your computer
      • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
      • If any remain of the above, uninstall one at a time
      • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
    6. For AMD:
      • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
      • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
        1. Click Start Menu
        2. Right Click My Computer/Computer
        3. Click Manage
        4. Click Device Manager from the list on the left
        5. Expand Display adapters
        6. Do the following for each adapter (in case you have multiple display cards)
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
        7. Restart your computer after uninstalling drivers for all display cards
        8. Install the latest driver for the display cards once Windows starts


        Alternatively:
        1. Login as an adminstrative user
        2. Click Start Menu
        3. Click Control Panel
        4. Click Hardware and Sound
        5. Click Device Manager (the last link under Devices and Printers)
        6. Expand Display adapters
        7. Do the following for each adapter (in case you have multiple display cards)
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    7. Restart your computer after uninstalling drivers for all display cards
    8. Install the latest driver for the display cards once Windows starts



    Check your memory:
    • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

      For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
      1. Shut down and turn off your computer.
      2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
      3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
      4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

      Once these steps have been followed, it is safe to remove and replace components within your computer.

    • Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
      My Computer


  4. Posts : 4
    Window 7 Home Premium 64 bit
    Thread Starter
       #4

    Hello there, cheers for replying :)
    I uninstalled the Nvidia and ATI software via the control panel, and restarted, which resulted a couple more crashes, same 0x50 type: the ATI card plus drivers are still installed
    Looking through the device manager, I do appear to have a mix of ATI and Nvidia drivers -

    ATI Radeon HD 5400 Series
    NVIDIA nForce Serial ATA Controller
    NVIDIA nForce Networking Controller

    The onboard motherboard graphics are also Nvidia, but those drivers are not installed at the moment.
    I'm going to run without the ATI graphics card, and just on the m/board graphics, to see if it is a the ATI Nvidia conflict

    edit* Right, I've taken the graphics card out and computer is running on the integrated m/board graphics only, no blue screens, and I've restarted numerous times to make sure.

    Is it worth trying to re-install the ATI card? I can't find any individual drivers on their website, it all seems to come under the Catalyst software, so is there somewhere else I should be looking or would that be alright?
    Last edited by daveydave43; 24 Apr 2012 at 02:18. Reason: Update
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    The mixed NVIDIA and ATI drivers will occur on your system, but you need to avoid mixed graphics drivers. The drivers you list are for your hard disk controller and network controllers and will not conflict with the graphics. What you want to make sure of is no NVIDIA graphics related software through start menu -> control panel -> uninstall a program by going through the software I provided in my previous post and making sure none of that software is installed when using the ATI card.


    You should try installing only the drivers for the ATI card after uninstalling the AMD Install Manager software. You can manually install the drivers for the ATI card as follows:
    • Download the ATI Catalyst software and begin the install.

    • Start the installation.

    • When you are given the option for the express install, cancel out of the installation.

    • The ATI folder should now be unpacked in C: under the AMD folder.

    • Open device manager as in my previous post.

    • Go to Display adapters and expand it by pressing the arrow/triangle to the left of the icon. Note: Your display adapter may also show up in unknown devices with a yellow triangle and exclamation point. You may also have to click the scan for hardware changes to get it to show up. To scan for hardware changes, click on the icon showing the Magnifying glass hovering over the computer.

    • Right click the generic VGA adapter (if it already says ATI then you do not need to follow the next steps)

    • Click Update Driver Software...

    • Follow steps 3-5 in OPTION TWO of Drivers - Install Vista Drivers on Windows 7

    • The drivers will be in C:\AMD\Support\**-*_vista_win7_64_dd_ccc\Packages\Drivers\Display\W76A_INF

    The asterisks are for the version of the driver being installed. Mine, for instance, were 12-3_vista_win7_64_dd_ccc\Packages\Drivers\Display\W76A_INF
      My Computer


  6. Posts : 4
    Window 7 Home Premium 64 bit
    Thread Starter
       #6

    Okay, problem seems fixed! Thanks for your help!

    Think I might go with an Nvidia graphics card next time if it avoids all these issues.
    David
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #7

    You're welcome. :) See how the system responds for a few days, and you can mark the thread solved when you are sure it is.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:15.
Find Us