help with bluescreen error, hardware issue?

Page 1 of 3 123 LastLast

  1. Posts : 118
    Windows 7 Ultimate 64 Bit
       #1

    help with bluescreen error, hardware issue?


    I got this bluescreen and I've had before after this new upgrade. Anyone know what it is?

    Code:
    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.768.3
      Locale ID:    2057
    
    Additional information about the problem:
      BCCode:    4e
      BCP1:    0000000000000099
      BCP2:    0000000000016920
      BCP3:    0000000000000002
      BCP4:    0000000000016D1F
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    768_1
    
    Files that help describe the problem:
      C:\Windows\Minidump\020412-13852-01.dmp
      C:\Users\James Beagrie\AppData\Local\Temp\WER-15537-0.sysdata.xml
    Thanks
      My Computer


  2. Posts : 18
    Windows 7 32 bit & Windows 7 64 bit
       #2

    Most of the time your BSOD code is due to a bad driver. For more info try googling stop 0x000004e

    Although it could also be caused by hardware, Ram and HDD would be the first Hardware that I would check.

    What driver did you last install / What Hardware did you last install?
      My Computer


  3. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #3

    It was the graphics card drivers I believe I installed last.

    It may be unrelated but one of my hard drives has become louder than usual, could that be an issue?
      My Computer


  4. Posts : 18
    Windows 7 32 bit & Windows 7 64 bit
       #4

    Could be either, For the hard drive It sounds like you have more than one, could you operate with only one of them installed? In other words unplug the hdd that's making the abnormal sound, or is the noisy hdd the OS drive?

    You might also want to go into your MOBO bios and check the voltage of the 12v rail. You have a lot of HDD's and stuff for running only a 650w, it SHOULD be enough, but it is close. The 12v should be within 10% according to manufacturer spec, but you could see problems if it is more than 5% from spec so between 11.40v and 12.60v
      My Computer


  5. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #5

    Well I'll check graphics drivers for it, otherwise I know which drive it is and unplugged it before to check, I have 4 drives including 1 ssd.

    I'll have a look at voltages later on and see what's what. I've never modified things like that before so excuse me if I ask a stupid question :)

    I'll post back my results later on.
      My Computer


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

    Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with the crash reports. For driver issues, it is a shot in the dark to determine which driver is causing it. Same thing for hardware. Your blue screen is usually related to memory problems or drivers, so to narrow down which, we really need your crash reports from following those instructions.

    Thank you.
      My Computer


  7. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #7

    Ok, I attached the zip with the files that tutorial needed.

    Oh and I know about the disabled devices like Bluetooth etc. I know what they do.

    Basic Specs:
    Intel i7 2600k 3.4GHz
    MSi GTX 560ti
    Asus P8Z68-V Pro
    Corsair TX650M PSU
    3 Hard Drives
    1 SSD (Boot drive)

    Using 64-bit Full Retail
    System is upgraded less than a month ago.

    Thanks
      My Computer


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

    Code:
    
    Loading Dump File [K:\Kingston\BSODDmpFiles\beagrie07\Windows_NT6_BSOD_jcgriff2\020412-13852-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 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`03297670
    Debug session time: Fri Feb  3 17:56:01.756 2012 (GMT-7)
    System Uptime: 0 days 10:55:57.519
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................................................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 16920, 2, 16d1f}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 0000000000016920, page frame number
    Arg3: 0000000000000002, current page state
    Arg4: 0000000000016d1f, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_99
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  iw5mp.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80003157d7c to fffff800030cec40
    
    STACK_TEXT:  
    fffff880`0ba3f828 fffff800`03157d7c : 00000000`0000004e 00000000`00000099 00000000`00016920 00000000`00000002 : nt!KeBugCheckEx
    fffff880`0ba3f830 fffff800`03063a53 : fffffa80`0042e730 fffff680`0043bf00 fffff880`0ba3fae0 fffff6fb`400021d8 : nt!MiBadShareCount+0x4c
    fffff880`0ba3f870 fffff800`0311c7ad : 00000000`00000002 0000bd40`00000001 fffffa80`0042e730 00000000`00026ed0 : nt! ?? ::FNODOBFM::`string'+0x11d18
    fffff880`0ba3f900 fffff800`030dd5a4 : 00000000`00000000 00000000`00000000 fffff880`0ba3fa00 00000000`00000000 : nt!MiRemoveLowestPriorityStandbyPage+0x1d5
    fffff880`0ba3f980 fffff800`030ccd6e : 00000000`00000001 00000000`87838000 fffffa80`068e9601 00000000`10c1aad0 : nt!MmAccessFault+0x19e4
    fffff880`0ba3fae0 00000000`00738e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0c16b6e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x738e40
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiBadShareCount+4c
    fffff800`03157d7c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiBadShareCount+4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    Followup: MachineOwner
    ---------
    Possible causes are Memory problems... Drivers...

    Thanks to Dave76 for help understanding possible causes.



    We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

    • If you are overclocking any hardware, please stop.


    • 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).


    • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
      a. Backup your system and user files
      b. Create a system restore point
      c. If you do not have a Windows 7 DVD, Create a system repair disc
      d. Run Driver Verifier

      If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

      Thanks to zigzag3143 for contributing to the Verifier steps.
      If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.


    Also, update your netr28x.sys driver. I know it has an update because I have a similar device in my machine.
    Code:
    netr28x	fffff880`058ee000	fffff880`0598d000	Wed Feb 25 20:02:09 2009 (49a60631)	000a3bdb		netr28x.sys
    You may use the following sites as references for finding drivers. We recommend finding the manufacturer of the driver and downloading drivers directly from the manufacturer or software developer. If you have trouble finding a driver or driver manufacturer, let us know and we will do our best to assist you. If you need help, please provide the device name, manufacturer, and the driver .sys file that you are looking for.
    1. Driver Reference is a good site to find the driver .sys files, their descriptions, and the site most likely to contain an update.
    2. Driver Search Methods provides driver manufacturers and links to their homepages.

    There are a few methods for updating drivers.
    1. Installing and updating drivers in 7
    2. Driver Install - Add Hardware Wizard
    3. Driver Install - Device Manager


    To fully re-install a driver, use the following steps.
    1. Click Start Menu
    2. Right Click My Computer/Computer
    3. Click Manage
    4. Click Device Manager from the list on the left
    5. Find the device you are trying to uninstall by expanding the appropriate set of devices
    6. Right click the device
    7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Restart your computer
    10. Install the latest driver for the device 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. Find the device you are trying to uninstall by expanding the appropriate set of devices
    7. Right click the device
    8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    10. Restart your computer
    11. Install the latest driver for the device once Windows starts.
      My Computer


  9. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #9

    Ok I'll try these, I'll post back any results
      My Computer


  10. Posts : 118
    Windows 7 Ultimate 64 Bit
    Thread Starter
       #10

    I ran the memtest86+ test for 30 mins yesterday and it was ok, I'll be running it longer tonight.

    I did the driver verifer task, it lagged my system on bootup and was laggy using it too. I had one BSOD from the verifier going and I attatched another BSOD zip to this post.

    Cheers
      My Computer


 
Page 1 of 3 123 LastLast

  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 07:34.
Find Us