Fix Powershell has stopped working error

[theovencook]

Hi there, when I'm using my Windows 7 Home Premium 64bit computer; and when using it (in general, not noticed it to happen at any specific time) an error message shows up saying "Powershell has stopped working" followed by "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" although when confirming to close the program, no solution is found by windows.
This error message will pop up every few seconds, and even if I don't confirm to close the program, multiple error messages will continue to appear.
During general use of my computer there doesn't seem to be anything wrong with it (although I'm not entirely sure what Powershell does) - the only annoyance is that the message continually shows up.

Is anybody familiar with this error and how to solve it? or how I can get more information about the error to give to you.

Many thanks, Toby.

 

[JDobbsy1987]

Hi and Welcome to SevenForums,

I would try a system file check - http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

If that doesn't help, take a look here and see if this helps - Windows Powershell has stopped working

Regards,
Jamie

 

[A Guy]

If the SFC Jamie suggested does not help, next time it happens, open the Event Viewer and see if you can find an error relating to Power Shell, and copy the full error info here

http://www.sevenforums.com/tutorials/226084-event-viewer-open-use-windows-7-a.html

A Guy

 

[iicarJohn]

Powershell has stopped working

After some 30-plus hours cleaning my computer while it was working(?) rather slowly ... and after many lengthy re-boot processes after encouraging it to accomplish several updates that it had not yet incorporated, I finally found that uninstalling a Windows update that reportedly "failed" (three times!) ... but which was actually present, seems to have resolved the issue. In my case, it was an update labeled "KB2952664". The installation failed twice in August and "failed" again on October 15, 2014. I have a few others that have "failed" as well, but removing KB2952664 and then re-installing it seems to have resolved my problem ... for the last several moments.

I have a Lenovo Model 4311 running an AMD Turion II P560 (64-bit, 4.0GB Ram) and Windows 7 Home Premium with Service Pack 1 installed.

Oddly enough, a couple of "failed" automated update installations are not even showing up on the MS website as updates ... so far. There is more to do?

Edit: OK, "Improved dramatically" would be accurate. Not entirely resolved, however. There is more to do!

 

[Airway911]

Hi Everyone!

I found this forum because I too am getting the error that powershell has stopped working, and I Googled solutions. So far I have completed the system file check as suggested by Jamie and no problems were found. I looked in system events for anything related to powershell. I found numerous entries. Here is the information from the most recent. Please direct me on what to do next. Thank you.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-12-05T20:21:25.000000000Z" />
<EventRecordID>230797</EventRecordID>
<Channel>Application</Channel>
<Computer>Larissa</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>0</Data>
<Data>PowerShell</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>powershell.exe</Data>
<Data>6.1.7601.17514</Data>
<Data>System.AccessViolationException</Data>
<Data>System.AccessViolationException</Data>
<Data>tem.Management.Automation.MethodInformation.Invoke</Data>
<Data>t.Invoke</Data>
<Data>Pipeli..ution Thread</Data>
<Data />
<Data />
<Data />
<Data />
<Data />
<Data />
<Data>0</Data>
<Data>310da7e3-7cbc-11e4-9164-685d43f20bc4</Data>
<Data>0</Data>
</EventData>
</Event>

 

[ljmartin]

ok i had this problem and found this solution in windows and it actually repaired it.
yes the OS files can be fixed. [most of the time]
many times you can fix your os problems yourself.
a C&P
Check your hard disk for errors

You can solve some computer problems and improve the performance of your computer by making sure that your hard disk has no errors.

1. Click to open computer.
   
   Right-click the hard disk that you want to check, and then click Properties.
2. Click the Tools tab, and then, under Error-checking, click Check now.
   
   If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
   To automatically repair problems with files and folders that the scan detects, select Automatically fix file system errors. Otherwise, the disk check will report problems but not fix them.
   To perform a thorough disk check, select Scan for and attempt recovery of bad sectors. This scan attempts to find and repair physical errors on the hard disk itself, and it can take much longer to complete.
   To check for both file errors and physical errors, select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors.
3. Click Start.

Depending on the size of your hard disk, this might take several minutes. For best results, don't use your computer for any other tasks while it is checking for errors.

Note

• If you select Automatically fix file system errors for a disk that is in use (for example, the partition that contains Windows), you'll be prompted to reschedule the disk check for the next time you restart your computer.
  
  Yes I selected to auto fix and it rescheduled to run on start up.
  I restarted and it ran and it fixed this issue with power shell.
  
  personal note* IMO it is good to run the other system tools to defrag on a regular basis.
  on previous win versions I ran these on my machine about every 90 days as I use my PC daily.
  on repairing others PC's - I do it almost every time they call me out. and most times it fixes it for me.