Меню

A process or thread crucial windows 7

BSOD: «A process or thread crucial to system operation has unexpectedly exited or been terminated». Startup Repair does Not fix the problem — — —

I recently had a severe virus infection on my Windows Vista SP2 Gateway laptop. After running the AVG virus cleaner, which appeared to have had to quarantine and/or delete some infected system files, I could no longer Boot Windows up on that machine — even in (all flavors of) Safe Mode. When attempting to boot up, I’d get

a Blue Screen of Death with the error msg indicated in the title to this thread. Before putting out the Crash dump, the system indicated:

«*** STOP: 0x000000F4 (0x00000003 0x85F22848 0x85F22694 0x82A26AB0)»

Other messages in the BSOD indicated that I might have new HW which was causing the BSOD (I didn’t — but nevertheless I removed all external HW and tried again — got the same result).

So, one of the first things i did was to capture the boot log so i could see what drivers were hanging up / Not Loading. Here is what I found:

(1) The last driver to load (as shown in ntbtlog.txt) was monitor.sys. My understanding is that this indicates that when this driver loaded, the system crashed at that point — implying there is «something wrong» with that particular driver. However, that doesn’t seem likely, as I can use the (built-in) screen/monitor for the laptop without a problem.

(2) Several Drivers did NOT Load: they are:

QUESTION 1: Since «monitor.sys» was the last driver to load, should I assume that is the driver the system hung up on (i.e., that caused the BSOD)? And if so, does that imply I should replace that driver? If so, how do I do that (where/how do I get a «Clean/good» copy of monitor.sys)?

QUESTION 2: Is there some way to go get «good versions» of the drivers I listed above that did NOT load (I am assuming they did Not load because they were corrupted by the virus and/or the virus cleaner, or perhaps simply deleted by the virus cleaner because they were infected) to put into the Windows\System32\Drivers directory? How?

So here are the steps I took to try and remediate the «corrupted system». I inserted my Windows Vista DVD into the DVD drive and loaded Windows using that.

Once that came up, I then tried the following (and here are the results for everything i tried):

(1) I selected the «Repair» option, then selected «Microsoft Windows Vista» OS, and hit «Next». It tried «attempting repairs» for 15 minutes or so, then finally ceased with a message: «Startup Repair cannot repair this computer automatically. Problem details indicated: (a) Problem Event name: StartupRepairV2»; Signature 01: ExternalMedia; Signature 02: 6.0.6000.16386.6.0.6001.18000; Signature 03: 6; Signature 04: 131074; Signature 05: 0xF4; Signature 06: 0xF4; Signature 07: 0; Signature 08: 2; Signature 09: WrpRepair; Signature 10: 5; OS Version: 6.0.60090.2.0.0.256.1

(2) I then selected the option to «View Diagnostic and Repair Details». It indicated that all the tests done completed successfully (Error code = 0x0), and

then indicated the «Root Cause»: «Unknown Bugcheck: Bugcheck f4, Parameters = 0x3, 0x88607b80, 0x88607ccc, 0x82a78ab0.

Repair action: System files integrity check and repair. Result: Failed. Error Code = 0x5

(3) I checked System Restore, and even though i know I had some Restore Points originally created for that system, System Restore indicated that there weren’t any Restore points to go back to, (leading me to believe the virus must have killed them)

(4) So I chose the selection «Command Prompt», which opened up defaulting to «X:\Sources>». I switched to C:, and then typed in: «sfc /SCANNOW». The system responded with the following messages:

«Beginning system scan. This process will take some time»; followed 30 seconds later by the message:

«Windows Resource Protection could not perform the requested operation»

MAIN QUESTION: any thoughts on what other tools and options I have to try and repair the windows installation / driver set??

Источник статьи: http://answers.microsoft.com/en-us/windows/forum/all/bsod-a-process-or-thread-crucial-to-system/96467de6-ed0e-4abd-9ba8-ad2511742d51

Lots of BSODs -win7 — Process or thread crucial to system operation has unexpectedly exited

I have been getting BSOD s, at least weekly, with a variety of error messages. Most recent (& most common): kernel_data_inpage_error

  • today it involved partmgr.sys
  • 3 days ago- involved win32k.sys

I am sure you need much more information. Let me know and I’ll get it to you. Be gentle with me. I’m a newbie.

Replies (2) 

Please post copies of the latest dump files as a shared file to your Sky Drive and post a link here.

Hope this helps, Gerry Cornell

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Check this thread for information using BlueScreenView, MyEventViewer and other methods
to troubleshoot BlueScreens — top 3 replies (+1 other).

We can analyze the minidumps if you make them available from the SkyDrive or other file
sharing sites.

Zip or upload the contents of C:\Windows\minidump

Also do this so you can see the likely bluescreens.

Windows Vista automatically restarts if your PC encounters an error that causes it to crash.
(also Windows 7)
http://www.winvistatips.com/disable-automatic-restart-t84.html

Check with these utilities to see if any information can be gathered :

This is an excellent tool for posting Blue Screen Error Information

BlueScreenView — Free — scans all your minidump files created during ‘blue screen of death’
crashes, and displays the information about all crashes in one table.
http://www.nirsoft.net/utils/blue_screen_view.html

MyEventViewer can be checked at the time of the BlueScreen (BSOD) to within a second or
so of the time of the BSOD to provide more information as to possible cause — see TIP.

MyEventViewer — Free — a simple alternative to the standard event viewer of Windows.
TIP — Options — Advanced Filter allows you to see a time frame instead of the whole file —
set it to a bit before and after the time of the BSOD.
http://www.nirsoft.net/utils/my_event_viewer.html

AppCrashView — Free — a small utility for Windows Vista and Windows 7 that displays the
details of all application crashes occurred in your system. The crashes information is extracted
from the .wer files created by the Windows Error Reporting (WER) component of the operating
system every time that a crash is occurred. AppCrashView also allows you to easily save the
crashes list to text/csv/html/xml file.
http://www.nirsoft.net/utils/app_crash_view.html

Rob Brown — Microsoft MVP Rob Brown — Microsoft MVP — Windows Insider MVP 2016 — current
Microsoft MVP Windows and Devices for IT 2009 — 2020

Источник статьи: http://answers.microsoft.com/en-us/windows/forum/all/lots-of-bsods-win7-process-or-thread-crucial-to/f29f279b-198b-496a-9c45-a2e04604302c

Blue Screen error: «A process or thread crucial to system operation has unexpectedly exited or been terminated» system Hand no minidump

Replies (3) 

Without a minidump there is not a lot we can do. Checking with WD Support as well as Intel
would be very good moves.

Please double check your settings here :

Control Panel — System — on left side Advanced System Settings — Advanced tab —

Startup and Recovery — Settings — System Failure — check the box to Write an Event to System Log

make sure the Write Debugging is set to small minidump

and the default folder should look like %SystemRoot%\Minidump.

You can do a lot of troubleshooting just by noting the Bug_Check or Stop Code displayed on
the BSOD and the other information provided in it.

Check this thread for information using BlueScreenView, MyEventViewer and other methods
to troubleshoot BlueScreens — top 3 replies (+1 other).

We can analyze the minidumps if you make them available from the SkyDrive or other file
sharing sites (such as MediaFire). If you have problems uploading the minidumps copy
them to the Desktop or the Documents folder and upload them from there.

Zip or upload the contents of C:\Windows\minidump

Also do this so you can see the likely bluescreens.

Windows Vista automatically restarts if your PC encounters an error that causes it to crash.
(also Windows 7)
http://www.winvistatips.com/disable-automatic-restart-t84.html

Check with these utilities to see if any information can be gathered :

This is an excellent tool for posting Blue Screen Error Information

BlueScreenView — Free — scans all your minidump files created during ‘blue screen of death’
crashes, and displays the information about all crashes in one table.
http://www.nirsoft.net/utils/blue_screen_view.html

MyEventViewer can be checked at the time of the BlueScreen (BSOD) to within a second or
so of the time of the BSOD to provide more information as to possible cause — see TIP.

MyEventViewer — Free — a simple alternative to the standard event viewer of Windows.
TIP — Options — Advanced Filter allows you to see a time frame instead of the whole file —
set it to a bit before and after the time of the BSOD.
http://www.nirsoft.net/utils/my_event_viewer.html

AppCrashView — Free — a small utility for Windows Vista and Windows 7 that displays the
details of all application crashes occurred in your system. The crashes information is extracted
from the .wer files created by the Windows Error Reporting (WER) component of the operating
system every time that a crash is occurred. AppCrashView also allows you to easily save the
crashes list to text/csv/html/xml file.
http://www.nirsoft.net/utils/app_crash_view.html

Rob Brown — Microsoft MVP Rob Brown — Microsoft MVP — Windows Insider MVP 2016 — current
Microsoft MVP Windows and Devices for IT 2009 — 2020

Источник статьи: http://answers.microsoft.com/en-us/windows/forum/all/blue-screen-error-a-process-or-thread-crucial-to/04596c22-4f0d-4cff-939c-fa7e145bcf52


Adblock
detector