Complex misbehaving

gyurika

Active member
Joined
Aug 7, 2015
Posts
36
Location
New York
Hi, I apologize, let me go backwards here, and anybody can make sense out of it is Great...
1./My original program I wanted to fix was, that automatic hibernation does not work, because something is preventing the system from completely shutting down. The interesting part is that if I "click" manually on hibernation it has no problem. A BSOD request of mine is pending for answer from Webroot, however I tried to leave it running with Webroot disabled and it still could not shut down so that may not be the original cause.
Now once I click the power button in the morning (the power light stays on and all USB because my keyboard and mouse are lit up all night, sometimes HDD running. Sometimes it shuts down that is a definite blue screen then.) - it then shuts down, and when I start it it either comes back with a blue screen or just a lilac strip to send error report to Microsoft.
2./ So therefore I started looking to solve "little" problems. Like Windows Color System will not start. I get a bogus message about timing but it cannot be started manually either. The dependencies are running, but when I checked the svchost.exe details in Svchost Process Analyzer, then WCS is listed under a Svchost that is <not active>. Now obviously that is why it will not start because the Path to executable in the WCS properties is C:\Windows\system32\svchost.exe -k wcssvc, and that is not running. so my conclusion at this point is ????????????? -- that is why would its svchost not be active? - or how could it be sent to an other one that is active, or whatever the fix is with these things. I am clueless in this area.
Have been trying to resolve this shutdown now for about 4-5 month diligently... appreciate all help thx.
 
I'm having a somewhat difficult time following exactly what the problem is here.

For example, what does this mean?
A BSOD request of mine is pending for answer from Webroot,

I honestly don't know what you mean by a "BSOD request" and why/how it is your request; why/what Webroot needs an answer/has anything to do with it (BSOD).

Regards. . .

jcgriff2
 
I'm having a somewhat difficult time following exactly what the problem is here.

For example, what does this mean?
A BSOD request of mine is pending for answer from Webroot,

I honestly don't know what you mean by a "BSOD request" and why/how it is your request; why/what Webroot needs an answer/has anything to do with it (BSOD).

Regards. . .

jcgriff2
 
Sorry that I am using a quality time to trying to figure my post. In one of my posts I sent two attachments. And I cannot see it from my end, maybe I am not using the site properly. The answer to too of those attachments suspected Webroot, notwithstanding that it may be already a consequence. (I do se a no answer from somewhere... that may have affected webroot). Anyway today I got an answer, and what Webroot has figured that memory is the culprit:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe001fadad880, The thread currently holding on to the Pnp lock.
Arg4: fffff802ba765980, nt!TRIAGE_9F_PNP on Win7

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE

I will be changing the memory. G-Skill will exchange it... I hope that explained what I meant by waiting for Webroot's analysis.
Any chance the Windows Color System may tickle you fancy? I have spent so much time, it has become an intellectual pest bugging me more than the computer...
Appreciate your kind concern so far and possibly beyond... +g
PS: My OS is 8.1 straight what is W7 in the log doing?
 
... Anyway today I got an answer, and what Webroot has figured that memory is the culprit:
Isn't Webroot security related software? --> Next-Generation Endpoint Protection & Threat Intelligence | Webroot

I don't understand how webroot is involved here & that it figured out that memory is the culprit.

... PS: My OS is 8.1 straight what is W7 in the log doing?
If that info came from Windbg, it is completely normal to see references to Windows 8.1, 8, 7 and Vista in the output, regardless of which Windows OS you have.

If you are seeking help for BSODs, I need you to run this - https://www.sysnative.com/forums/bs...ng-instructions-windows-10-8-1-8-7-vista.html

Regards. . .

jcgriff2
 
... Anyway today I got an answer, and what Webroot has figured that memory is the culprit:
Isn't Webroot security related software? --> Next-Generation Endpoint Protection & Threat Intelligence | Webroot

I don't understand how webroot is involved here & that it figured out that memory is the culprit.

jcgriff2

Hi jcgriff2

I admire and appreciate you tenaciousness.
As I told you I have a post in the BSOD section and I uploaded 3 attachments. I believe from the mini-dump a kind soul analyzed, that Webroot processes were named in two separate instances. (Although he mentioned Webroot may not be the actual offender.) So I contacted Webroot, and they had me upload the Webroot log. That in turn has shown no Webroot screwup, but a few lines containing the phraze "memory corruption". (or failure?)
That is both a surprise and a no-surprise. I have run memtests ad nauseum. Nothing. Stripped it to one stick, still had a blue screen... On the other hand every type of blue screen with either iastoreB and ntoskrnl involvement - among the possible causes memory has been routinely mentioned. (among a bunch of other possible causes.)
So this is how I got to the memory via Webroot.
I am wondering if those files were not helpful, that Microsoft is sending to himself, every time I wake from auto-hybernation??? (+ files)
Thanks
gyurika
 
Hi. . .

I need the kernel memory mini dumps + the system files.

I don't see any files attached anywhere in this thread, but did find a 2+ week old BSOD thread - https://www.sysnative.com/forums/bs...tdown-banana-problems-i-am-going-bananas.html

"Cluberti" posted last and cited over-clocking as a possible cause. If you're still over-clocked, please reset to factory default settings.

In the meantime, please run our BSOD Posting Instructions and attach the resulting zip file(s) to your next post -

https://www.sysnative.com/forums/bs...ng-instructions-windows-10-8-1-8-7-vista.html

Regards. . .

jcgriff2
 
Hi. . .

I need the kernel memory mini dumps + the system files.

I don't see any files attached anywhere in this thread, but did find a 2+ week old BSOD thread - https://www.sysnative.com/forums/bs...tdown-banana-problems-i-am-going-bananas.html

"Cluberti" posted last and cited over-clocking as a possible cause. If you're still over-clocked, please reset to factory default settings.

In the meantime, please run our BSOD Posting Instructions and attach the resulting zip file(s) to your next post -

https://www.sysnative.com/forums/bs...ng-instructions-windows-10-8-1-8-7-vista.html

Regards. . .

jcgriff2
 
Hi jcgriff2
Same thanks as before... You did find the right post I think and it has the attachments similarly under my name.
Not sure how the automatic minidump uploads work, - do they only collect the last dump? Assuming it is so, maybe I should wait for a brand new Blue screen. Or maybe I could collect one for the IastoreB.sys version and one for the ntoskrnl.exe... ??
Cluberti's over-clocking assumption may or may not have been well founded from two aspects no less. My memory is a 32 GB DDR4 2666 G-skill Ripjaws set. The ASUS X99 registers it (in error) under STATUS as 2133 or something. So all I did (lots of tinkering including G-Skill techs setting it to their specs) was, to set it to its nominal baseline value 2666 - and the computer lives through that as an overclocking experience which it is not - strictly speaking. After a time the computer looses that setting, and reverts back to 2133. So depending when the mini-dump was taken it may have been running 2133 or 2666, but in my mind one is normal and the other one is underclocked. BUT: this is certainly another memory anomaly, and it will be interesting to see if an exchange set behaves differently or not... (I need to get some money to have that experience, my employer has not been paying me for the last 7-8 month and I am trying to bring the Labor Dept into the mess and in the mean time suing him 150 for each day I am not working but I am pretty bottomed out as you may figure. So I have LOTSA TIME to do free tinkering, but the mem swap is temporarily on hold. So, in the mean time I am very appreciative for help like you are providing, because this is a borderline area of my knowledge a "no go on my own..." Thx a lot.
 
Last edited:

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

Back
Top