zeezam Posted November 2, 2011 Share Posted November 2, 2011 Have a fresh windows 7 64bit install on a lenovo x200s.Got bsod when doing some ftp transfer for example.Here is the event logLog Name: SystemSource: Microsoft-Windows-WER-SystemErrorReportingDate: 2011-11-02 18:32:34Event ID: 1001Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: noneDescription:The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000030, 0x0000000000000002, 0x0000000000000000, 0xfffff8800584a394). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110211-20592-01.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-11-02T17:32:34.000000000Z" /> <EventRecordID>4882</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>none</Computer> <Security /> </System> <EventData> <Data Name="param1">0x000000d1 (0x0000000000000030, 0x0000000000000002, 0x0000000000000000, 0xfffff8800584a394)</Data> <Data Name="param2">C:\Windows\MEMORY.DMP</Data> <Data Name="param3">110211-20592-01</Data> </EventData></Event>Memory problem? Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted November 2, 2011 Share Posted November 2, 2011 compress the file C:\Windows\Memory.dmp to 7z (ULTRA, LZMA2) and upload it to mediafire.com and post a link here. Link to comment Share on other sites More sharing options...
zeezam Posted November 3, 2011 Author Share Posted November 3, 2011 (edited) compress the file C:\Windows\Memory.dmp to 7z (ULTRA, LZMA2) and upload it to mediafire.com and post a link here.Here you go,http://www.mediafire.com/?pwdgds35judmws9Edit:I ran the MEMORY.DMP in WinDbg and got following:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\sys\Desktop\MEMORY.DMP]Kernel Summary Dump File: Only kernel address space is availableSymbol 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 (2 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506Machine Name:Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c56670Debug session time: Wed Nov 2 22:04:27.235 2011 (UTC + 1:00)System Uptime: 0 days 3:32:18.827********************************************************************** 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 SymbolsLoading unloaded module list......******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck A, {0, 2, 0, fffff80002ffc477}*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll - *** ERROR: Symbol file could not be found. Defaulted to export symbols for ndis.sys - *** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys*** ERROR: Symbol file could not be found. Defaulted to export symbols for vwififlt.sys - *** ERROR: Module load completed but symbols could not be loaded for nwifi.sys*** ERROR: Module load completed but symbols could not be loaded for pacer.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 ****** ****************************************************************************Probably caused by : NETw5s64.sys ( NETw5s64+b76b )Followup: MachineOwner---------Seems to be the wifi driver?I updated the Intel driver to 13.5.0.6 and then ran a ftp transfer like before when I got bsod and now it seems to work.I'll update the thread if I got bsod again... Edited November 3, 2011 by zeezam Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now