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

error

0
0
error 0x80246019 al tratar de actualizar facebook

电脑蓝屏

0
0

 电脑蓝屏求助是不是硬件问题

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


Loading Dump File [J:\020317-8377-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.23569.amd64fre.win7sp1_ldr.161007-0600
Machine Name:
Kernel base = 0xfffff800`04663000 PsLoadedModuleList = 0xfffff800`048a5730
Debug session time: Wed Feb  1 20:32:09.000 2017 (UTC + 8:00)
System Uptime: 0 days 0:15:21.249
*********************************************************************
* 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 \SystemRoot\system32\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
.......
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800629b0bc, fffff880049cd258, fffff880049ccab0}

***** 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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b60bc )

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

Can I find a missing laptop using this site?

0
0
My laptop came up missing. When I log into my account I see where I have added it but it shows up as off. If it is connected to WiFi or a network somewhere will this status change? 

i cant open some things on my computer

0
0

Hello everybody,

I have a problem opening some apps on my computer, I can't open this pc, recycle bin, steam, settings and skype, I reed online that I shold reset my computer but I can't because I can't open the settings, I've faced this problem before with with skype and somehow I managed to make it work, I would like to know what can I do or what should I do? pls help! (windows 10)

Power button

0
0
Hi. Is there any way to make the power button on the surface pro 3 be a long press to turn on? I am sick of accidentally bumping the button or having it tap something and turning itself on. This always happens and when I go to use it it's flat. Worse when travelling with it. Not a great spot for the button actually. 

Office for Mac 2011学生和家庭版更新

0
0
您好,在无法用office自动更新下载新版本后,我又尝试了从微软官网下载新版本的安装包,但是无法安装。系统给出的理由如下

계산기 앱을 실행하면 이 앱의 체험기간이 만료되었습니다. 오류..

0
0

계산기 앱을 실행하면

" 이 앱의 체험기간이 만료되었습니다. 전체앱을 구매하려면 Windows 스토어를 방문하세요. "

라고 뜹니다.

기본앱이라 삭제도 안되고, 여간 불편한것이 아니네요.

어떻게 해결 방법이 없을까요?..

아달〔제주도오피◆홀리◆〕제주도건마{제주도립카페}제주도키스방ロadAL 2닷C O Mロ부천마사지

0
0
〔제주도 오피 오피 홀리 홀리 홀리 홀리 건마 As shown in Fig. 1, as shown in Fig 아달 아달 아달 아달 아달 아달 As shown in Fig. 1, as shown in Fig 아달 아달 아달 아달 아달 아달 As shown in Fig. 1, as shown in Fig 아달 아달 아달 아달 아달 아달 As shown in FigadAL 2닷C O Mロ부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지제주도오피◆홀리◆〔제주도건마〕제주도립카페 제주도키스방}아달{부천마사지

Office 365 message encryption branding

0
0

Hi,

I need to know if it is possible to have multiple message encryption branding under one business. Like users under *** Email address is removed for privacy *** have their message encryption branding while *** Email address is removed for privacy *** has their own? If so, how can proceed with this?

Please let me know my question make any sense.

Thank you,

I need a replacement power cord for my surface 3

0
0
I need a replacement power cord for my surface 3

Word2016 文字化け

0
0

Word2010(Win7)で問題なく表示されていたハングル語の文書(.doc形式)を、Word2016(Win10)で開くと文字化けしてしまいます。

Word2016ではフォントを追加する必要があるのでしょうか。

Encrypted External Drive that cannot be opened.

0
0

Members,

I have an external drive that was encrypted with bitlocker that cannot be opened. When I connect it to my PC, it says the device is working properly but the dialogue box does not appear for me to type my password. The password is correct.

I just don't know the problem.

Can you assist me to open the external drive, decrypt it and get rid of stupid bit locker.

Thank you Team.

meu arquivo de musica tem 1.26'30''

0
0
qual procedimento  pra reduzir o arquivo 1.26'30" para mídea de 80' de música

분당오피▣오로라▣≡분당건마≡아찔한달리기ョ분당립카페ョ분당키스방つ연산마사지つ『Αda L 2. c 0 м 』

0
0
『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지분당오피▣오로라▣≡분당건마≡아찔한달리기ョ분당립카페ョ분당키스방つ연산마사지つ『Αda L 2. c 0 м 』『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ Αda L 2. c 0 м』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지『분당오피▣오로라▣ 』아찔한달리기≡분당건마≡분당립카페つ분당키스방ョ연산마사지

windows10内置应用无法打开

0
0
windows10内置应用无法打开  当前用户是管理员用户  提示如下  所有内置应用都打不开

Microsoft compatibility telemetry

0
0
Microsoft compatibility telemetry 100% disk usage slowing my PC even when it is set at security. How to disable it permanently?

I set up a new outlook email account as my primary. still getting old email and says new account doesn't exist!

0
0

I just set up a new email address but old Hotmail address email is still there. When I try to access the new one, it says it doesn't exist. I try to recheck by redo but it says email already exists...this is why I use Google!

Lumia800商城无法访问且需要刷新

0
0
我才买的 Lumia800,重置了系统,在商场显示要安装“刷新商城”应用,安装并刷新后依然无法连接商城!如何解决

Window 10 (14393.726) run into blue screen when USB network plugged in

0
0
The NDIS connection seems to not work fine.I got disconnected.I have to restart to fix it.My laptop turns into blue screen. 
I guess the reason is D-Link or WiFi.I'm not sure.It still happens sometime, although I turned off WiFi and unplugged D-Link USB before I restart or shutdown window.The same issue on Window 10 Insider.

Windows 10 Insider build 15025怎么在桌面设置显示“此电脑”图标

0
0
请问:Windows 10 Insider build 15025怎么在桌面设置显示“此电脑”图标?
Viewing all 1237219 articles
Browse latest View live


Latest Images