Hello,
Once again at this period of the year I'm running into computer problems compbash2.
This time, it is a BSOD that triggers from time to time, not at every session of Windows (7), but often enough to be a pain.
I run the 64 bits version of Win7 on a AMD Athlon II X2 245 (64+), so things are rather straightforward there, should be perfectly compatible.
I've searched around the Web and found that my error code (x0...01A) means that a "severe memory error occured". Riiight.
That doesn't seem related to a particular program. Sometimes the BSOD occured right on Windows boot (after the BIOS & "pseudo-MS-DOS" checks).
By "memory" I guess they mean RAM. I have 4GB installed in a "2*2" configuration. DDR3 if I remember well, for what that matters.
I tried to help myself and installed the Windows Debug Tools. Hoping to get an insight on what is going wrong, I tried to open the Crash Dump File and here is what I got :
It seems that something is wrong on the debugger itself. :beathead:
So I'm taking advices on :
- 1) what can be wrong on the computer crystalball
Needless to say, the memory checkup at startup is running perfectly, every byte is present and accounted for. I've read several forums and saw that basic reactions to similar problems were "it must be your RAM chips, try to switch them etc...", but I feel very confident that the problem isn't there. If there was an hardware fault, IMHE (Experience), it would rather come from the Motherboard.
On the software side there is nothing obvious I installed and that could cause that mess.
- 2) how to get that buggy debugger working correctly !
Thank you, any help getting out of that blues would be very much appreciated. :tiphat:
Once again at this period of the year I'm running into computer problems compbash2.
This time, it is a BSOD that triggers from time to time, not at every session of Windows (7), but often enough to be a pain.
I run the 64 bits version of Win7 on a AMD Athlon II X2 245 (64+), so things are rather straightforward there, should be perfectly compatible.
I've searched around the Web and found that my error code (x0...01A) means that a "severe memory error occured". Riiight.
That doesn't seem related to a particular program. Sometimes the BSOD occured right on Windows boot (after the BIOS & "pseudo-MS-DOS" checks).
By "memory" I guess they mean RAM. I have 4GB installed in a "2*2" configuration. DDR3 if I remember well, for what that matters.
I tried to help myself and installed the Windows Debug Tools. Hoping to get an insight on what is going wrong, I tried to open the Crash Dump File and here is what I got :
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081713-16114-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0xfffff800`02e4f000 PsLoadedModuleList = 0xfffff800`030926d0
Debug session time: Sat Aug 17 20:38:55.426 2013 (UTC + 2:00)
System Uptime: 0 days 0:08:06.799
*********************************************************************
* 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
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8000009510, ffff, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 : ntoskrnl.exe ( nt+75b80 )
Followup: MachineOwner
---------
So I'm taking advices on :
- 1) what can be wrong on the computer crystalball
Needless to say, the memory checkup at startup is running perfectly, every byte is present and accounted for. I've read several forums and saw that basic reactions to similar problems were "it must be your RAM chips, try to switch them etc...", but I feel very confident that the problem isn't there. If there was an hardware fault, IMHE (Experience), it would rather come from the Motherboard.
On the software side there is nothing obvious I installed and that could cause that mess.
- 2) how to get that buggy debugger working correctly !
Thank you, any help getting out of that blues would be very much appreciated. :tiphat: