Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Resolved Question

win7 home premium bugheck

Sep 11, 2014 12:34PM PDT

system.. toshiba portege r835, win7 home premium, updated 3 days back (no problems with update)

have had this laptop for 3 years , never had BSOD or lockup until today....got a BSOD, while i was surfing.........system shut down.

powered up ok, no problems, ran full virus scan- no issues.

tracked the event- says bugcheck code 126.

EventData


BugcheckCode
126
BugcheckParameter1
0xffffffffc0000005


BugcheckParameter2
0xfffffa800a49ffcb


BugcheckParameter3
0xfffff880009e88a8


BugcheckParameter4
0xfffff880009e8100


SleepInProgress
false


PowerButtonTimestamp
0

have not been able to find the cause or solution by searching for bugcheck code 126.

any suggestions?

thanks

Discussion is locked

dr.gj has chosen the best answer to their question. View answer

Best Answer

- Collapse -
The thing you learn is
Sep 12, 2014 12:34AM PDT

That a bugcheck is not all that useful on its own. When I see a BSOD I collect the make/model of the machine along with what the PC was doing at the time and then use prior experience and google to guide what to do next.
Bob

- Collapse -
no resolution
Sep 12, 2014 6:29AM PDT

r. proffitt....all the info you mentioned is my post...

web search- did not find any answer, that is why i posted

- Collapse -
Not entirely.
Sep 12, 2014 6:53AM PDT

I don't see any note about you keeping up on maintenance, scanning for malware, battery age, and so on.

It could be hardware or software so let's take your word you can't decipher the prior replies.

1. Software.
If it's software, restoring the PC to it's factory load will correct it.

2. Hardware.
If it's hardware the most common is lack of maintenance as well as dried up, crack heat sink compound. It's well discussed on the web how to use canned air and replace compound so I'll pause here.

3. It happened ONE or TWO TIMES.
There are some newer PC owners that freak when it happens. They want to track down why. The issue here is it could be an SEU (see google) and there are too many random reasons why we can have a SEU.
Bob

- Collapse -
Re: SEU
Sep 12, 2014 7:14AM PDT

Hi Bob, I followed your advice and googled SEU ACRONYM. That brought me to http://www.acronymfinder.com/SEU.html that gave 27 possible definitions.

You don't mean Stupid End User, do you? My guess is Single Event Upset (probably not caused in this case by Slighty Enriched Uranium, although that would be a very good source for that particles).

Kees

- Collapse -
Single event upset I think.
Sep 12, 2014 8:45AM PDT

Dafydd.

- Collapse -
Single Event Upset.
Sep 12, 2014 9:25AM PDT

I've never heard of that first definition but the circles I run in are all software authors and hardware designers. Thanks for that one, we'll love it.
Bob

- Collapse -
sepcific answers
Sep 12, 2014 8:39AM PDT

bob...thanks for taking the time to answer...let us see if with this you can point to some specific approach to narrowdown between hw & sw..... reloading the OS (restoring to factory) is not a useful answer, unless we can at least narrowdown if it is is a SW problem. i do have the recovery disk (and a spare hard drive) if it comes to that

scanning- i use windows essentials- as stated, update 3 days ago both windows-updates and virus, no malware found.

ran a scan after the event- no issues found

the pc has running fine since the event (granted it is less than 24 hrs but i have used it a lot)

hardware- yes anything can be bad- i have replaced heatsinks & fan assemblies (on other machines) - if it comes to that

recurrence- as above, has happened only once since i bought it 3 yrs back

apparently, according to some experts (if one know how decipher it) the code and the 4 parameters posted should point to an area of the problem...

- Collapse -
Scanning with a single tool no longer cuts it.
Sep 12, 2014 9:28AM PDT
- Collapse -
other scan, SEU, recurrance
Sep 12, 2014 1:19PM PDT

other scan- yes, will be scanning over the weekend

SEU - not sure which definition you were eluding to.....i am assuming it is not the stupid...... not to say that at times i have not felt that i wan not doing the smart thing. but if you were,in this case, that will be an easy to ward off the question.

recurrence- the whole purpose of this effort is to be ready if it happens again...but it happens once every 3 yrs.....

- Collapse -
I'm ready.
Sep 12, 2014 10:40PM PDT

I reboot and carry on. Happens more often at our office because we are writing apps. Figure once a month. It happens.
Bob

- Collapse -
spicific answers
Sep 12, 2014 8:44AM PDT

thanks providing more detail shrtly.

- Collapse -
Answer
Re: bugcheck 126
Sep 12, 2014 6:45AM PDT
http://www.faultwire.com/solutions-fatal_error/An-invalid-pool-request-has-been-made-to-netio-managed-0x00000126-*1291.html seems a reliable source (DON'T believe the sites that say that a registry cleaner like regcure will fix it in a few clicks: it won't).

So it can be anything, software or hardware. For the moment, it seems that "restart the computer" was the solution. If it occurs repeatedly, follow the suggestions made in that link. If you believe it's software, you can start with system restore, then go back to factory conditions. If you believe it's hardware, you can start with checking the RAM (memtest86 is free and recommended).
If it still occcurs after going back to factory conditions, it's certainly hardware. Then find the broken component and replace it.

It's quite unlikely it's a vrius.

Kees
- Collapse -
looks like i have to wait till
Sep 12, 2014 8:54AM PDT

it happens (it it happens).

i posted the details based on what i read in this forum....

apparently- both you and bob seem to think otherwise....so i have to wait and see what happens next.

thanks for the response

- Collapse -
Answer
not resolved & not the best answer
Nov 26, 2014 5:21AM PST

i understand this is a free forum and help provided is by volunteers-- i do appreciate it.

however, not sure how & who decides when the question is declared "RESOLVED" ...my question is NOT resolved and i did not pick the best answer either (as stated on one of the answers- possibly i was ). unless, as some vendors do, the trouble-ticket is declared "RESOLVED" if no one knows the answer.

i am still looking for the basic cause of the problem posted...

- Collapse -
Simplest answer?
Nov 26, 2014 5:28AM PST

Our PCs are not free from bugs or flaws.

- Collapse -
bugs are a way of life
Nov 26, 2014 10:18AM PST

indeed. and neither are the operators.

no comment on operator bugs, but the curious in wants to find the cause of 126

- Collapse -
Re: resolved
Nov 26, 2014 5:32AM PST

As far as I know, only you yourself can say it's resolved; nobody else can and it doesn't happen automatically. Also, I don't think it can be undone.

But now we are 2.5 month further, can you tell how often it happened in that 2.5 month? If not at all, forget abut finding the cause. It just happened.

Kees

- Collapse -
windows - reloaded
Nov 26, 2014 10:16AM PST

the original problem problem has not re-occurred. however i did have another issue: the windows explorer became unresponsive...so re-loaded the system image to a version about a month ago.

i had actually stopped thinking about the bugcheck 126...only because of the recent issue i started taking another look