when i open internet explorer we get error message internet explorer stopped working

any luck

Всем доброго дня.

Систему установил начисто, обновил, устанавливаю Google Chrome,  ввожу данные, он зависает приходится перегружать систему, удаляю из браузера расширения, он зависает, изменяю закладки - зависает.

Проверяю на совместимость - не совместим.  Проверил систему на целостность - всё нормально.

Удалить через Панель управления  и  Параметры  -  стандартным способом не получается, хотя очистил браузер, потом отключил все службы,  удалил сначала через Program Files, потом в других директориях вручную.

Подскажите в чём проблема?

위 스크린샷의 오른쪽 상단에 처럼 이 그림이 마음에 드는지 아닌지를 물어보고 바뀌는 기능을 지원 했었고, 재부팅이사 일정 시간 경과에 따라서 늘 다른 잠금화면을 보여 줬었는데 지금은 Windows추천 으로 선택을 해도 사진이 하나로 고정되어 변경이 되지 않습니다.

혹시 크리에이터 업데이트 후 이와같은 증상이 발생하는 것인지도 궁금하고 해결이 가능하다면 해결방법을 알고싶습니다.

자동으로바뀌는 멋진 풍경사진을 보는 즐거움을 MS가 돌려줬으면 좋겠습니다.

Jeg får flere gange dagligt denne fejlmeddelelse : TREAD STUCK IN DEVICE DRIVER.

Jeg kører flere programmer fra iobit.com blandt andet Driver Booster Pro plus HP Support Assistent.

Jeg sørger at holde min bærbare opdateret.

Jeg har haft min bærbare pc siden marts måned 2017.

Styreprogrammet er Windows 10.

Problemet er opstået efter den seneste sikkerhedsopdatering af Windows 10.

I am using a windows 7 desktop.

I do not have any issues with Internet Spades or Checkers, the only issue is with Internet Backgammon.

Basically it errors out in the middle of games. I can't play for more than a few minutes before it happens. Sometimes I will get the error on start up, other times I will get the error mid game. It's extremely annoying.

Anyone have a fix for it?

之前用的是office2003,公司最近換office2016後出現一個怪問題

,直接對著檔案點二下開檔時變要求先"另存新檔",而不是開啟檔

案,但先開word or excel在用開啟舊檔方式就能開啟檔案,先謝謝

各位的幫忙 感激不盡

    Buenas tardes, primera vez que uso la comunidad, espero que puedan ayudarme seré lo mas detallista posible con mi problema.

    Mi computador desde siempre ha sido problemático, todo tipo de problemas tiene.... Por ejemplo no puedo si quiera actualizar las nuevas versiones del SO pues me lanza pantalla Azul y tengo que regresar a versiones pasadas de recuperación SIEMPRE, por ende tengo bloqueado el Microsoft Update. Pero uno de los problemas mas estresantes ocurre con mi conexión WiFi.

   Verán suelo jugar muchos videojuegos online, de todo tipo, pero desde siempre mi pc tiene un cierto problema con cualquier videojuego en linea: Se desconecta del WiFi sola. Mientras estoy jugando sale por ejemplo ¨se perdió conexión intentando renaudar conexión¨, y si minimizo la pantalla veo en la barra de tareas que el símbolo donde esta el nivel de la señal del WiFi aparece desconectado con el asterisco de ¨Hay conexiones disponibles¨, si le doy click e intento reconectar a mi WiFi no me deja, me sale ¨No se pudo reconectar a la red WiFi¨ ¿Como recupero la conexión? pues a juro y por que si tengo que cerrar el juego y ahí me deja reconectarme al WiFi, mas luego volverá a desconectarse.

   He probado muchas cosas, las opciones de rendimiento y energía de mi pc están al máximo, he modificado mil y un veces los procesos que descargan datos del sistema, he descargado de todo tipo de programas, y he visto distintos foros en reddit.... Incluso una de las herramientas mas útiles que he encontrado son los solucionadores de Windows Fix-it, el Fix-it de ¨solucionador de problemas en conectividad web¨ logra mejorar aveces la situación.

Cada vez que intento solucionar los problemas de WiFi con el solucionador Fix-It me sale el mismo resultado:  se encontró un problema con el adaptador de red inalámbrica o punto de acceso--> solucionando problemas-->restituyendo la conexión --> corregido. Esto es lo que siempre arroja de resultados el Fix-It, pero no suele funcionar, y una vez que está corregido si vuelvo a correr el fix-it, aveces me encuentra otra vez el mismo problema y me lo vuelve a ¨corregir¨. Pero usándolo o no, el problema que se desconecta del wifi sigue ocurriendo, aveces arregla la situación pero solo por un rato.

Es demasiado seguido, realmente cada vez que juego ocurre, sin exagerar. Tengo ya como 6 meses con este problema pero últimamente se ha vuelto mas recurrente y sumamente estresante.  La mejor solución que he encontrado es, apagar el pc forzándolo, es decir apagarlo manteniendo el botón de encendido de la maquina, y hacerlo varias veces seguidas: apago el pc, lo enciendo y abro un juego en linea para probar, si en 15 min no se desconecta ¨se arreglo por hoy¨, y si se desconectó vuelvo a forzar el apagado y repito.

¿Que hacer? la verdad no se que hacer, las otras pcs de mi hogar no tienen ningún tipo de problema parecido y están conectadas al mismo WiFi, es mas, puedo jugar en ellas sin este problema, solo que no todos los juegos por que no son computadoras para jugar (Sin Vram).

Mi paciencia esta alcanzando limites alarmantes con mi pc, necesito ayuda.

Salve,

purtroppo ho scordato il pin di accesso allo schermo del mio vecchio lumia 920 senza sim perché rotto. Contiene musica e altro a cui tengo molto. É possibile sbloccarlo da remoto attraverso l'account Microsoft e/o il codice imei? Non voglio effettuare hard reset per non perdere il contenuto. Grazie!

ผมอัพเกรดเครื่องโดยเปลี่ยนฮาร์ดแวร์ใหม่ (CPU/Mainboard) เพราะของเดิมเริ่มรวนเปิดติดบ้างไม่ติดบ้าง

จากนั้นผมก็ทำการ Activate ใหม่ตามคำแนะนำในเว็บไซต์ของ Microsoft

ผมเลือก I changed hardware on this device recently แล้วมันก็ขึ้นเป็นแบบนี้ครับ

ลองหลายครั้งแล้วคือไม่ผ่านครับ ลงชื่อเข้าใช้ใหม่ก็เหมือนเดิม (License ของผมผูกติดกับ E-mail) คือต้องทำยังไงถึงจะผ่านครับ ขอคำแนะนำด้วยครับ

Hi,

Recently I had my laptop sent in for repairs. Ever since I received my laptop back, the sole account on my computer has had no administrative privileges, despite being the only existing account and despite being an administrator. This is very irritating as it means many of the programs I have been trying to use do not work, as they cannot access the necessary files. This has made both work and leisure on my laptop an incredible nuisance.

I don't know what caused this, the previous repairs were to the keyboard so hypothetically it shouldn't have affected my user account. Every fix I've found and tried via Google has been a failure, I've even reset my PC to factory settings with no avail. I've made a new administrator account and that doesn't work, and anything done in safe mode is a temporary solution at best or completely useless at worse. I don't know how to fix this short of sending my laptop away again, which I'd rather not do until I've exhausted every other option.

Thanks.

I have been trying to contact Skype Help to remove a Skype Account.  All I have been led to do is a series of confusing password changes.

Is there a Help Chat, and how do I contact it?

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23572.amd64fre.win7sp1_ldr.161011-0600
Machine Name:
Kernel base = 0xfffff800`0420c000 PsLoadedModuleList = 0xfffff800`0444e730
Debug session time: Fri May 26 12:07:23.639 2017 (GMT+8)
System Uptime: 0 days 1:05:49.323
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdd018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {773bbdaa, 0, ffff, fffff880088c3b60}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KeSynchronizeExecution+3d39 )

Followup: MachineOwner
---------

I am using windows 10 and word 2013

When I check the properties of a file it does not mark the file as read only

These files were not previously read only

Now when I open the file it will not let me edit them as they are read only

I believe the the program crashed at one point.

This is urgent as I have a lot of work and are unable to do anything

Having just upgraded to Office 365 (32 bit) the  above error message appears when I open a split data base.

I have looked at all the suggestions in the previous posts on  this error and tried all the offered solutions. None of which have worked.

The data data base was functioning correctly in Offie 2010 and on a lap top running Office 365.

Have unistalled Office and reinstalled as 64 bit version that did not fix the issue, then reinstalled 32 Bit

Version of Access is 16.0.8067

Have run Microsoft memory check and it found no errors

Specs for PC

Windows 10 Home (x64) Version 1703 (build 15063.296)
Install Language: English (United States)

2.70 gigahertz Intel Core i5-6400
256 kilobyte primary memory cache
1024 kilobyte secondary memory cache
6144 kilobyte tertiary memory cache
64-bit ready
Multi-core (4 total)

8138 Megabytes Usable Installed Memory
Slot 'DIMM 1' has 8192 MB (serial number 14291867)
Slot 'DIMM 2' is Empty

NVIDIA GeForce GT 720 [Display adapter]

***votre sujet a été déplacé dans la bonne section, une autre fois faites attention au choix de votre section***

Bonjour,

ce matin, windows 10 mail m'affiche des comptes vides, comment faire pour retrouver l'ensemble des mails sur ces comptes.

aucun éléments a vous proposer", sur un compte le dernier message entrant c'est affiché mais aucun ancien messages.

4 comptes :

1  : emails retrouvé aprés un bon moment

1 : 1 seul mail entrant, mais les archives n’existe plus

2 :  complètement vides

Je suis inquiet car si j'ai tout perdu !!!!

Merci pour votre aides