Skype install causes a BSOD ks.sys Crash

Similar Questions

• Satellite A660-1CJ - 8.1 Windows crashes - BSOD bridge.sys

  Hello

  I have a Satelite A660-1CJ, running Windows 8.1 and he already broke 5 times with a BSOD:
  DRIVER_IRQL_NOT_LESS_OR_EQUAL (bridge.sys)

  What can I do?

  Hello

  It seems that the bridge.sys is causing the BSOD.
  Bridge.sys is a Windows system component.

  Toshiba says that the Windows 8.1 is not supported on Satellite A660 series.
  What does that mean?
  This means that Windows 8.1 drivers are not released by Toshiba.

  I assume that you have installed drivers in your own hand and probably one of the drivers causing the BSOD.

• BSOD caused by NETIO. SYS

  Hi all

  I am running Windows 7 on a laptop Samsung series 7 NP700Z5A-S0AUS. Recently I've been making a large number of BSOD (as much as two or three a day) that appear to be caused by the netio.sys driver. You can download the most recent dump of my computer here file: https://dl.dropboxusercontent.com/u/488076/Blue%20Screen%20Dump.dmp
  I'm good with instructions and I am happy to provide any additional info, you may need. Any help will be greatly appreciated!
  Kind regards
  Jacob

  Hello

  For netio.sys errors updated network driver (NIC) and wireless (WiFi) drivers from the
  Site of the manufacturer of system/motherboard if embedded and the sites of manufacturers of real devices if they are separated
  devices. Check also for the update of the BIOS and the low level chipset drivers

• Service exception C50-A-157 - BSOD - (Netio.sys) satellite system

  Hi, I recently had random stops, and I got this error message.

  Service system (Netio.sys) exception

  Any help would be appreciated.

  NetIO.sys file belongs to the the network driver, which is part of the Windows System.

  In some cases of different network applications, antivirus and firewall software may cause this show NetIO.sys BSOD.
  You have probably a program installed that may cause problems with your network connection.

  For example: program NVIDIA Network Access Manager. This software is available during the installation of NVIDIA network adapter drivers.
  But as far as I know this laptop doesn't support nVidia GPU... so it should not be installed on your system...

  However... Check if the NVIDIA Network Access Manager software or other network software is installed... and if possible to uninstall this kind of software using the option "uninstall a program".

• BSOD iusb3xhc.sys

  Greetings! I have problem with my pc im getting random BSOD iusb3xhc.sys. I think it all started when I updated some drivers using extra driver. I got about 3 or 4 BSOD randomly this sort relating in particular to iusb3xhc.sys everything. I run sfc/scannow, and she reported that it fixed a problem .i run it again 3 times and no problems have been detected and I thought that everything was going well so far.
  I have a win 7 ultimate 64-bit service pack 1
  Core i3 of intel 4160
  RAM Kingston kvr 4 x 2 8 GB
  motherboard Asus b85m g
  660 GTX video card
  160 GB of disk velociraptor hard disk OS and 500 GB samsung spinpoint f3 as storage device
  Corsair vs650 650watts PSU.

  Here's the last minidump file:
  http://1drv.Ms/1JdcgRN

  Hello

  Apologize for the delayed response. It seems that this problem started after the installation of the Booster driver in the computer. These applications are known to cause damages instead of being useful to the computer. Did you uninstall the software from the computer? If this isn't the case, I suggest you uninstall the same and check if still have problems you.

  See the following article to troubleshoot BSOD:

  http://Windows.Microsoft.com/en-in/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

  Please make sure that your computer is virus-free by running a full scan using the Microsoft Safety Scanner. No doubt these files were created by viruses.

  Note: The files infected by viruses will be deleted and so there is a chance of data loss.

  Please be sure to download and install the latest drivers for your card display and Chipset graphics and motherboard from the manufacturer's website. Also check the updates of the firmware or the BIOS and install it as well.

  Come back for additional help.

• BSOD "dxgmms1.sys" for the game World of Warcraft on Windows 7 Ultimate x 64

  Recently, I made a new installation of Windows 7 (delete hard drives/formatting etc.) and installed WoW today with each update of windows, DirectX, c ++ etc. I played for about 4 hours and I got a BSOD. I looked at the dmp with BlueScreenView and it said that dxgmms1.sys was the problem. I don't know what it is or how to fix this so that any help would be appreciated. I have included my dmp file in a link mediafire HERE if someone wants / needs to have another look.

  Hello

  The attached file of the DMP is to bug checking SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) .

  This indicates that a system thread threw an exception who did not catch the error handler.

  Bugcheck 1000007E, {ffffffffc0000005, fffff8800fdb7ec8, fffff88007c22668, fffff88007c21ec0}

  ^^ 1 bug checking parameter is 0xc0000005 indicating an access violation has occurred:

  2: kd > .exr 0xfffff88007c22668
  ExceptionAddress: fffff8800fdb7ec8 (dxgmms1!) VIDMM_GLOBAL::ReferenceAllocationForPreparation+ 0x00000000000000c4)
  ExceptionCode: c0000005 (access violation)

  ^^ Access violation has occurred in dxgmms1! VIDMM_GLOBAL::ReferenceAllocationForPreparation.

  -dxgmms1.sys is the MMS X Direct.

  ------------------

  1. remove and replace AVG with Microsoft Security Essentials for purposes of troubleshooting temporary, as it is probably cause conflicts:

  -AVG removal http://www.Avg.com/us-en/utilities

  MSE - http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download 

  2 in your list of drivers loaded, dtsoftbus01.sys figure who is the driver for Daemon Tools. Daemon Tools is a very popular cause of BSOD in 7/8 base systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

  3. make sure you have the latest video card drivers. If you are already on the latest graphics card drivers, uninstall and install a version or a few versions behind the last to make sure this isn't a last number one driver. If you have already experienced with the driver of the card later and earlier versions, please try the driver beta for your card.

  Kind regards

  Patrick

• Qosmio G50 - 10 H - I get BSOD usbvideo.sys

  I have the Qosmio G50 - 10H.

  Sometimes I get a BSOD indicating a problem with usbvideo.sys.
  Does anyone have any ideas as to what could be the problem.

  A search of my files, including hidden files, shows no version of this file on my laptop.

  Thank you

  Hello

  The USBVIDEO. SYS driver is part of the Windows operating system and it of a Microsoft driver.
  I don't very well why this disc is causing the BSOD, but it is advisable to clean the operating system and registry run CCleaner and upgrade the OS to the latest state of m!

  In the worst case we could recommend recover the operating system by using Toshiba drives.

  Welcome them

• BSOD - usbhub.sys

  Hello!

  I bought a g505s and I have upgraded to Windows 8.1. Sometimes I get bsod usbhub.sys related.

  Here is my production of windbg:

  Microsoft (R) Windows debug 6.3.9600.16384 AMD64 Version
  
  Copyright (c) Microsoft Corporation. All rights reserved.
  
  Loading dump file [C:\Windows\MEMORY. DMP]
  
  The Bitmap core dump file: the single kernel address space is available
  Symbol of validation of the path summary *.
  
  Response                         time (ms)     location
  
  Report                                       srv*c:\symbols*msdl.microsoft.com/download/symbols
  
  Symbol search path is: srv*c:\symbols*msdl.microsoft.com/download/symbols
  
  Executable search path is:
  
  Windows 8 Kernel Version 9600 MP (4 procs) free x 64
  
  Product: WinNt, suite: TerminalServer SingleUserTS
  
  By: 9600.16452.amd64fre.winblue_gdr.131030 - 1505
  
  Computer name:
  
  Core = 0xfffff801 'e121c000 PsLoadedModuleList = 0xfffff801' e14e0990
  
  The debugging session: Sun Jan  5 2014 12:09:45.020 (UTC + 02:00)
  
  System Uptime: 2 days 1:33:11.375
  
  Loading the kernel symbols
  
  ...............................................................
  
  ................................................................
  
  ............................................
  
  Loading user symbols
  Loading unloaded module list
  
  ....................................
  
  *******************************************************************************
  
  *                                                                             *
  
  *                        Bugcheck analysis                                    *.
  
  *                                                                             *
  
  *******************************************************************************
  Use! analyze - v to obtain detailed debugging information.
  9F error checking, {3, ffffe00002dc8060, fffff801e2be3840, ffffe0000276eb80}
  Probably caused by: usbhub.sys
  Follow-up: MachineOwner
  
  ---------
  0: kd >! analyze - v
  
  *******************************************************************************
  
  *                                                                             *
  
  *                        Bugcheck analysis                                    *.
  
  *                                                                             *
  
  *******************************************************************************
  DRIVER_POWER_STATE_FAILURE (9f)
  
  A pilot was not a power of the PRI ends in a moment.
  
  Arguments:
  
  Arg1: 0000000000000003, a device object has been blocking an Irp for too long
  
  Arg2: ffffe00002dc8060, physical device from the stack object
  
  Arg3: fffff801e2be3840, nt! TRIAGE_9F_POWER on Win7 and higher, otherwise the functional device object of the stack
  
  Arg4: ffffe0000276eb80, blocked IRP
  Debugging information:
  
  ------------------
  DRVPOWERSTATE_SUBCODE:  3
  Nom_image:  usbhub.sys
  DEBUG_FLR_IMAGE_TIMESTAMP:  5215f839
  MODULE_NAME: usbhub
  FAULTING_MODULE: fffff8000300f000 usbhub
  DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
  BUGCHECK_STR:  0x9F
  Nom_processus:  System
  CURRENT_IRQL:  2
  ANALYSIS_VERSION: 6.3.9600.16384 (debuggers (dbg). 130821-1623) amd64fre
  DPC_STACK_BASE:  FFFFF801E2BEBFB0
  STACK_TEXT:
  
  fffff801 'e2be3808 fffff801' e14131a6: 00000000' 0000009f 00000000'00000003 ffffe000 '02dc8060 fffff801' e2be3840: nt! KeBugCheckEx
  
  ' fffff801 'e2be3810 fffff801' e14130c6: ffffe000 ' 07968650 00000000' e9f181f0 00000000 00000003' fffff801 ' e1278a04: nt! PopIrpWatchdogBugcheck + 0xde
  
  ' fffff801 'e2be3870 fffff801' e12c9f64: ffffe000 ' 07968688 fffff801 ' e2be3939 ffffe000'079686 c 8 00000000'00000002: nt! PopIrpWatchdog + 0x32
  
  ' fffff801 'e2be38c0 fffff801' e12ca478: 00000000 ' 00000001 ffffe000 ' a 0238, 748 fffff801 'e150a180 fffff801' e150e0c0: nt! KiProcessExpiredTimerList + 0x1d8
  
  fffff801 'e2be39a0 fffff801' e1326478: fffff801 'e150a180 00000000' 001f3bea 00000000' 0067 d 662 00000000' 0067d67a: nt! KiExpireTimerTable + 0 x 218
  
  ' fffff801 'e2be3a40 fffff801' e1276abc: ffffe000 00000000' 00001f80 ' 0000019f 00000001 ' 598dfbd6 00000000'00000002: nt! KiTimerExpiration + 0 x 148
  
  fffff801 'e2be3af0 fffff801' e136d7ea: fffff801'e150a180 fffff801 'e150a180 00000000' 001a3fc0 fffff801' e1562a80: nt! KiRetireDpcList + 0x19c

  
  fffff801'e2be3c60 00000000' 00000000: fffff801 'e2be4000 fffff801' e2bdd000 00000000'00000000 00000000'00000000: nt! KiIdleLoop + 0x5a

  STACK_COMMAND: kb

  FOLLOWUP_NAME: MachineOwner

  IMAGE_VERSION: 6.3.9600.16384

  FAILURE_BUCKET_ID: 0x9F_3_btfilter_IMAGE_usbhub.sys

  BUCKET_ID: 0x9F_3_btfilter_IMAGE_usbhub.sys

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:0x9f_3_btfilter_image_usbhub.sys

  FAILURE_ID_HASH: {e32271a1-eb13-6913-1626-4c8d704b5d5a}

  Follow-up: MachineOwner
  ---------

  Any advance-help would be appreciated.

  Thank you

  I'll try to reinstall my bluetooth drivers...

• Access to a specific registry key (HKEY_USERS\S-1-5-18\software\Microsoft) causes a BSOD. How can I fix the key?

  Original title: access to a specific registry key generates BSOD. How can I fix the key?

  Scans the registry in XP causes a BSOD. The wrong key is HKEY_USERS\S-1-5-18\software\Microsoft. Access to manually also causes a BSOD so I can't delete or export it. I do not have a restore point from before the problem started. Other than the access to that key or run a search, XP works well.
  Is it possible to fix this?

  Not having no not this error in my notes (in other words, I've not seen at least 2 times), I Googled it and first fell on a MS KB article:

  http://support.Microsoft.com/kb/810558

  This article includes this statement:

  Contact Microsoft Technical Support to help heal the corruption in the registry.

  I think that is where you are right now, so let's see what is the response of the Microsoft Support Engineer, now that there is more information.  I always love to see what they have to offer first.

  Why and how did you change the system restore to create restore Points 3 a day for 30 days (FYI - that is not the same as a backup).

  If you were to solve some problem at the time, what was the question?

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

  In the meantime, I would run a chkdsk /r on your volume XP since XP Recovery Console.

  If you are not sure of the SP2 CD you have is an XP bootable installation CD authentic and not some kind of restore CD for the Dell system to 100%, I would recommend this (that I've seen more than 2 times):

  If you have no XP bootable media (or aren't sure you have) create a bootable XP Recovery CD of Console and don't forget (no support for XP not necessary).

  This is not the same as recovery disks that might have come with the acquisition of the system store.

  You can make a bootable Recovery Console CD by downloading an ISO file and burn it to a CD.

  The ISO bootable image file you need to download is called:

  xp_rec_con. ISO

  Download the ISO from here:

  http://www.mediafire.com/?ueyyzfymmig

  Use a new CD and this simple and free program to burn your ISO file and create your bootable CD (do not install UniBlue or the Ask Toolbar - never!):

  http://www.ImgBurn.com/

  Here are some instructions for ImgBurn:

  http://Forum.ImgBurn.com/index.php?showtopic=61

  It would be a good idea to test your bootable CD on a computer running.

  You may need to adjust the computer BIOS settings to use the CD-ROM drive as the first device to boot instead of the hard drive.  These adjustments are made before Windows tries to load.  If you miss it, you will need to restart the system again.

  When you start on the CD, follow the instructions:

  Press any key to boot from CD...

  Installing Windows... going to pronounce.

  Press 'R' to enter the Recovery Console.

  Select the installation that you want to access (usually 1: C:\WINDOWS)

  You may be asked to enter the password (usually empty).

  You should be in the folder C:\WINDOWS.  It's the same as the

  C:\Windows folder that you see in Solution Explorer.

  The Recovery Console allows base as file commands: copy, rename, replace, delete, chkdsk, fixboot, fixmbr, cd, etc.

  For a list of the commands in the Recovery Console, type help at the prompt of commands or read on here XP Recovery Console:

  http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

  A good idea before you start things must first verify the integrity of your file system by using the chkdsk command.

  In the command prompt window, run the chkdsk command on the drive where Windows is installed to try to fix any problems on the afflicted player.

  Running chkdsk is fine, even if he finds no problem.  It won't hurt anything to run it.

  Assuming your boot drive is C, run the following command:

  CHKDSK C: /r

  Let chkdsk finish to correct the problems, he could find.

  It may take a long time for chkdsk complete or they seem to be "stuck".  Be patient.  If the HARD drive led blinks always, chkdsk is something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.

  You must run chkdsk/r again until it finds no error to correct.

  Remove the CD, and then type "exit" to exit the RC and restart the computer.

  You have not to set the BIOS to boot the disk HARD since the CD won't be.

• Vista updates causing interference day and PC crashing.

  Greetings,

  I have a tiny little problem. It seems that the new updates for Windows Vista has been causing some intolerable freeze and crash my PC. I don't understand quite updates are causing it. How ever I can officially say that BEFORE I updated my machine it worked almost perfect (except for the graphics). I won't be pesmistic, it really worries me. On top of her crashing and freezing. I also noticed a sufficient amount of gain and loss data. I.E. I have several backups of games on pc before I played. but when I'm done with extracting files and remove approximately "20" of them only '13' will do for the recycling bin, so my (OS - operating system) * HDD partition * wins extra/hidden files. I also noticed that my PC has not been suggested to download SP2 from the Auto Update Center. I had to recover this file manually on the microsoft site. Please explain this problem and please not to recommend a re-installation of the operating system... I have already this is plenty of time to do it either.

  Side of a person responding to this hopeful message. because I have problems with my pc could you please send me a response @ (* address email is removed from the privacy *) thank you.  "ACEs".

  You will get the best help for your question of Windows Update in the right Forum; link at the bottom of this answer.

  http://www.bleepingcomputer.com/tutorials/tutorial140.html

  Understanding Windows Update and Extras in Windows Vista at the link above.

   

  Remove the Vista updates; two ways to do this:

  1. a System Restore to before the updates:

  Click Start > programs > Accessories > system tools > System Restore > restore time/choose your own date > next

  If you use Norton, disable it before using the system restore.

  If it is impossible to enter the Normal Mode, do a Safe Mode system restore:

  Press F8 at the startup/power and the list of startup options, use THE ARROW key to select Safe mode > and then press ENTER.

  System restore steps according to the info above.

  Also:

  2. click on start > right click on computer > properties > Windows updates down the lower left corner > updates installed in the lower left corner in the next window

  > then click the one that you don't want > uninstall will appear at the top > uninstall it.

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  In addition, on the page where you clicked "Installed updates", click on change settings at the top left corner it

  > Change update settings in the next page of AutoUpdate to "check for updates but let me choose etc" > OK ".

  When you take a look at pending updates, you can either download/install them one at the time, namely the update causing you problems.

  > or if you do not need an individual > right-click on > UAC prompt > hide it

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  Windows Update Forum:

  It's updated operating system Vista, upgraded installation and activate Forum.

  You will get the best help for any problem of Update/Service Pack in the Windows Update Forum; the link below:

  http://social.answers.Microsoft.com/forums/en-us/vistawu/threads

  When you repost here, kindly include the Error Codes, and exactly what is happening when you try to update.

  In this way, you will receive the best help.

  See you soon.

  Mick Murphy - Microsoft partner

• Use of system high - random, TFP causes a BSOD.

  Original title: System high use

  Hey Microsoft:

  Software can dominate the system resources?   I have a program which, lately, seems to want to use all system resources to the point of view of a BSOD.   Unfortunately, there is no way to post a screenshot of the Task Manager.  So I ask on manually in this post.

  Username name image CPU Memory (Private working set) Description

  Taskmgr.exe Gary S...        00 2 112 K Windows Task Manager

  PTF 16PRO.exe Gary S...       TurboFloorPlan3D 00 212 172 K

  Winlogon.exe 00 1 896 K

  Any software that I run... IE11, Google Earth, Photoshop Elements, works fine.  But at random times, TFP causes a BSOD.  BAD_POOL_HEADER sometimes, sometimes other random messages. Sometimes, this software will work correctly, but when I click the X (to close), usually I'll take the option to SAVE.  Sometimes it will just stop, and will display the BSOD.  If my CPU / RAM goes bad, why who is not performing OTHER software?    I tried to reinstall the TFP, where the initial installation has not "installed" correctly.    And, if this software is not compatible with my Windows 7 Pro 32 bit, then it would not operate in first place.    I thought to do a total reinstall of Windows7.  But, the last time I did this, the FORMAT option on the disk version would not allow me to FORMAT my hard drive, just DELETE the partition only. Which could explain the instability of my copy of Windows 7.   If my thinking is correct, then THIS time, while still in Windows 7, put in my CD Player installation disc, FORMAT my hard drive.  Restart the disk, then go through the process of re - install... correct?     Advice?

  stanulg

  In order to diagnose your problem, we need run Windows performance toolkit, the instructions that are in this wiki

  If you have any questions do not hesitate to ask
  
  
  Please run the trace when you encounter the problem

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

• McAfee obsolete computer installed causing close

  McAfee obsolete computer installed causing close

  Get rid of it.
   
  Correction of tool McAfee Consumer Product Removal triple
  http://service.McAfee.com/FAQDocument.aspx?LC=1033&ID=TS100507  

• Any who save a pre-installed Windows xp home edition that crashed...

  Hello
  My cousin had this pre-installed windows xp that the computer crashed recently, keep prompting
  for a recovery disc for repair, but this machine is pre-installed with a windows xp. Now to make
  the store that sold this machine went crashing too worse question. So what can he do to recover the
  computer? Thank you.

  Hi Daniel,.

  Thanks for bearing with me, now the recovery disc creator, is anyway I can enter the first hard disk.
  Or maybe some software I can download from microsoft? OOP! Sorry I ask, who cares about repair or
  maintenance of software, we sell only. Anyway, is that the recovery disk creator is something like the recovery console?
  I'm treating this horse dead as a direct. Anything radical might be considered.

• Problems with windows install, Skype instalation was failure, code 1601

  I tried to install Skype, but there was a message: "it was not possible to access Windows Installer, check with technical support if the installer of Windows" and nothing else. I don't know what to do, can you help me with this? He also write "Skype instalation was failure, code 1601" I checked also some other posts on Skype instalation problems, but it was not really useful for me, because I did not fully understand them.

  Hello Samuel,.

  Thank you for the update.

  1. What are updates?
  2. Have you tried to install these updates? If so, you receive error message?

  Try to install these updates one by one and check if they install.

  If you receive an error message, please let us know the error message full/code so that we can further research and help you.

  Thank you.