MEMORY_MANAGEMENT BSOD Windows 8.1

Toggle sidebar Toggle sidebar
U

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815
I know I have a thread open on this somewhere, but I'm just going to post this one.

Tried sleep mode again, got another blue screen, different error. it was Memory_Management this time. It's funny how when Windows messes up, which at least for me is very often (and I don't tinker with any settings or even touch anything, just use it the way it was intended) I don't even act concerned or angry, I just go 'eh, Windows' and Windows 7 was better, but reliability was an issue there too for me. With Vista I remember having only one issue one time and that was it until a virus took it down. 8.1 , as proven by my post history, constant problems and 7 less issues but recurrent ones (OEM laptop). That actually makes Vista the more reliable one :O, as reliable as OSX in my experience

How do I fix the sleep mode BSODs. It's been doing this since day 1 twelve months ago. My RAM was fine then when it was tested and is still fine today. XMP is on in the BIOS to get 1600 MHz. To be honest I can't even be bothered to fix it, because I guarantee something else will break within Windows soon, I'm overdue for nuking the drive and reinstalling the OS actually
 
Solution
J
if you are getting a bugcheck, it is best to put your memory .dmp file on a cloud server so it can be looked at in a windows debugger.
generally bugchecks during low power states are caused by:
BIOS bugs, and 3rd party hardware device drivers and actual bugs in the electronics of some hardware.
Generally, windows 7 has the low power states turned off by default, windows 8.x turn them on and many hardware devices actually fail due to bogus electronic circuits in the device. Many OEMs have put out new drivers to "fix" the problem by disabling the features.

Also, the default TP link driver that was provided to microsoft corrupts memory and will cause a whole range of bugchecks for you. if you use that driver you must: updtate the...
Sort by date Sort by votes
A

Alec Mowat

Honorable
Jan 8, 2014
3,244
0
13,460
The issue is probably hardware related. It's fun to blame others for your problems, but you should always look in the mirror first. Windows NT 6 (Vista, 7, 8, 8.1 and 10) has been relatively stable since the original release of Vista. BSOD usually points to bad hardware, or bad drivers. If it was OS related, everyone would be getting the same issue, which is not the case.

Sounds like an issue either reading your RAM, or reading the data your RAM dumps to your hard drive.
I'd run a memtest 86 for a few passes and see how it goes. I'd also run a check on your harddrive with HD Tune.

You should post you're full system specs as well.
 
Upvote 0 Downvote
U

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815


I'm not ruling out hardware, but all I know is:
Memtest 86 has already tested this RAM and passed it. Windows itself has tested it and passed it. This has been done multiple times if I remember right and it has passed every time

Hard Drives have all been tested and they have passed. One did fail the very first time, it was retested and passed and has done ever since

CPU has been tested for over 12 hours straight and has passed without problem

GPU has been tested using Furmark and other tools, it also passed and yet I get random graphics issues (incredibly rare and only during boot) which also happened with the old 760 which also passed the same tests. I don't bother looking into them because I can't be bothered any more, because something else will break. Most likely candidate, MS Office since that used to give me trouble back in the day, no such problems on OSX though which is weird when you think about

Thing has been checked for viruses and malware, it's clean and yet there's a different set of issues with each install

Just of the top of my head what I've had since this was built 12 months ago:
- Multiple corruptions found using DISM. Repeated problems. Finally fixed by, I don't know, because even using Restore health it would still reoccur
- One hard freeze
- Multiple losses of sound. Cause identified to be Realtek not working well with 8
- Graphics corruption on Windows 8 splash screen
- Multiple sleep mode BSODs. Cause still unknown
- Windows failing to gauge where my screen starts and ends
- MS Word crashing when saving
- Explorer.exe crashing
- The memory cannot be read bug at shutdown. Known bug within 8 that MS never fixed
- Apps not opening
- Apps losing settings (see my post on mail the other day). Don't use this app anymore. Windows Live Mail replaced it but says Not Signed In. Network Unavailable. When signed in it fails to retrieve mail anyway. Then explain why my Mac and my Android phone on the same network have no issues getitng mail
- Windows itself losing settings. Most recently my printer disappeared for unknown reasons. Guess what? My Mac never lost it, so I printed from there instead. Since reinstalled
- New user accounts defaulting to a black wallpaper like it failed to load up one of the defaults.
- Safe Mode with Networking taking literally one hour plus to start. Fixed, because Windows decided it would work for once
- The install disc refusing to start. Those were scary times. Not that it would work anyway, because it always says can't do anything
- Reactivation requests after CHK DSK on drive D
- And a tonne of other

^ This is why I don't bother with it any more (and why I have a Macbook that sees more use than this ever does, other than watching videos and playing music. The PS4 covers me for gaming) and why I don't do any maintenance on it any more.. Somewhere between all that it does actually work. I never have any trouble gaming. It passes POST, otherwise it wouldn't actually start.. Between the 360, 7 and 8.1 MS' track record with me has been unacceptable whereas with other vendors (Sony and Apple) I'm not spending half my time fixing what should be working in the first place or any issues are fixed relatively quickly and don't come back. Anyway rant over (the more I type this, the angrier I'm getting :p).

Spec:
https://www.youtube.com/watch?v=_d3L8E0n3KA

If you don't want to watch the vid with my spec in it
CPU: 4570 i5
GPU: GTX 780
Board: Gigabyte GA H87 HD3
PSU: Antec TP 750 W 80+ Gold
SSD: 840 Evo 120 GB
HDD: 2TB WD Black, 2TB WD Green
Memory: 16 GB 2 x 8GB 1600 MHz Corsair Vengeance RAM
Optical drive: 16x Blu Ray LG Drive
WiFi: TP Link 802.11n 2.4GHz WiFi
Bluetooth: 4.0 USB Adaptor

I was thinking the issues might be RAM, but there's no evidence to support that from the stress testing that's been done on this. While I'm not ruling out RAM, I don't want to buy a new kit and find the same problems exist because I'll have wasted £100. It's been through a few configurations to get to there, all had issues. It was stable for a while last year, but I had to reinstall to change the User file name. Set it up with the same settings everytime since and I don't think I've had it as stable ever since.
 
Upvote 0 Downvote
A

Alec Mowat

Honorable
Jan 8, 2014
3,244
0
13,460
Why are you using DISM? Did you install from an image or a CD?
If you imaged your copy of Windows from different hardware, you are probably getting bluescreens for that reason.

None of these are Windows issues. If you installed via DISM, your image may be corrupt or the drivers are wrong.

You can't really compare Apple and Sony to Microsoft.
Apple makes hardware and builds the OS to suit it, they also charge a lot more.
Sony doesn't build an OS.
Microsoft makes an OS, but it's up to the hardware manufactures to build compatible hardware and the proper drivers.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
if you are getting a bugcheck, it is best to put your memory .dmp file on a cloud server so it can be looked at in a windows debugger.
generally bugchecks during low power states are caused by:
BIOS bugs, and 3rd party hardware device drivers and actual bugs in the electronics of some hardware.
Generally, windows 7 has the low power states turned off by default, windows 8.x turn them on and many hardware devices actually fail due to bogus electronic circuits in the device. Many OEMs have put out new drivers to "fix" the problem by disabling the features.

Also, the default TP link driver that was provided to microsoft corrupts memory and will cause a whole range of bugchecks for you. if you use that driver you must: updtate the BIOS, update the CPU chipset driver, update any custom USB 3.0 driver, then find a update TP link driver and remove the old driver that windows has and reboot. if you fail to do this, each time you boot you will get a different memory corruption in a different driver. This is because windows will load drivers in different orders on each boot. A bad driver tends to corrupt the driver next to it in memory. (drivers data corrupted)

- very common for 3rd party bluetooth drivers not to work well for low power links (sleep)
try to update the driver or use control panel to disable the sleep function for the device.

you should not need the dism.exe command is used to repair files that become corrupt due to malware and hacking software. if you are getting corrupt files on a regular basis that is not caused by malware i would make sure I am not running a custom storage driver or make sure it is up to date.

sound problems with the motherboard sound are often effected by the GPU high def audio support for the video cable. (you can disable it in windows control panel if you don't have speakers in your monitor feed by the video cable)


 
Upvote 0 Downvote
Solution
U

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815


I used the official Windows 8 install CD. I used DISM when the store wasn't working and none of my apps opened. It found component store corruption which has been fixed. It's not an image. Everything in this computer is new, including the OS which had never been installed anywhere else, until it got to this computer.

I was comparing Apple to MS because MS makes an OS, Apple makes an OS (they also make hardware) and in my experience Apple's solution has

I used Sony to compare the 360 to the PlayStation.

Sorry about the rage earlier though, it's just years of using MS products that never quite work right (doesn't matter if it's their console or their desktop OS, I've had problems with both) has left me sort of anti-Microsoft especially when I've found more often than not the alternatives look and work a lot better.

To be fair though, reliability on my PC has really improved from where it was one year ago, I don't know why though, seeing as I did the install process the same every time (it's been a while, but if I remember right, I'd nuke the OS drive and reinstall from disc) and for the most part it does work. It's just I've had a lot of random and different issues each time my computer decides to brain fart and since the hardware in here has passed stress tests multiple times and what messes up most is software made by MS (had problems with Office, Explorer, Windows 8.1 failing to wake from sleep etc) that doesn't help my opinion of them. I did overheat the CPU once though when I first put it together on day one, because I didn't realise the CPU cooler wasn't spinning because it wasn't in all the way. I'd never have known that the temps were getting so high had I not been in the BIOS at the time and had it not emergency shut down to save itself. I put my hands up to that one, the cooler looked and felt like it was in all the way, but evidently it wasn't. Could that be the cause???
 
Upvote 0 Downvote
A

Alec Mowat

Honorable
Jan 8, 2014
3,244
0
13,460
Apple doesn't technically make Apple OS, it's just a repackaged flavour of Unix/Linux. Most of it is actually open source or closed source packages from other companies in a Unix shell.

PS4 also runs FreeBSD, a Linux flavour.
http://en.wikipedia.org/wiki/PlayStation_4_system_software


Don't use DISM. Use SFC /scannow. http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm

Upload the dump files, or if you are feeling up to it, use WinDBG and check which files are breaking. If you have any type of Antivirus running and didn't disable Windows Defender, these types of conflicts can cause crashing.

https://msdn.microsoft.com/en-us/windows/hardware/hh852365.aspx

http://www.techrepublic.com/blog/windows-and-office/how-do-i-use-windbg-debugger-to-troubleshoot-a-blue-screen-of-death/

The only real MS products I've had problems with are the early versions of XP and Vista. Most of these issues with related to incompatibility with previous software and drivers though, not really technical problems. I never tried ME until recently, fortunately.

Apple and Sony might seem better on the front, but when you lose all of your ability to make any real changes to the OS. They've locked it down, locked the drivers down and locked the software down. It's the sacrifice we make as PC users to have customized software and hardware. They tried to lock down Windows (See Windows Apps, that part of Windows 8 no one uses) and everyone complained.
 
Upvote 0 Downvote
U

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815


I was thinking that it could be a driver. There was a time I like 8.1, it's just, the issues wear you down you know. If I could find the root cause and fix it, I'd more readily use Windows, because it's not that bad once the reliability issues (I've experienced, not saying 8.1 is inherently broken) are fixed as I found out last year as I found out in that near perfect few months of reliability, was awesome, I said to my computer do this and it did it without complaint :D
- My BIOS has recently been updated by the board manufacturer
- DISM was used because, according to the internet, that was the best way to solve the issue. Issue hasn't reoccured though so that's good
- Actually, now you mention drivers my TP Link driver is out of date. Would never have thought that that could be behind the issues. I'm using the TP Link driver that came on the disc with my adaptor. Searching MEMORY_MANAGEMENT error on the internet told me drivers could be a cause.
- My board keeps everything plugged into the USB ports powered on in sleep and in shut down state, so I don't think they actually sleep, but there was a time where Windows would shutdown my bluetooth adaptor at shutdown rather leave it running like it normally would.

So, this could be a driver issue? Could a bad driver also cause a hard freeze? :/
Where do I find all the drivers that are currently installed?
There might dump file somewhere on the hard drive, I haven't looked for them in a while

Just trying to find the root cause so I can once again boast rock solid reliability
 
Upvote 0 Downvote
U

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815


True, OSX is linux, but I had no idea the PS4 ran on Linux too. That thing is everywhere.

What I did was sfc/scannow which found component store corruption and then after looking online, the best way I found to fix that was DISM. What should I have done instead?
 
Upvote 0 Downvote
A

Alec Mowat

Honorable
Jan 8, 2014
3,244
0
13,460


Better question is, what did you change/modified before your entire store was corrupted? If you try to restore system files from your CD or an old image, you are replacing the patched files with old files and creating new issues.
 
Upvote 0 Downvote
A

Alec Mowat

Honorable
Jan 8, 2014
3,244
0
13,460


The dump files are in C:\Windows\minidump
 
Upvote 0 Downvote
U

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815


Nothing. Got all my programs loaded, it was running and then I think it was the apps ceasing to function that lead me down the sfc/scannow route which I then fixed with DISM so I went on my way again. Again, I didn't change any settings, same set of programs and came back not too long later and did sfc/scannow just to check, it reported corruption, so again I fixed. Finally it stopped reporting corruption and to date I have not had to do this again. I guess that makes sense with the CD. I used the CD when safe mode wouldn't start. Was in a remote access session with MS, they rebooted to Safe Mode with Networking, it turned off, I got the BIOS splash screen as normal, got the Windows splash screen for a few seconds and it faded to black and died. Just sat there for ages until I eventually force killed it. After that it would not get passed the Windows splash screen and that's when I tried the disc as a last resort. Disc would not start. The disc would go in and the computer would just sit there after the BIOS had done its thing. Can't remember how I got it back running again. Disc doesn't matter though, about as useful as the plastic it's made out of, always says it can't do anything unless you want to nuke the whole thing and start over

I don't change much in Windows' settings, other than wallpaper, screensaver, when it should sleep (in this computer's case sleep is turned off, my SSD everything up itself in terms of that), and in the case of this computer, because it's my multi-hard drive set up, change the default storage locations for installs and documents. That's how it's been with every Windows computer I have used, I don't change very much in the settings, but there's a long list of things that went wrong with this one (including my C drive which I named Evo because it's an 840 Evo SSD renaming itself back to Local Disc C and Windows requesting I reactivate after I've run a CHK DSK which I had already done otherwise I wouldn't be using Windows would I? Also, for some reason when I create a new user account, the default wallpapers don't load, I get a black screen with a taskbar like it tried to load, but forgot what it was doing or gave up. I don't know if it still does it now though

So, I don't change much, just things like wallpapers, which programs need to run at start up (I only alter the ones I installed) like Steam and stopping the LG ODD firmware update running at boot because it never did anything and that's pretty much it. The other stuff is how it was when it installed

You know my ALT+Tab and my Print Screen broke once. ALT+Tab looked like it had come from Windows 98 and Print Screen wouldn't take a screenshot of the game that was on the screen at the time, but instead it would always grab the desktop. Yeah, I've had random issues like that. Persistent issues are why I ended up getting a partial refund on this OS.

I was just thinking could it be down to something like the BIOS being set wrong? UEFI didn't work when I set it up it said something about a GPT partition table, so I set it to Legacy or some sort of hybrid mode (I can't remember, it's been ages since I've been in the BIOS) and it worked. This reminded me of when 8.1 kept identifying my tertiary drive as an IDE drive when it was connected by SATA cable and the BIOS even said it was SATA but Windows had other ideas
 
Upvote 0 Downvote
U

unplanned bacon

Distinguished
Jan 11, 2014
1,649
1
19,815


I can't, it gives this error:


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


Loading Dump File [C:\Windows\Minidump\020115-6203-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 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17415.amd64fre.winblue_r4.141028-1500
Machine Name:
Kernel base = 0xfffff802`6bc84000 PsLoadedModuleList = 0xfffff802`6bf5d250
Debug session time: Sun Feb 1 14:02:44.119 2015 (UTC + 0:00)
System Uptime: 0 days 23:47:56.078
*********************************************************************
* 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
..................................................

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff68000037180, efe0000131903886, fffff680000b7181}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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+1509a0 )

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

This is what I spent too much time doing the last 12 months, trying to fix problems :/
And currently it's crashed
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom