Quantcast
Channel: Microsoft Community - Super Fresh
Viewing all 1237628 articles
Browse latest View live

【求助】笔记本cpu被锁频

$
0
0
只买了3个月的笔记本,重装系统之后 cpu很容易被锁频  一直是0.38GHz

satisfecho

$
0
0

ESTOY DANDO LAS GRACIAS ETERNAS A LA (S) PERSONAS QUE SE TOMARON EL TIEMPO EN LEER MIS CORREOS Y CONTESTAR.

QUE MAS TRANQUILO, GRACIAS NUEVAMENTE.

SOLO ME QUEDA LA DUDA : DE SI EN ALGUN MOMENTO ESAS FOTOS DE PODRAN ELIMINAR. YA ESAS FOTOS MIAS QUE ESTAN EN "FOTOS", YO JORGE, JAMAS LAS ENVIE POR CORREO A ALGUN CONTACTO Y MUCHO MENOS LAS RECIBI POR CORREO. DE MI CARPETA DE "IMAGENES APARECEN EN "FOTO". EN FIN, GRACIAS.

Notepad

Enquiry

$
0
0

Hi there, I’m just enquiring for my 9 year old Son, whom is looking for an Appropriate Western Game for the Xbox 1, if there is one that doesn’t have blood when playing as he gets really freaked out about it! Any suggestions please, he loves Action and Adventure Games! Cheers Dee 😊

鼠标变成了一个亮圈

$
0
0

鼠标变成了一个圈。就是这个中间这个亮圈

Machine policy value 'DisableUserInstalls' is 0

$
0
0
i have windows 7 professional how do i fix this

No more Xbox home reset help

$
0
0

I have a problem where someone hacked my account and used home Xbox resets on my account in November 2017. I need my Xbox home account set to my account now I can’t play my games as I just worked very hard to get a Xbox. My brother who left to collage he took my Xbox without telling me. I had to get a job with my grandpa. Now I have digital games I can’t play. Please help me out I can’t play the games I love. Thanks for you time.

onenote移动端字体和设置的不一致

$
0
0

OneNote 移动端和PC端设置的字体都是仿宋  字体11 

在移动端输入的时候,刚开始两个字是仿宋,后面就变字体了,像是黑体 。但是在设置里还是仿宋,请问这个怎么修改?


微软拼音浏览器中文输入bug

$
0
0
我的默认输入语言为中文,但是在浏览器中,每新建一个窗口,输入法就会跳回英文,每打开一次网页都得调整一次输入法,只是在浏览器中出现这个问题。如何解决这个问题

where do I find "settings and more" as advised in the "Tips" included in the latest update.

$
0
0
where do I find "settings and more" as advised in the "Tips" included in the latest update.

Pantalla Azul Codigo: MEMORY_MANAGEMENT

$
0
0

Desde unos par de días mi pc comenzó a apagarse de forma inesperada y salia la pantalla azul y me decía "tienes un problema... se reiniciara tu pc " 

Después de eso comenzó a aparecer cada rato la misma cosa y se comenzó a crashear mi pc saliendo cuadros negros en la pantalla cuando aparecía la pantalla azul y me ponía ve a tal pagina de STOPCODE y me salia el código MEMORY_MANAGEMENT después de eso comense  a actualizar mi pc...... Formateandolo como 3 veces pero igual seguía el problema

 

y bueno eso es todo y espero que halla una solución 

Gracias                                                                 :)

Vungle advertising on your free Solitaire game

$
0
0

Vungle advertising on your free Solitaire game has ruined it for me.  I am an old retiree and am not going to pay to stop advertising. The Paradise Island 2 advertisement is so intrusive and takes over everything so that I would never consider buying it or any other game that intrudes on the solitaire game I am playing.  I will just play a different version on my Ipad instead and to hell with Microsoft x-box all together.

Wwe

$
0
0

dear xbox, 

Thank you for adding gta San Andreas and midnight club L.A. to the xbox one backwards compatibility list. Would you guys consider adding some wwe games to the list as well

MAJ de Windows Defender, et des Notifications constantes du Centre de Fonctions Sécurité de Windows Modifications Protections des virus et menaces

$
0
0

Bonjour, 

Est-ce que je peux supprimer les MAJ de la définition Windows Defender Antivirus KB2267602 total 32 du 12 juin à aujourd'hui 11 juillet 2018. ?

Est-ce qu'on peux désactiver Protections des virus et menaces 

Modification non autorisée bloquée

L'accès contrôlé aux dossiers a empêché ...

C:\Programme …\You Cam 7.exe d'apporter des modifications au dossier %userprofile%\Documents

C:\Programme …\OLRStateCheck.exe d'apporter des modifications au dossier %userprofile%\Documents

C:\Programme …\VLC.exe d'apporter des modifications au dossier %userprofile%\Documents

Ces notifications apparaissent 10 fois par jour si non plus.

Comment procéder pour ne plus recevoir ces notifications ? ou réparer ?  Merci

在安卓版的Word、Excel、PowerPoint无法看到别人的OneDrive共享给我的文件夹里的子文件夹和文件,安卓版的OneDrive里能够正常看到,请问该怎么解决?

$
0
0

最近更新的了安卓版的WordExcelPowerPoint以后,发现原来可以看到别人的OneDrive共享给我的文件夹和文件

,现在只能看到文件夹,文件夹里的面的子文件夹和文件都看不到,显示为“此文件夹是空的”。但是在OneDriveApp里能正常看到所有别人共享给我的文件夹和文件,且能够通过OneDrive App调用WordExcelPowerPoint打开相应的文件。请问这是怎么回事,应该怎么解决?之前的旧版的WordExcelPowerPoint App是可以正常看到并打开别人共享的文件的。

App版本:

Word1.0.116.0.10325.20043

Excel1.0.116.0.10325.20043

PowerPoint1.0.116.0.10325.20043


怎么关闭显卡驱动的自动更新

$
0
0

有一张来路不明的显卡,只能使用旧版本的驱动,但是win10每次版本更新的时候都会带着驱动一起更新了,导致显卡无法使用。

每次都要手动卸载然后安装旧版真的很麻烦。尝试过网上所有方法都不能单独关闭某个硬件驱动更新。

outlook2013에서 메일 발송시 첨부한 파일이 수신자측에서는 winmail.dat으로 첨부되어 수신됨

$
0
0

회사 오피스 2013을 통해서, 아웃룩 2013을 사용중입니다.

메일형식을 html또는 서식있는 텍스트로 발송시 메일 수신자 측에서 첨부파일이 winmail.dat으로 보이는 현상이 최근 빈번히 발생하고 있습니다.

동일버전 아웃룩을 사용하는 다른 pc는 예전에 그런일이 잦았지만 저는 괜찮은편이 었는데,,,제 아웃룩도 이제 거의 그런일이 발생합니다.

해결 방법이 없을까요?   os은 윈도우7입니다.

WIN10系统 1709版本 使用中出现蓝屏BAD_POOL_CALLER

$
0
0

WIN10系统 1709版本 使用中出现蓝屏BAD_POOL_CALLER

请帮忙分析问题原因

谢谢


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+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`42219000 PsLoadedModuleList = 0xfffff800`42585130
Debug session time: Wed Jul 11 23:32:16.040 2018 (GMT+8)
System Uptime: 0 days 1:35:32.884
*********************************************************************
* 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+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {4, 0, 0, ffffd30182a21978}

Unable to load image ndis.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
Unable to load image mfefirek.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfefirek.sys
*** ERROR: Module load completed but symbols could not be loaded for mfefirek.sys
Unable to load image fwpkclnt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fwpkclnt.sys
*** ERROR: Module load completed but symbols could not be loaded for fwpkclnt.sys
Unable to load image NETIO.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
***** 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 : hardware_ram ( PAGE_NOT_ZERO_VISTA )

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

 *** Memory manager detected 94476 instance(s) of page corruption, target is likely to have memory corruption.

Question if I wanted to delete all changes

$
0
0
Split from this thread.

I have same problem.

Saved xls file on OneDrive account and closed on 7/7/2018.

File shows on File Explorer as synced.

When opened on today got same message and question if I wanted to delete all changes.

I answered no and save as temp file.

Used Spreadsheet Compare to compared file with temp file.  There are no differences.

I have had this happen before.  Why does this happen.  It's a pain to verify that nothing is lost everytime I get the message.

Bob

50% Increase in CPU Usage after Installing Any Windows 10 1803 Cumulative Update released June 12 or Later

$
0
0

Hello,

After I installed the first Cumulative Update released in June (17134.112), I noticed a significant increase in overall CPU usage and terrible performance; instead of taking a couple seconds to open Microsoft Edge, it took nearly a minute, and instead of quickly typing up a search and getting results within half a second, I had to wait for 30 seconds for the typed characters to show up, and when loading up the search results, Edge stopped responding for 10 seconds. I didn't know what was going on, so I reinstalled Windows 10 (after putting all personal files onto a separate partition).

After I reinstalled Windows 10 1803 (17134.1), I installed the Cumulative Update (17134.112) again and had the same problem. I took further note this time that Desktop Window Manager, Diagnostic Policy Service, UtcSvc, and the Connected Device Service were all using CPU when they didn't use much if any at all prior to the Cumulative Update. I uninstalled the Cumulative Update, and CPU usage returned to normal. I installed the May 2018 Cumulative Update (17134.81), and CPU usage remained the same. I know that 17134.83 also doesn't have the problem since that was what I was running prior to reinstalling Windows 10, but when I was going through the Microsoft Update Catalog, I didn't spot it for some reason.

I have also installed (and promptly uninstalled) the third June Cumulative Update (17134.137) and now the July Cumulative Update (17134.165) as both had the same problem. I did some math with the July update, though, and found that, besides the fact that almost twice the number of System Executables/Services were using CPU, but CPU usage by all programs using CPU is increased by about 50%. That's an average, but when you look at programs, it's more like double. Edge, which uses ~15% idle (looking at a website) and ~45% loading a website, uses ~35% idle and ~70% when loading a website.

As I have said before, I have uninstalled the Cumulative Updates all three times, and the problem was resolved immediately afterwards all three times. DISM and SFC have been unable to solve the problem. I am thinking that there may be a driver incompatibility issue that the June Cumulative Update (17134.112) caused. However, I would have no way of knowing since none of my drivers have updated in the process of updating to the Cumulative Updates. I am running on an HP Elitebook 745 G2 Notebook PC (for those who want PC specs). These Cumulative Updates have important security updates that I would like to have on my system, but as long as this performance issue exists, I cannot update beyond 17134.83. I am open to any suggestions as to what may be causing this issue on my machine as I have only seen one or two other people report this problem.

Thank you,

Benjamin

Viewing all 1237628 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>