BSOD errors, seeking help narrowing of the cause

A quick overview - I've been "gifted" a site with about 250PCs to manage.  From the beginning of the contract (before my time), they have random BSOD errors and a few other programs that I am trying to sort now that I'm responsible for everything.

The issue is that when the user to log in and begin to open programs, or sometimes during the initial connection, the system will blue screen and they reboot.  To restart the system in general will allow them to connect you and start working.  Other times it can happen 2 - 3 times before the system decides to cooperate.

I started the collection of mini dumps memory.dmp and msinfo for systems after sorting what I could of BSOD Viewer (which only the States, it's a question about memory, but all searches are futile determine exactly what the cause.)

Here is a link to the 2 systems, that I'm watching, hoping someone can do the same a fraction of light to help solve this problem.  Users have dealt the question, at least 1-2 years, I've been here since February and I'm about to start pulling my hair (what little I have excluded).

Thank you all!

fffff880 '066 d 3398 fffff880' 04c 48130 * ERROR: Module load completed but symbols could not be loaded for mfeaack.sys
mfeaack + 0 x 48130

fffff880 '066cde68 fffff880' 01151c4a * ERROR: symbol file could not be found.  Defaulted to export symbols for mfehidk.sys-
mfehidk + 0x68c4a

McAfee and graphics card intel are mentioned in the two systems. I suggest you uninstall mcafee and running the tool of cleaning, found in the link below.

Recommended methods of removal of Windows: Windows 7

http://Windows.Microsoft.com/en-us/Windows/uninstall-change-program#uninstall-change-program=Windows-7

Download the tool Development http://us.McAfee.com/apps/SupportTools/MCPR/MCPR.asp

If you continue to have problems after you remove Mcafee, uninstall and reinstall your driver intel graphics.

Tags: Windows

Similar Questions

  • I have printer color laserjet 5550N having problem with error 59.C0. What is the cause of the error?

    I have printer color laserjet 5550N having problem with error 59.C0. What is the cause of the error?

    Thanks Ray,

    Hello... How can I get the manual download for all the error on any printer laser color spray top of HP range.

    Kind regards

    Monday Nwankwo

  • OSB console error messages: how to see the cause of the error

    Some of the error messages from the OSB, like the one below

    BEA-382612
    : Error to prepare the message for shipping
    Description
    A runtime exception has occurred during the preparation of the message out for the routing node. This occurred due to an error during the execution of the actions of the node routing request. There should be a specific error message that will point the cause of the problem

    How to view the cause of the error, such as described in the "BOLD" above. I'm not on the console when an error occurs.

    THX
    Ashwani

    Published by: Ashwani Kalra January 16, 2012 16:27

    Try to keep track of the message in the test console. Change the server debug logging level to see more debugging messages. Enable tracing in an operational framework of the proxy service and business.

    Most likely your proxy is not able to find the business service to route the message and it is why throw above mentioned error.

    Kind regards
    Anuj

  • BSOD error: IRQL GT ZERO at THE SERVICE of the SYSTEM

    Hello

    I have known many BSOD errors since last year. I tried to install a new copy of Windows, but the problem is still going.

    I read some responses who blame Bitdefender here, but I want to confirm by sending my dumpfiles before complaining to them, can you help me?

    I also read something related to this on Bitdefender forum http://forum.bitdefender.com/lofiversion/index.php/t48376.html, but I think that's exactly my problem. However, I installed the patch mentioned, but still have not tested its effectiveness... Could this hotfix (http://support.microsoft.com/kb/2664888) solve my problem?

    Here is the link to my dump files and msinfo32: http://www.4shared.com/rar/J0al3nomba/Minidump.html

    Thank you in advance.

    Renato Rigotto.

    Hello Renato.

    Thank you for the update on the issue and if problem continues try to follow these methods and check if it helps.

     

    Method 1:

     

    Select last good known in Windows Advanced options and check if that helps. To do this, restart the computer and press the F8 key for about four to five times. You will see the that last known good Configuration in the advanced options of windows. Please select last known good Configuration and then press enter.

     

     

    http://Windows.Microsoft.com/en-us/Windows7/using-last-known-good-configuration

     

     

    Method 2:

     

    You must disable the auto restart in case of failure system on your computer and note the error message receive you on the blue screen and you need to post back to us.

    To do this, you must start your computer on the Advanced Boot options , and select Disable automatic restart in case of system error.

    See this link to start your computer in Advanced startup options.

    http://Windows.Microsoft.com/en-us/Windows7/advanced-startup-options-including-safe-mode

     

     

    Method 3:

    I suggest to follow the steps described in the article and check if this can help resolve the issue:

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

    Hope it would help. If problem persists always post back with the current state of your computer and the result of the proposed suggestion, we will be happy to help you.

    Kind regards

  • 213.5 error please help me get the DW works again. Thanks CaptJim4685

    I have a Mac OS 10.10 used the Migration Assistant to move all the files from the old computer to new computer yesterday. Now can't use my Dreamweaver CS 5.5 I have my original installation disk. Tried that. Get the 213.5 error please help me get DW works again. Thanks CaptJim4685

    In my experience of software migration from one machine to another rarely works.

    Use the tools CS cleaner to wipe all trace of DW in your system before reinstalling.

    Use the CC cleaning tool to resolve installation problems. CC, CS3 - CS6

    Disabling an old product is necessary if you previously had it installed on 2 machines.  If you did, you need to contact Adobe customer service to disable your old facilities so you can activate the last being.

    Contact the customer service

    Nancy O.

  • Cannot download KB971468 error code 8E5E0147 what is the cause?

    Have tried everything microsoft has offered, to no avail. Would appreciate help, novice computer user. Thank you

    Sarahmc,

    Please post with the information requested here: what to post in the Windows Update forum
    Start with these troubleshooting steps and post returns with the requested info and arises from the troubleshooting.

    Clean boot your PC, and then run Windows Update.

    The system update tool

    Reset the Windows Update components

    Perform operations of KB883825

    Mike - Engineer Support Microsoft Answers
    Visit our Microsoft answers feedback Forum and let us know what you think.

  • Has anyone seen this error VAMI?  What are the causes?

    He's a service launched at startup, recorded in the var

    Cannot get the vamitty instance: unknown parameter TTY

    Google found nothing for me.

    Thank you

    CJ

    Hello

    Yes, that seems correct.

    TTY should be in the working environment of vamitty when it is started, but the error you mentioned seems to indicate the opposite.

    There is nothing else that it must call outside the initctl call as much as I know.

  • Displaying the right information to get a BSOD error help

    When your computer crashes and displays a blue screen there are often very valuable information about the photo that will allow users to help you solve your problem and to know what is causing this blue screen appears.

    Looking at the image at the end of the article you will see two sections highlighted, you will always want to post this information in your forum thread when looking for help she will be the most critical part of troubleshooting. The top tells us what's happening and said background where it goes to. We have just responded to two of the most important issues when you try to solve a problem.

    What's not?

    Where is the problem isolated to?

    Most of the text is quite annoying, but if that's important to you then it may be important for us. We have all seen what looks like a BSOD, but we do not know what your BSOD.

    There are more important questions that you can answer that will help your troubleshoot BSOD error message.

    1. What is your system brand and model? We know that you have an HP computer, but there are tons of computers. We need to know your specific model to ensure you use the appropriate drivers and we recommend the proper drivers.
    2. What is your version of Windows and the Service pack?
    3. Are you running a 64 bit or 32 bit OS?
    4. What is your Internet browser and version?
    5. Does your system use IDE or SATA disk drives?
    6. What virus protection software and current malicious software do you use? Is up to date?
    7. The issue occurred after an interruption of the power supply as an abnormal termination or power failure?
    8. What has changed recently?
    9. Does this happen often you can effectively reproduce the problem? If you can easily reproduce what steps can you take to reproduce the problem.

    Here is a list of the most common mistakes of the BSOD you can see

    • Stop 0 x 00000003 UNSYNCHRONIZED_ACCESS
    • Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL
    • Stop 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
    • Stop 0 x 00000023 FAT_FILE_SYSTEM
    • Stop 0 x 00000024 NTFS_FILE_SYSTEM
    • Stop 0x0000002E DATA_BUS_ERROR
    • Stop 0x0000003F NO_MORE_SYSTEM_PTES
    • Stop 0 x 00000044 MULTIPLE_IRP_COMPLETE_REQUESTS
    • Stop 0 x 00000050 PAGE_FAULT_IN_NONPAGED_AREA
    • Stop 0x0000006B PROCESS1_INITIALIZATION_FAILED
    • Stop 0 x 00000073 CONFIG_LIST_FAILED
    • Stop 0 x 00000074 BAD_SYSTEM_CONFIG_INFO
    • Stop 0 x 00000076 PROCESS_HAS_LOCKED_PAGES
    • Stop 0 x 00000077 KERNEL_STACK_INPAGE_ERROR
    • Stop 0 × 00000079 MISMATCHED_HAL
    • Stop 0x0000007A KERNEL_DATA_INPAGE_ERROR
    • STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE
    • Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    • Stop 0x0000007F UNEXPECTED_KERNEL_MODE_TRAP
    • Stop 0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED
    • Stop 0x0000009C MACHINE_CHECK_EXCEPTION
    • STOP 0x0000009F DRIVER_POWER_STATE_FAILURE
    • Stop 0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY
    • Stop 0x000000C2 BAD_POOL_CALLER
    • Stop DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000C4
    • Stop 0x000000CA PNP_DETECTED_FATAL_ERROR
    • Stop 0x000000CB DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
    • Stop 0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
    • STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
    • Stop 0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
    • Stop 0x000000D8 DRIVER_USED_EXCESSIVE_PTES
    • Stop 0x000000DA SYSTEM_PTE_MISUSE
    • STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
    • Stop 0x000000ED UNMOUNTABLE_BOOT_VOLUME
    • Stop 0x000000F2 HARDWARE_INTERRUPT_STORM
    • Stop 0x000000F4 CRITICAL_OBJECT_TERMINATION
    • Stop 0x000000FC ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
    • STOP 0x000000FE BUGCODE_USB_DRIVER
    • Stop 0xC0000218 UNKNOWN_HARD_ERROR
    • STOP 0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED
    • Stop 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
    • STOP 0xC0000244 STATUS_AUDIT_FAILED

    This thread is purely an informative thread. If you are experiencing a BSOD error please create a new thread ensure you provide information that questions on this thread.

    While many BSOD errors may be troubleshooting-made the same way, there is an amount of many of them and they should be troubleshoot-carried out on their own.

    If you have anything else you want to add or general BSOD issues then you can post them here, but if you ask about anything that requires real troubleshooting it should be in its own thread.

  • Error 1502: help... can't build my exe

    Hello

    I am stuck and tried all advice warmly 1502 error in order to build an exe from the "RS_Init_SSH2.vi" file in the attached zip.

    I use LabVIEW 2012 and never experience while building exe until I have add this prtoblems vi.

    Note that enabling of mode in the debug compiler makes build ok but the exe resulted in lack of other dependencies and actually leads to more problems on my side.

    I hope that this issue is just one small thing that someone could help me find the cause of this problem.

    Thanks in advance for your support,

    BR,

    BIM

    I'm using LabVIEW 2013 and I have no problem to create an executable file. However, there is still a missing file (command: Cl_ssh_connect.ctl).

    I went down again while LabVIEW 2012 and you can check.

  • Need help to diagnose the regular system analysis on iMac - processors maxed out

    I need help to identify the cause of a problem that occurs at least 2 - 3 times per day using my iMac (27-inch, mid 2010) running 10.11.5.

    I will use my iMac and then all at once things will start to really trolling. To the point of being completely unusable. Even if I'm able to move my cursor, then click to drag the windows around the screen nothing does really.

    I have iStat menus running so that can see graphics in my menu bar that all 4 cores are completely overfished. Occasionally, I was fast enough to launch the activity monitor to try to see what applications / services are responsible for, the use of % CPU column is completely empty of values, so I can't identify the culprits in a reliable way. I try to keep that column sorted by % CPU use in the hope that he could reveal something and normally it's the kernel_task who is up there.

    I use a Wacom Bamboo dated Tablet (MTE - 450 has) instead of a mouse, and at one point, I was convinced the pilot of PenTabletDrive it is based on was to blame. I contacted Wacom on this subject, and although there is no known issues they pointed out that although the latest drivers will allow me to use the tablet that they no longer support older devices. I was wondering if there was a problem of communication between the device and a driver that is no longer supported. I installed the latest driver supported for my tablet, but the problems persist.

    It may be interesting to note that, when my computer is in this semi-frozen state, I am able to launch the window enough force and quit all open applications leaving me with only the Finder. I guess that means that there are none of my apps running and it is probably one of the services. If I restart the Finder system grinds to a completely enclosed holt.

    I hope someone can let me know what I can find in the Console or elsewhere to help me finally zero in on what is to blame. I can share a log if that helps.

    Thank you in advance!

    Information that might be useful:

    Kept by I tend to be running: Adobe InDesign, Photoshop, Acrobat (all CC 2015), Mail, Safari with several tabs & Dropbox sync constantly.

    Download and run EtreCheck, created by one of his own assistants here in CSA. It is a diagnostic tool that is very useful for us to find problems. It will also give us additional specifications on your Mac. After his execution after the logfile here. It will never contain any personal information.

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

  • Help me solve the mystery of The Blue Screen of Death BSOD

    I have a user who knows to randomly BSOD errors.

    After reading another post I have collected the minidump, the msinfo file and config of Dell.   I hope this is the right place to ask these files for further assistance with this issue.  Can you read through these and help me understand what is causing this problem?

    Link to the above mentioned files.

    https://drive.Google.com/folderview?ID=0Bz7KXOfhWjvvY0ZSLUN5VmtwbmM&USP=sharing

    These accidents were related to the corruption of memory (probably caused by a driver).

    Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

    If you are overclocking anything reset by default before running these tests.
    In other words STOP! If you don't know what it means that you're probably not  


    1-Driver Verifier (for full instructions, see our wiki here)
    2-Memtest. (You can learn more about running memtest here)
  • I am trying to install windows xp from the disk, but it hangs during the installation process. no error code. It just hangs. What is the cause and what is the solution?

    I am trying to install windows xp from the disk, but it hangs during the installation process. no error code. It just hangs. What is the cause and what is the solution?

    Hello

    1. at what stage of the installation, the computer crashes?

    2. what operating system was installed on your computer prior to this?

    If you have the similar problem as mentioned in these links, you can follow these links and check if the problem persists:

    Windows XP Setup stops responding (hangs) during the "Preparing Installation" phase

    Windows XP does not meet the Message "Setup starts Windows XP"

    Hope the helps of information.

  • What doesWhat is the cause of the msg blue screen error stop: 0 x 90909220, 0xBF94BAD1, 0 x 00000000, 0 x 00000000?

    Under XP SP3

    As the forums MS Answers does not prompt for any information system 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.

    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?

    What is your Internet browser and version?

    Your system's disks IDE or SATA drives?

    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 genuine XP installation CD bootable, which is the same Service as your installed Service Pack (this 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?

    Your system seems to start OK and then crash or didn't he start not at all?
    Can you make the system crash when you want?  For example, you would say that there is no specific system activity that coincides with the accidents (like watching videos, playing games, etc.).

    The next time your system crashes, provide more information on what you see.

    Here's a BSOD example showing information you provide:
    Send for the nose and the Red arrows (3 to 4 lines total).
    Send all * line STOP message since there are clues in the 4 parameters.
    If there is a name of the file listed in the STOP message, don't forget to include this information too.
    Ignore the boring text unless it seems important to you.  We know what a BSOD looks like, we need to know what your BSOD looks like.
    Now provide more information about your system and data against more recent accidents.
    Click Start, run and enter in the box:
    Msinfo32
    Click on OK and when the system info summary appears, click on Edition, select all, copy, and then paste the information here.
    For information about video drivers, expand components, click view, click on edit, select all, copy and then paste the information here.
    There will be some personal information (such as the user name and the name of the system), and anything that turns information private for you, simply delete the pasted information.
    This will minimize back Q & A and eliminate guesswork.
    Download BlueScreenView here:
    Unzip it and run it (BSV installs nothing) and let him complete the digitization of all your crash dump files.
    If you double-click on depressed, you will get information on it (including the field caused by the driver) and you should be able to spot the problem right away - especially if you see a model in landfills where Caused by field pilot is the same (beginning with this driver).
    BlueScreenView tries to find the right driver or module that caused the blue screen by looking inside the stack of the accident. However, be aware that the driver detection mechanism is not 100% reliable, and you should also look in the lower pane, that display all drivers/modules found in the stack.

    Sometimes BlueScreenView will involve XP files as being the cause of the accident (ntoskrl.exe, win32k.sys, hal.dll etc.) but they are probably not the real cause of the accident (BSV is doing the best he can).  You will need to either pick up some example crashes over and look through them, or find somewhere the XP files are not the 'cause' or you can upload your files to your SkyDrive crash dump and someone with the windows debugging tools can help take a look at them more closely.

    Select (highlight) one or more of the most recent dump files by clicking on them and hold down the CTRL key to select multiple files.  Try to select only the most recent links that relate to your problem (perhaps five or six to start dump files).
    Click on file, save selected items and save information from the dumps to a text file on your desktop called BSOD.txt.

    Open BSOD.txt with a text editor Notepad, WordPad, etc.), select all (Ctrl-A), copy all the text in the Windows Clipboard (Ctrl-C) and paste the text to the Clipboard (Ctrl-V) back here in your next reply.

    Here's an example of report ASB to a single BSOD I initiated on purpose that indicates the cause of the accident as the pilot i8042prt.sys belonging to Microsoft Corporation:

    ==================================================
    Dump file: Mini102911 - 02.dmp
    Crash time: 2011-10-29 04:54:36
    Bug Check String: MANUALLY_INITIATED_CRASH
    Bug check code: 0x000000e2
    Parameter 1: 0x00000000
    Parameter 2: 0x00000000
    Parameter 3: 0x00000000
    Parameter 4: 0x00000000
    Caused by the driver: i8042prt.sys
    Caused by the address: i8042prt.sys + 27fb
    Description of the file: i8042 Port driver
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 5.1.2600.5512 (xpsp.080413 - 2108)
    Processor: 32-bit
    Plant address: ntoskrnl.exe + 22f43
    Stack address 1: i8042prt.sys + 27fb
    Stack address 2: i8042prt.sys + 2033
    Battery 3 address: ntoskrnl.exe + 6e715
    Computer name:
    Full path: C:\WINDOWS\Minidump\Mini102911-02.dmp
    Number of processors: 4
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 94 208
    ==================================================

    Send the information of the last 5 memory dumps (if you don't have 5 memory dumps yet, send the newest, you have).
    While you wait, please follow these steps:
    Perform scans for malware, and then fix any problems:
    Download, install, update and do a full scan with these free malware detection programs:
    Malwarebytes (MMFA): http://malwarebytes.org/
    SUPERAntiSpyware: (SAS): http://www.superantispyware.com/
    They can be uninstalled later if you wish.
    Restart your computer and solve the outstanding issues.
  • In XP, error at startup 'Windows couldn't start. A recent hardware or software change might be the cause.

    Windows could not start. A recent hardware or software change might be the cause. To solve the problem:

    1. Insert your Windows installation disc and restart your computer.

    2. choose your language settings and thenk click 'next '.
    3. click on "repair your computer".

    If you do not have the disk, contact your system administrator or computer manufacturer for assistance.

    File: \Windows\system32\winload.exe

    State 0 xC0000001
    Info: The selected entry could not be loaded because the application is missing or damaged.

    But, instead of file: \Windows\system32\winload.exe I get file: \$Windows.~BT\windows\system32\winload.exe.

    Hi imranhussain1979,

    ·         You have made any changes recently?

    ·         When it was working fine?

    ·         You have Windows XP or a later version of Windows?

    Step 1: The error seems to refer to a later version of Windows. Restart the computer and check if the installed operating system.

    Step 2: Try to start the computer in safe mode and check the number.

    Start your computer in safe mode

    Microsoft Windows XP: start the computer in safe mode

     

    Respond with more information so we can help you best.

Maybe you are looking for