HP 2000 - no noise except reboot (Windows 8)

Hello

I have an intermittent problem on my computer, where there is no sound unless I restart the computer, or I put the computer in standby mode and turn it back on. I did an audio troubleshooting (which no issues were found), a system restore and the drivers updated. It is not a problem with my browser, because when the problem occurs, I can't listen to anything on the media player...

Thank you!

Hello

Try the following.

Open windows control panel, open Windows Update, select "View update history" in the left pane and then select "Installed updates" link in the next window.

Locate the KB2962407 update, right click and choose uninstall.  Once completed, restart the computer, open windows control panel, open Windows Update and select "Check for updates".  You will see the update that you have uninstalled just offered once again - right click and select "Hide update".

After that you may or may not need to remove and reload the sound driver - if you do, how to use Recovery Manager to reinstall the drivers and software is detailed in the document at the link below.

Recovery Manager - Windows 8.

Kind regards

DP - K

Tags: Notebooks

Similar Questions

  • Failed to create system restore point exception exception c:\windows\system32\shell32.dll,control_rundll,"c:\windows\system32\sysbm.cpl",system

    Original title: I can't do a restore point.

    I get exception c:\windows\system32\shell32.dll,control_rundll,"c:\windows\system32\sysbm.cpl",system what can I do?

    This has happened for a very long time.

    Does really say '... sysdm.cpl "?"

    Is that what the text complete and accurate of what the message said exactly?  (there is no sysbm.cpl in XP, but there's a sysdm.cpl).

    What happens if you click on start, run and enter in the box:

    sysdm.cpl

    Click OK - the system properties box opens?

    What happens if you click on start, run and in the type box (exactly):

    %SystemRoot%\System32\restore\rstrui.exe

    Click OK - is the open window of the system restore?

    What is exactly the process (step by step) you are using when you try to create the restore point and when in the process you see this message?

    I think it's a miracle that the Microsoft support engineer can provide a link to an article when the error message report you is a little out of whack and articles doesn't mention your error message at all.  It's real good troubleshooting or clairvoyance!

    You should also tell us a little about your system:

    Since the Microsoft Answers forum does not have any kind of information system request when a new question is asked, we know absolutely nothing about your system.  Not knowing the basic information a problem prolongs the frustration and the agony of these issues.

    Thank you MS Answers, allowing the resolution of simple problems as frustrating and a lot of time as possible.

    Provide information on your system, the better you can:

    What is your system brand and model?

    What is your Version of XP and the Service Pack?

    Describe your current antivirus and software anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc..

    The question was preceded by a loss of power, aborted reboot or abnormal termination?  (this includes the plug pulling, buttons power, remove the battery, etc.)

    The afflicted system has a working CD/DVD (internal or external) drive?

    You have a true bootable XP installation CD (it is not the same as any recovery CD provided with your system)?

    Do you see that you think not you should see and when you see it?

    What do not you think that you should see?

    If the system works, what do you think might have changed since the last time it did not work properly?

  • I can't find Microsoft Paint app in HP-2000-2b19wm laptop computer with windows 8.1

    I don't find Microsoft Paint app in HP-2000-2b19wm laptop computer with windows 8.1. I search in my C drive, and I offer files, which, when I opened the say I try to open a file of type "file system" (.dll) and then he offers me the store and word and other places to select to open the file, but when I select one of those, the file is still not there for me to open and use. Please help me find this file.

    Thank you.

    Hello

    Please try:

    • Hold down the Windows key and press Q
    • Painting in the Find box to anywhere

    You can locate paint from there, and you can "pin" in the taskbar.

    Kind regards.

  • I can´t find the network controller driver. Is Hp 2000 - 2d09EE, 8 x 64 windows. Please can you help me?

    Hello

    I can´t find the network controller driver. Is Hp 2000 - 2d09EE, 8 x 64 windows. Please can you help me?

    PCI\VEN_168C & DEV_0036 & SUBSYS_217F103C & REV_01
    PCI\VEN_168C & DEV_0036 & SUBSYS_217F103C
    PCI\VEN_168C & DEV_0036 & CC_028000
    PCI\VEN_168C & DEV_0036 & CC_0280

    Direct link is here

    http://ftp.HP.com/pub/SoftPaq/sp62001-62500/sp62425.exe

  • HP 2000-2c27CL Lan driver for windows 7

    Hello

    I have a laptop HP 2000 - 2c27CL that I installed Windows 7 Professional 64 bit because I don't like Windows 8.  I can't find the Lan Driver for Windows 7.  It took me forever to find the wireless driver, but I finally got.

    Please help me...

    Thank you

    DMEVid

    Hello:

    You can use all the drivers and the software of this model on your.

    DO NOT USE ANY BIOS OR THE FIRMWARE OF THIS MODEL FILES

    http://h10025.www1.HP.com/ewfrf/wc/softwareCategory?OS=4063&LC=en&cc=us&DLC=en&sw_lang=&product=5275376

    You are looking for Realtek ethernet LAN driver...

    If you have a controller SMBus needing a driver, you must download and install the drivers for the amd chipset, which is the first file in the list at the link below.

    http://support.AMD.com/en-us/download/chipset?OS=Windows%207%20-%2064

  • I have nothing on my screen except the window side bar same not start how he back?

    I have nothing on my screen except the window side bar same not start how he back?

    Restore point:

    http://www.howtogeek.com/HOWTO/Windows-Vista/using-Windows-Vista-system-restore/

    Do Safe Mode system restore, if it is impossible to do in Normal Mode.

    Try typing F8 at startup and in the list of Boot selections, select Mode safe using ARROW top to go there > and then press ENTER.

    Try a restore of the system once, to choose a Restore Point prior to your problem...

    Click Start > programs > Accessories > system tools > system restore > choose another time > next > etc.

    See you soon.

    Mick Murphy - Microsoft partner

  • Downloaded Windows 10. Yet, after each reboot, windows 7 restart... no windows 10?

    Original title: Windows 10

    I have a laptop with windows 7 installed. I ran a few the applet to see if the laptop is eligible. He did, and I see the windows icon 10 appearing in the task bar. I click on it to get the upgrade and windows starts the download process. Then after it is downloaded double click on the file and it seems to be the installation. This seems to go to the end and I restarted several times when asked to do so.

    Yet, after each reboot, windows 7 restart... no windows 10.

    Review:

    Retry the upgrade manually:

    Option 1:

    Download the media creation tool

    Click with the right button on the MediaCreationTool.exe file and then click on run as administrator.

    Note: How to check if you are downloaded or installed the update Windows 10 November

    How to create an ISO or USB drive.

    Select upgrade this PC now and then click Next

    Option 2:

    Task of pre-required

    When you make significant changes to your computer for example updated operating system, you must always back up. See the links to resources on the backup by clicking the link for each version of Windows you are using: Windows XP, Windows Vista, Windows 7, Windows 8/8.1

    then

    then

    • Turn off (preferably uninstall) your Antivirus utility before you perform the upgrade.
    • Reboot several times, and then try again.
    • Disable the general USB peripherals (for example - smart card reader).
    • If you are using a SCSI drive, make sure you have the drivers available for your storage on a thumdrive device and it is connected. During the installation of Windows 10, click on the advanced custom Option and use the command load driver to load the driver for the SCSI drive. If this does not work and the installer still fails, consider switching to an IDE based hard drive.
    • Perform a clean boot, restart, and then try again.
    • If you upgrade to the. ISO file, disconnect from the Internet during the installation, if you are connected in LAN (Ethernet) or wireless, disable both, then try to install.
    • If you are updated through Windows Update, when download reaches 100% disconnect from the LAN (Ethernet) Internet or Wi - Fi, then proceed with the installation.
    • If this does not work, try using the. ISO file to upgrade if possible.
    • If you are connected to a domain, go to a local account.
    • If you have an external equipment, attached to the machine, unplug them (example, game controllers, USB sticks, external hard drive, printers, peripherals not essential).
  • Cannot open the .eml files in Explorer windows except for Windows Live Mail

    In Windows XP, I could download the files of .eml Windows Live Mail on my computer and then open them from almost anywhere on my computer. In Windows 7, I can only open these files in Windows Live Mail. I have created an association between the 2, but I can not open files with the exception of Windows Live Mail. How can I change this?

    Simple design flaw. Simple solution - but he just buried by so many doors to Microsoft you idiots jump through.

    Follow these steps:

    I found the solution: Set Window Live Mail (WLM) defaults for EML files in Winodws 7:

    Panel--> programs-> set your default programs--> Windows Live Mail--> choose Defailts for this program. Now simply select .eml by checking the box. Select Save at the bottom and close.

    There you have it.

    It's another forum by Mike - http://TechHelp.Santovec.us

  • 2000 - portable 2b19WM - Downgrade from Windows 8 for Windows 7

    My sister recently bought a portable 2b19WM 2000 with Windows 8 and not to worry for the new operating system and want to return to Windows 7. A few questions:

    -Is it possible? Is the 2000-2b19WM compatible with WIN7?

    -If Yes, what drivers I need to locate for WIN7 so that the laptop work properly, or most works already?

    -If not, where can I find the drivers I have to perform the downgrade?

    It is possible to downgrade this machine to Windows 7. Its not particularly difficult, just time consuming.

    You will need to get the following:

    Win 7 drivers - http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=5275377&prodTypeId=321957&prodSeriesId=5259212&swLang=13&taskId=135&swEnvOID=4063#11360

    Everything you need is there except the driver of the Bus SM... you'll have to get directly from AMD.

    from THIS link http://www2.ati.com/drivers/13-1_vista_win7_win8_32-64_sb.exe

    Save these drivers on a USB key.  This laptop has no internet connectivity until the network drivers are installed.

    You must get the OEM version of flavor that never in Windows 7 that you want to install (Home, Pro, full, etc.)

    You are local MOM and computer store pop who built and sold computers should be able to set you up with one (you will probably need to buy a mouse or something to satisfy the requirement of equipment for OEM sales)

    5 DVD to back up your current configuration of Windows 8 (just in case something goes wrong).

    What you need to do:

    1. first of all use the HP Recovery Manager to create DVD of restoration Windows 8 since laptops recovery partition. Just in case where for some reason, something goes wrong during the downgrade or if ever you want to go back to windows 8. During the downgrade the recovery partition on the hard disk will be deleted, so if you don't do it now, you will need to order them from HP if you want to return to 8.

    2. go in settings PC in charms bar select GENERAL, and then scroll down to advanced options boot... choose the option that allows you to enter the BIOS.  Here, you will change the boot to 'LEGACY BOOT' section (don't worry about the warning that appears), and set the first boot on the internal DVD ROM drive device. Insert your Windows 7 DVD in the drive and press F10 to save the changes and reboot. the PC should boot from the DVD and start installing windows 7.

    3. when the installation program gets listed in the part where it asks where you want to install Windows 7, remove ALL partitions, and then create a new primary partition and continue the installation.  Windows 7 will NOT install with any of the original scores left in place.

    4. after the installation is complete and windows is enabled, install the drivers... starting with the driver chipset and video drivers first. The rest can be installed in what you order here...

    5. download and install Service Pack 1 from microsoft here http://www.microsoft.com/en-us/download/details.aspx?id=5842 choose the second from the bottom (the 6.1 windows x 64 version)

    THEN

    install internet explore 10... from there... http://www.Microsoft.com/en-US/Download/details.aspx?ID=36806

    Once it is all done,

    go to http://www.ninite.com

    Check the programs that you want from those available and click on the get Installer button... It will download and install the programs you choose in a single automated... scan this can save a lot of time.

    That's all there is too it.

    To return to 8, just jump in the BIOS to disable legacy startup and boot from DVD 1 of your recovery discs 8 woodwork earlier. and itll be immediately how it was when it was new out of the box.

  • p6130nl making noise after installing windows 7?

    Hi, I removed from Windows vista and installed Windows 7 (using a custom installation, not 'upgrade', so that the computer has been cleaned), but now it makes a humming noise when turned on. He had always made this noise then boot the system, but generally, it became quiet after the start-up had finished. Now, the noise persists. I already opened to check the fans, but they do not seem to be the problem; the noise continues even when I stop the fans spinning.

    What is the problem and how to fix it? It seems strange to me that something like clean the PC (deletion of all programs, etc., do not "clean up" the office itself) and installation of Windows 7 may cause sudden hardware problems...

    Thank you in advance!

    I managed to solve it after a night of messing around; installing new drivers did not work whether, since the problem is that it does not load the driver until the video Bios has been updated. And install other windows operating system did not help either, or formatting the drive etc etc etc.

    However, ultimately I just value all non-active disk partitions, rebooted the PC and went up in some menus weird (never seen that one before) which forced the office back to factory default (including the "thank you and welcome to your office purched brand-new", lol) and after that everything was done the graphics card acknowledged again and errors stopped. Being curious, I installed Windows 7 once again, and all the problems started once more. After a reset, I installed Windows 7 for the third time, but this time by using "update" rather than clean-install and that seems to work great so far.

    So: to assign all non-active partitions, and restart the PC. What he has done for me in the end.

  • Loud fan noise when runing Windows 8 on my Mac

    Hello to all the experts in Mac:

    I have recently installed Windows 8 with Bootcamp on my MacBook Pro (tecniques illustrated below) and when I start reading Microsoft Flight Simulator, which requires a lot of graphics, fans start to go very hard and the temperature is normal. Is there anyway to reduce the noise?

    Thank you

    MacBook Pro

    Processor: Intel Core i7-5557U CPU @ 3.10 GHZ

    Memory: 16GB

    Buffer: 512 GB (200 GB for Win8)

    The app is CPU intensive.

    Can I run Microsoft Flight Simulator X on my Mac?

    http://www.pcgamer.com/PC-gamers-Guide-to-gaming-on-a-Mac/

    http://www.Macworld.co.UK/feature/Mac/best-Mac-for-gaming-3446272/

    You can try to reset the SMC http://support.apple.com/kb/ht3964

  • Noise of crackling windows on Satellite P100-429

    I get crackling to regular windows sound effects intervells, someone else has had this prob?

    Recently had a problem with no sound at all from speakers who himself fixed in less than an hour also had no noise at some point, when I tried to turn up the volume on the toolbar that I received a msg saying no active device, when I went to the settings of the speakers it says there is no current , speakers there are involved, they are built.
    This prob also corrected himself.

    These are isolated probs and have not brought he runs again since.

    I'm alone with these probs?
    Does anyone have a solution?

    Hello

    I found very interesting information in this forum.
    According to statements of a user forum the crackling will not appear after the BIOS and updated audio driver.
    There is a sound driver update (V3.11.0.51) available that address this issue.

    Note: Before you install the audio driver updated at least, the BIOS version 2.10 or higher must be installed on the laptop.
    But do not forget to use a good BIOS and the correct BIOS update procedure

    How to install the Sound Driver (V3.0.51):
    1. download the driver of his Web site to a folder in time.
    2 unzip the file in a folder in time.
    3. double-click on the "setup.exe." Shortly after, the window
    4. click on 'OK '.
    5. click on 'OK '. The audio driver is installed

  • After reboot windows take position reset)

    Hello everyone. How do El Capitan to remember the position of the windows arranged after reboot? can't find anywhere. Help, please.

    Is that what you're after?

    Check the "Reopen windows when you connect in" before selecting restart.

  • PC PORTABLE from HP 2000 369WM: need to upgrade window 10 new pilots

    Hello everyone I have recently updated my laptop to HP 2000 369 WM 10 (64-bit) Windows, 4GB and now I need new drivers and I'm not sure where to find drivers spin an APU AMD E-450 with graphics Radeon (TM) HD

    PILOT

    AMD SMBus

    AMD SATA controller

    Realtek PCIE card reader

    Raltik RT5390 802.11b/g/n WIFI adapt

    I appreciate the help that I can ge, thanks a lot

    Jean

    You are the very welcome.

    The list of supported laptops may not matter as much as the list of compatible wireless cards... Please read the list below...

    SUPPORTED DEVICES:
    802.11n wireless PCI Express Card LAN Adapter
    MediaTek MT7630E 802.11bgn Wi - Fi adapter
    RALink RT3090 WiFi 802.11b/g/n adapt
    Wi - Fi 802.11b/g/n Ralink RT3290 adapter
    WiFi 802.11a/b/g/n Ralink RT3592 adapter
    RALink WiFi 802.11b/g/n RT5390 adapt
    RALink WiFi 802.11b/g/n RT5390R adapt

    -Provides the initial version of Windows 10 support WHQL driver.

  • Unexpected reboot Windows 2008 R2 server caused by PROCEXP111. SYS

    The computer was restarted after a bugcheck.  The bugcheck was: 0 x 00000050 (0xfffffa80bd8dc050, 0 x 0000000000000000, 0xfffff88008072ddd, 0 x 0000000000000000). A dump was saved in the: C:\Windows\Minidump\052313-36332-01.dmp. Report ID: 052313-36332-01.

    Report of the debugger:

    Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading dump file [C:\Windows\Minidump\052313-36332-01.dmp]
    The mini kernel dump file: only registers and the trace of the stack are available
    Symbol search path is: * invalid *.
    ****************************************************************************
    * Loading of the symbol may be unreliable without a symbol search path.           *
    * Use .symfix to get the debugger to choose a symbol path.                   *
    * After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols cannot be loaded because the path is not initialized. *
    *                                                                   *
    * The symbol path can be defined: *.
    * using the _NT_SYMBOL_PATH environment variable.                 *
    * using the o - argument when starting the debugger. *
    * using the .sympath and .sympath + *.
    *********************************************************************
    Could not load the ntoskrnl.exe, 0n2 error Win32 image
    WARNING: Unable to verify timestamp for ntoskrnl.exe
    ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (24 procs) free x 64
    Product: Server, suite: TerminalServer SingleUserTS Enterprise
    Computer name:
    Kernel base = 0xfffff800 '01a1d000 PsLoadedModuleList = 0xfffff800' 01b 61670
    The debugging session: 17:52:43.775 Thu May 23, 2013 (UTC + 10:00)
    System Uptime: 118 days 1:53:41.084
    *********************************************************************
    * Symbols cannot be loaded because the path is not initialized. *
    *                                                                   *
    * The symbol path can be defined: *.
    * using the _NT_SYMBOL_PATH environment variable.                 *
    * using the o - argument when starting the debugger. *
    * using the .sympath and .sympath + *.
    *********************************************************************
    Could not load the ntoskrnl.exe, 0n2 error Win32 image
    WARNING: Unable to verify timestamp for ntoskrnl.exe
    ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
    Loading the kernel symbols
    ...............................................................
    ................................................................
    ..................
    Loading user symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************
    Use
    ! analyze - v to obtain detailed debugging information.
    Bugcheck 50, {fffffa80bd8dc050, 0, fffff88008072ddd, 0}
    The kernel symbols are FALSE. Correct symbols to do the analysis.
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    ! KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    ! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    ! KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    !_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Cannot load the image PROCEXP111. SYS, 0n2 error Win32
    WARNING: Unable to verify timestamp for PROCEXP111. SYS
    ERROR: Module load completed but symbols can not be loaded for PROCEXP111. SYS
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    Probably caused by: PROCEXP111. SYS (PROCEXP111 + 1ddd)
    Follow-up: MachineOwner
    ---------
    8: 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.  In general, the address is simple bad or it
    pointing to freed memory.
    Arguments:
    Arg1: fffffa80bd8dc050, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88008072ddd, if not zero, the address of the instruction that refers to bad memory
    address.
    Arg4: 0000000000000000, (reserved)
    Debugging information:
    ------------------
    The kernel symbols are FALSE. Correct symbols to do the analysis.
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    !_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    ! KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    !_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    !_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    !_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt
    ! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    ADDITIONAL_DEBUG_TEXT:
    Use '! findthebuild' command to search for the generation of target information.
    If the build information is available, run '! findthebuild s; .reload ' to set the symbol path and of loading symbols.
    FAULTING_MODULE: fffff80001a1d000 nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 47194089
    READ_ADDRESS: could not get nt! MmSpecialPoolStart
    Unable to get nt! MmSpecialPoolEnd
    Unable to get nt! MmPoolCodeStart
    Unable to get nt
    ! MmPoolCodeEnd
    fffffa80bd8dc050
    FAULTING_IP:
    PROCEXP111 + 1ddd
    fffff880'08072ddd 66833805 cmp word ptr [rax], 5
    MM_INTERNAL_CODE: 0
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
    BUGCHECK_STR: 0 X 50
    CURRENT_IRQL: 0
    LAST_CONTROL_TRANSFER: from fffff80001a43eec to fffff80001a9bfc0
    STACK_TEXT:
    fffff880 '06-60348 fffff800' 01a43eec: 00000000'00000050 fffffa80 'bd8dc050 00000000 00000000' fffff880' 06a604b0: nt + 0x7efc0
    fffff880 '06 a 60350 00000000' 00000050: fffffa80 'bd8dc050 00000000 00000000' fffff880' 06a604b0 00000000' 00000000: nt + 0x26eec
    fffff880 '06-60358 fffffa80' bd8dc050: 00000000 00000000' fffff880 '06a604b0 00000000 00000000' fffffa80' 7d2c61d0: 0 x 50
    fffff880'06 has 60360 00000000 00000000': fffff880 '06a604b0 00000000 00000000' fffffa80' 7d2c61d0 00000000' 00000000: 0xfffffa80'bd8dc050
    STACK_COMMAND: .bugcheck; Ko
    FOLLOWUP_IP:
    PROCEXP111 + 1ddd
    fffff880'08072ddd 66833805 cmp word ptr [rax], 5
    SYMBOL_NAME: PROCEXP111 + 1ddd
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: PROCEXP111
    NOM_IMAGE: PROCEXP111. SYS
    BUCKET_ID: WRONG_SYMBOLS
    Follow-up: MachineOwner
    ---------

    Hello

    Support for Windows Server is not provided in these forums. On the other hand, it please repost your question in the relevant Microsoft TechNet forum here:

    http://social.technet.microsoft.com/Forums/en-us/category/windowsserver .

    Thank you.      :)

Maybe you are looking for