(KB3197954) installs but upon restart BSOD storport.sys and reverts to not installed

J

jzchen

Contributor
Joined
Nov 3, 2016
Posts
14
Location
Arcadia, CA
I'm sorry I did not really know which place to put this thread, but since I made some progress in Windows Update, it no longer fails with 0x800703f1, I started trying the instructions on the BSOD side because that doesn't seem to resolve. BSOD notes storport.sys and I have tried to figure out which driver, if any, may be the cause. I have purchased a SSD because I thought my HDD was failing and the computer does seem to perform better.

Perfmon /report seems to crash. I get a cmd prompt, but the window that opens stays at "Report Status" "Collecting data for 60 seconds..." It is still running after over 30 mins.

Please advise, and thank you so much for providing this service!!!

OS- Windows 10 Home KB3194798 (Barely got that installed after the SSD upgrade somehow!) (Version 1607 Build 14393.187 from "About")
x64
Original OS- Windows Vista
Upgraded from Vista to 7 (purchased a 3 pack license), and then took advantage of the free Windows 10 Upgrade.
I believe I bought the laptop back in 2008, so around 8 years old.
I upgraded to 7 and then Windows 10 around mid March

AMD Turion X2 Ultra Dual-Core Mobile ZM-84 2.30 GHz
ATI Mobility Radeon HD 3400 Series (0x95C4) from "Display adapter properties"
motherboard- it is a laptop (skip)
power supply- laptop (skip)

HP
dv5z-1000
Laptop computer
 
Last edited:
Perfmon has been running for about 1 hour 40 minutes now... I guess I could leave it for 24 hours and then start the driver tests then RAM tests. (I'm assuming I can skip the HDD test as the SSD is brand new...)
 
Hi,

it is the Chipset which is to old, see
Code: 
start             end                 module name
fffff809`fcee0000 fffff809`fcf2b000   [COLOR=#ff0000]ahcix64s[/COLOR] T (no symbols)           
    Loaded symbol image file: ahcix64s.sys
    Image path: ahcix64s.sys
    Image name: ahcix64s.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Apr 11 08:40:05 [COLOR=#ff0000]2008[/COLOR] (47FF07C5)
    CheckSum:         00033B21
    ImageSize:        0004B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
your notebook:
HP Pavilion dv5z-1000 CTO Entertainment Notebook PC Treiber und Downloads | HP(R) Kundensupport

bios is current / latest.

a slightly newer one is available at AMD but discontinued at win8 / (8.1) and should work better, else your laptop reached the end of its capabilities.

Chipset
 
Dear Michael,

Thank you so much for the fast response!!!!

I installed the chipset drivers and it requested I reboot, and the reboot went fine.

I then installed the Raid driver. I restarted and got the exact same BSOD. It then went on to attempt reboot and another BSOD:

SYSTEM THREAD EXCEPTION NOT HANDLED
TDI.SYS

It was really quick so I am not sure I copied it down correctly, but it looks like one I saw when installing KB3197954, although this one doesn't always show up.

I am going to try to install the Cumulative Update now and see....
 
Well, seems like it's definitely the raid driver portion causing an issue. (I am always worried I may have a Rootkit as one computer I tried to repair had one.) I am happy that it is installing, but it gets deleted when restarting. Before it would not even complete with error 0x800703f1!

I didn't know the old hard drive is only 2 years old. It still has warranty I think, but it was acting like it was failing. Now with the SSD it is running a lot smoother.

I know you advise it is a very old computer. I am just trying to save some money at this time....

Thank you again! I have sent a little something for my gratitude. :dance:
 
Dumpfile 110116-34937-01.dmp

found the following which isn't good, wondering it did not crash earlier.



Sunbelt Counterspy??
fffff80f`758b0000 fffff80f`758ce000 sbapifs sbapifs.sys Wed Jul 25 19:59:15 2012 (501033F3)

Avanquest File Restore
fffff80f`759f0000 fffff80f`759f8000 AQFileRestore AQFileRestore.sys Fri Nov 23 07:18:53 2012 (50AF154D)

Gear ASPI- not needed
fffff80f`768b0000 fffff80f`768b6c00 GEARAspiWDM GEARAspiWDM.sys Thu May 3 21:56:17 2012 (4FA2E2E1)

pretty old Bitdefender?
fffff80f`73b00000 fffff80f`73b2d000 bdftdif bdftdif.sys Mon Nov 14 18:15:59 2011 (4EC14CCF)

Filefilter from XIMETA
fffff80f`73930000 fffff80f`739eb000 ndasfs ndasfs.sys Mon Dec 28 23:39:04 2009 (4B393388)
Filefilter from XIMETA
fffff80f`739f0000 fffff80f`73aa9000 lfsfilt lfsfilt.sys Mon Dec 28 23:39:04 2009 (4B393388)

remove / uninstall.
 
Dear Michael,

Thank you again for looking into this issue!

The link you gave had two separate downloads, one specific for the Raid. It failed when I tried to update the raid part only. The first driver installed fine.

The one I found is newer and lists Windows 10, but unfortunately it is a complete single download package, including the Raid driver. I am assuming it is the raid driver that has a problem, but when I check device manager it is there.

Sunbelt- I don't recognize that
Avanquest- A recent install as I have been happy with their Fix-It product. Used it to check for HDD issues and fix registry issues.
Gear ASPI- Don't recognize
Bitdefender- Antivirus I bought after the rootkit found in another computer. It makes the computer slow, particularly when it automatically downloads updates, which are large as well! And whenever I start the computer the firewall starts and knocks out any sort of internet access, after Windows 10 upgrade, so I have to disable the firewall every start!
Ximeta- NDAS storage device, but honestly I haven't used it for at least a year, if not two.

For some reason I get the feeling the KB3197954 includes the raid driver and that is why it fails.

Did you mean I should try to uninstall these items?
 
Hi,

I'm afraid in my last post I did not respond to one item. (If you look carefully at my posts I am up at odd hours of the day here and I guess I am not sleeping well.) I did try to download the KB from the Microsoft Catalog. It now installs fine, either the Catalog download or through Windows Update, but upon restart I get a BSOD, then revert to not installed. I followed the instructions on the Windows Update side of sysnative.com, downloaded the software package that was created by someone on sysnative, and it downloaded one item to repair, then said it completed without any remaining issues. Since that one download seemed key to the consistency of install success now, (prior to restarting that is,) I was more than happy to send a little donation.

Here on the BSOD side of sysnative, I just recently tried the driver verifier, but it crashed Windows. Luckily it first has you create a system restore point. I restored and it now boots, but just this boot there was a blue screen saying some device is missing, (a new BSOD I am not familiar with seeing before), but started up afterwards. I sent a PM to the thread creator because that thread is closed, asking if verifier is now turned off/if I need to do anything more to turn the verifier off, so far no response.
 
Actually, I need to make a correction. I used Avanquest Fix-It for many years. (I am much happier with it than I had been with Symantec or McAfee). After the rootkit problem at work where an employee complained about Fix-It being "junk" because it let the rootkit infect a computer, I purchased 3 years of Bitdefender Small Business Edition. It is set to expire in 97 days, (it notes the days on the bottom when I open it to disable the firewall).
 
So I did a little more research on your items in question.

Sunbelt is probably from the VIPRE antivirus software. I may have used it to check if this computer was infected as I used this computer to download stuff for the rootkit infected computer, (the rootkit caused no internet access).
Avanquest must have been some sort of system restore. (It has it's own.)
Gear is some sort of recording/duplicating software. I'm throwing a guess at ImgBurn because I'm really not sure.
Bitdefender is my current antivirus. When I installed Fix-It it recognizes the Bitdefender and does not install it's own antivirus. Kind of nice feature of Fix-It.
Ximeta I can just remove. (I'll just verify I still have the installer package because it seems the company went out of business.)
 
i know pretty well what I've marked as to be removed.

either its the functional package or only a rest of it, get rid of otherwise i can't help more on this particular issue.
 
Thank you!

I was typing my last responses in the middle of the night, and was definitely confused. VIPRE was uninstalled a long time ago. I am not sure how to remove the item, but I will search and try. I will uninstall Bitdefender and Avanquest because they are still installed. The Gear item I am not sure what to remove. It is some generic thing, but I will try. I already uninstalled the Ximeta.

I will try to run the software I downloaded here again once again after to verify I am successful. Is it easy to find the part you posted to see that they are gone?

I am not sure what you meant. Did you try to remove them for me?
 
So far:

I Uninstalled Bitdefender.

I uninstalled Avanquest Fix-It but I did keep logfiles and restore information just in case if that is okay?

Ximeta uninstalled as I noted before.

I ran the command SC Delete SBAPIFS in an Administrator command prompt and it said it was successful.

Followed this to remove GEARAspiwdm.sys manually:

http://www.gearsoftware.com/wiki/index.php/DRIVERS:_Windows_-_Updating,_removing,_64_bit_versions,_etc#Manual_Removal_.E2.80.93_64-bit

I still get the same BSOD storport. Can I verify somehow I uninstalled the items completely, and how?

Thank you again for your time and patience.
 
I found the .dmp file but when I open it is unreadable... (Sigh.) Tried to download the Windows Debugger Toolkit and open with WinDbg with no luck.... :huh:

Attaching the new/updated .zip.

Can't tell if I removed the items you wanted me to remove successfully or not.
 
I am currently trying the instructions for VIPRE removal here:

How to manually remove a VIPRE Business Agent : Support

Since it was a really long time ago and only remnants seem left, I am down at "Manual Agent removal..."

Apparently there are a few items left as SC Delete xxx says success on a few items, including the SBAPIFS, which I had done earlier. I am going to attempt to delete the registry keys a little later but I did not want anyone to spend time with the .zip before I finish. (I will continue later.)

Items still in the system seem to be:

SBAMSvc
SBAPIFS
SBRE

(Add VIPRE to the list of programs I do not like. I only used it because it recognized the rootkit infection. Only Malwarebytes was able to remove the rootkit...)
 
jzchen said:
I found the .dmp file but when I open it is unreadable... (Sigh.) Tried to download the Windows Debugger Toolkit and open with WinDbg with no luck.... :huh:

Attaching the new/updated .zip.

Can't tell if I removed the items you wanted me to remove successfully or not.
Click to expand...


Nothing more to fix from my point of view, even Debugger strikes


Code: 
===============================================================================
Common Platform Error Record @ ffff848a7b9c9038
-------------------------------------------------------------------------------
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Signature     : *** INVALID ***
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Revision      : 0.0
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Record Id     : 0000000000000000
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Severity      : Recoverable (0)
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Length        : 0
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Creator       : {00003839-003e-0000-0000-00000f000000}
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Notify Type   : {00003839-003e-0000-0000-00000f000000}
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Flags         : 0x00000000

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************

and yes, still portions already mentioned are in the system.

last hint: clean install unless another member wants to jump into^^
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top