New
#111
Keep driver verifier running.
When you upgraded windows, did you check HP for driver updates?
Keep driver verifier running.
When you upgraded windows, did you check HP for driver updates?
Sometime later HP gave me some driver update suggestions, but at the time only installed the few I thought I needed, and NOT Bluetooth, etc. Since the past weeks have updated ALL drivers and BIOS except Mobile Partner (no update available)
BIG question: before I dare run the stress-test again, I need to know how long it should stay at 100% with NO change! When it ran before it went to Blue Screen almost immediately, stayed at 100% for ca. 10 min, the machine got HOT and I need to know if the test is still really functioning or stalled! You wrote to quit at the Blue Screen, which happened right away! (but I let it run -- or stall -- for ca. 10 min, not knowing if that was normal!).
How long should I allow it to get hotter and HOTTER at 100% while it is supposedly "collecting some data info"?! Should I unplug and turn OFF Mobile Partner dongle first? > that was "what failed" ... and NO indication of ANY other failures!
B.t.w., I have no income (from any source) at the moment and cannot afford another machine or even repairing this one (everything costs up to 3x what it would in USA, incl. repairs), or getting another WinX, etc.
Normally driver verifier should be run for 48h at once, I expect there are a few drivers behaving poorly. To catch every bad driver, re-enable driver verifier after addressing the caught driver.
It is very normal for your system to behave like that, most of the times a system will act very slow.
Driver verifier is NOT a tool that collects data, all it does is monitor the actions of the specified drivers for any illegal activity. If it catches a driver misbehaving, it will crash the system. The crash collects the information in the RAM and stores it as a dump file on your disk.
Well that was an adventure I do not wish to repeat! I tried Verifier again, this time with Mobile Partner turned off and the dongle unplugged from the USB port. So NO Internet. System worked, albeit slowly, and to exercise drivers I normally use I tried some stored recordings and music videos, Audacity (complex recording/mixing system intense use home studio), then (not to completion, just to stress system) a Defender Quick Scan, and similarly a Kaspersky Quick Scan. All OK.
Then I plugged in Mobile Partner. Zippo ... Big Blue Screen, same failure cause indicated on screen (Mobile Partner USB). Then quickly "collecting error data" to 100%, then backlit black (grey), auto re-start, then same Blue Screen. Finally unplugged Mobile Partner , went to "normal" but slow start, clicked on Start to try to re-set Verifier, no luck. "Please wait for start menu to complete initial collection of information". After many minutes of no change, used manual power off. Started again and managed to start pre-set System Restore but Verifier still slowing everything, and Restore getting nowhere after several long minutes (I have used System Restore enough to know how long it should take to get going into initialization, etc.).
Purposely put Mobile Partner into USB to cause crash and after TWO same Blue Screens as above finally (in German) given options and was able to use (in German) the pre-set System Restore which worked successfully at normal speed and manner.
While there may be other not-great drivers, even under Verifier stress they caused NO problems. Obviously -- written there as the crash failure cause -- the Mobile Partner caused all the above Blue Screen crashes. Since I have no other viable Internet-connection options, and since my 98% use of this device requires the Internet, I must use Mobile Partner as the only option available to me.
I vote against doing another driver stress-test, especially since while it is on without Mobile Partner I cannot use the computer for the only real need I have for it .... and my use of the Internet for most of the day is essential for me at this time.
However the dump files might give you (or someone) valuable information. How can I find and post them, or should I even do so?
.... and what about failing InstallAgentUserBroker which is now up to 326 recent failures?
can someone think of or find a workaround?
Attachment 161239
Don't want to interrupt BSOD analysis in any way... just to ask, Airider, which version of USB modem drivers are you using?
After you finish analysis, check out these, if they are newer...
Station-drivers
from description:
Description:
Resolve a blue screen issue after the PC resumes from S3/S4 sometimes.
Send the notification when PC goes into S3/S4 or resume from S3/S4 in default.
Resolve a issue that if there is an indication with the AT result, it can not parse the content.
Add a notification for system time when open the GPS port.
Add some permission for some registry
File Size:
26.9Mo
Downloads:
211
File Version:
Version 4.25.17.04
The only USB device I use is Huawei Mobile Partner (dongle). It has firmware from FIVE years ago, and according to both the Hauwei site and Windows (update driver) that is the "latest" firmware
Attachment 161245
Attachment 161247
Attachment 161248
It seems that the drivers of the dongle are very old, too old to be guaranteed compatible with Windows 10.
Also, do you need 16GB of RAM? It seems you're using mixed memory which could contribute to the problem, if not the sole cause.
These have newer date, but you should check under details, if they are for the same hardware (PCI_ven)
Attachment 161256