A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

"Bugcheck Code 126"



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old November 28th 16, 03:16 AM posted to alt.comp.os.windows-10
The Real Bev[_2_]
external usenet poster
 
Posts: 140
Default "Bugcheck Code 126"

Friend's Win10 machine keeps crashing -- several times a day, while she
was working with it. Desktop computer, no heat problem. Bug check
0x7e. Googling has resulted in circular references,
incomprehensibility, and a couple of firefox/linux crashes at the
microsoft site, along with one possibility that the cause is a faulty
USB driver -- that just happened to be one guy's problem, but I saw
others for the 0x7e thing. The Event Viewer produced the following. Can
anybody translate this into actual information?

the Event Viewer lists 9 events from 10/8/2016 9:21:03pm thru 11/25/2016
7:29:37pm

Level: Critical
Source: Kernel-Power
EventID: 41
Task Category: (63)
---------
details:
Event 41, Kernel-Power
(Friendly View)
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 4
Level 1
Task 63
Opcode 0
Keywords 0x8000400000000002
- TimeCreated
[ SystemTime] 2016-11-28T00:11:23.707890000Z
EventRecordID 67204
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer name
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 126
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff80139e515b0
BugcheckParameter3 0xffffa3819bfee378
BugcheckParameter4 0xffffa3819bfedba0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 1
CsEntryScenarioInstanceId 0

it also has Details in XML View

- Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"
- System
Provider Name="Microsoft-Windows-Kernel-Power"
Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /
EventID41/EventID
Version4/Version
Level1/Level
Task63/Task
Opcode0/Opcode
Keywords0x8000400000000002/Keywords
TimeCreated SystemTime="2016-11-28T00:11:23.707890000Z" /
EventRecordID67204/EventRecordID
Correlation /
Execution ProcessID="4" ThreadID="8" /
ChannelSystem/Channel
ComputerBEWsDesktop64/Computer
Security UserID="S-1-5-18" /
/System
- EventData
Data Name="BugcheckCode"126/Data
Data Name="BugcheckParameter1"0xffffffffc0000005/Data
Data Name="BugcheckParameter2"0xfffff80139e515b0/Data
Data Name="BugcheckParameter3"0xffffa3819bfee378/Data
Data Name="BugcheckParameter4"0xffffa3819bfedba0/Data
Data Name="SleepInProgress"0/Data
Data Name="PowerButtonTimestamp"0/Data
Data Name="BootAppStatus"0/Data
Data Name="Checkpoint"0/Data
Data Name="ConnectedStandbyInProgress"false/Data
Data Name="SystemSleepTransitionsToOn"1/Data
Data Name="CsEntryScenarioInstanceId"0/Data
/EventData
/Event



--
Cheers, Bev
"To turn is to admit defeat." -- Hugh Grierson
Ads
  #2  
Old November 28th 16, 03:34 AM posted to alt.comp.os.windows-10
David LaRue[_2_]
external usenet poster
 
Posts: 8
Default "Bugcheck Code 126"

The Real Bev wrote in news1g3vm$pn2$1@dont-
email.me:

Friend's Win10 machine keeps crashing -- several times a day, while

she
was working with it. Desktop computer, no heat problem. Bug check
0x7e. Googling has resulted in circular references,
incomprehensibility, and a couple of firefox/linux crashes at the
microsoft site, along with one possibility that the cause is a faulty
USB driver -- that just happened to be one guy's problem, but I saw
others for the 0x7e thing. The Event Viewer produced the following.

Can
anybody translate this into actual information?

the Event Viewer lists 9 events from 10/8/2016 9:21:03pm thru

11/25/2016
7:29:37pm

Level: Critical
Source: Kernel-Power
EventID: 41
Task Category: (63)
---------
details:
Event 41, Kernel-Power
(Friendly View)
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 4
Level 1
Task 63
Opcode 0
Keywords 0x8000400000000002
- TimeCreated
[ SystemTime] 2016-11-28T00:11:23.707890000Z
EventRecordID 67204
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer name
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 126
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff80139e515b0
BugcheckParameter3 0xffffa3819bfee378
BugcheckParameter4 0xffffa3819bfedba0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 1
CsEntryScenarioInstanceId 0

it also has Details in XML View

- Event

xmlns="http://schemas.microsoft.com/win/2004/08/events/event"
- System
Provider Name="Microsoft-Windows-Kernel-Power"
Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /
EventID41/EventID
Version4/Version
Level1/Level
Task63/Task
Opcode0/Opcode
Keywords0x8000400000000002/Keywords
TimeCreated SystemTime="2016-11-28T00:11:23.707890000Z" /
EventRecordID67204/EventRecordID
Correlation /
Execution ProcessID="4" ThreadID="8" /
ChannelSystem/Channel
ComputerBEWsDesktop64/Computer
Security UserID="S-1-5-18" /
/System
- EventData
Data Name="BugcheckCode"126/Data
Data Name="BugcheckParameter1"0xffffffffc0000005/Data
Data Name="BugcheckParameter2"0xfffff80139e515b0/Data
Data Name="BugcheckParameter3"0xffffa3819bfee378/Data
Data Name="BugcheckParameter4"0xffffa3819bfedba0/Data
Data Name="SleepInProgress"0/Data
Data Name="PowerButtonTimestamp"0/Data
Data Name="BootAppStatus"0/Data
Data Name="Checkpoint"0/Data
Data Name="ConnectedStandbyInProgress"false/Data
Data Name="SystemSleepTransitionsToOn"1/Data
Data Name="CsEntryScenarioInstanceId"0/Data
/EventData
/Event


Hello Bev,

The BugcheckParameter1 looks like a null dereference occurred. The
SystemSleepTransitionsToOn is 1. Perhaps the system was about to go to
sleep and had some kind of issue.

If that is the case perhaps your friend can adjust their sleep settings
so it doesn't try to sleep. That might prevent the problem.

David
  #3  
Old November 28th 16, 07:11 AM posted to alt.comp.os.windows-10
The Real Bev[_2_]
external usenet poster
 
Posts: 140
Default "Bugcheck Code 126"

On 11/27/2016 06:34 PM, David LaRue wrote:
The Real Bev wrote in news1g3vm$pn2$1@dont-
email.me:

Friend's Win10 machine keeps crashing -- several times a day, while

she
was working with it. Desktop computer, no heat problem. Bug check
0x7e. Googling has resulted in circular references,
incomprehensibility, and a couple of firefox/linux crashes at the
microsoft site, along with one possibility that the cause is a faulty
USB driver -- that just happened to be one guy's problem, but I saw
others for the 0x7e thing. The Event Viewer produced the following.

Can
anybody translate this into actual information?

the Event Viewer lists 9 events from 10/8/2016 9:21:03pm thru

11/25/2016
7:29:37pm

Level: Critical
Source: Kernel-Power
EventID: 41
Task Category: (63)
---------
details:
Event 41, Kernel-Power
(Friendly View)
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 4
Level 1
Task 63
Opcode 0
Keywords 0x8000400000000002
- TimeCreated
[ SystemTime] 2016-11-28T00:11:23.707890000Z
EventRecordID 67204
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer name
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 126
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff80139e515b0
BugcheckParameter3 0xffffa3819bfee378
BugcheckParameter4 0xffffa3819bfedba0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 1
CsEntryScenarioInstanceId 0

it also has Details in XML View

- Event

xmlns="http://schemas.microsoft.com/win/2004/08/events/event"
- System
Provider Name="Microsoft-Windows-Kernel-Power"
Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /
EventID41/EventID
Version4/Version
Level1/Level
Task63/Task
Opcode0/Opcode
Keywords0x8000400000000002/Keywords
TimeCreated SystemTime="2016-11-28T00:11:23.707890000Z" /
EventRecordID67204/EventRecordID
Correlation /
Execution ProcessID="4" ThreadID="8" /
ChannelSystem/Channel
ComputerBEWsDesktop64/Computer
Security UserID="S-1-5-18" /
/System
- EventData
Data Name="BugcheckCode"126/Data
Data Name="BugcheckParameter1"0xffffffffc0000005/Data
Data Name="BugcheckParameter2"0xfffff80139e515b0/Data
Data Name="BugcheckParameter3"0xffffa3819bfee378/Data
Data Name="BugcheckParameter4"0xffffa3819bfedba0/Data
Data Name="SleepInProgress"0/Data
Data Name="PowerButtonTimestamp"0/Data
Data Name="BootAppStatus"0/Data
Data Name="Checkpoint"0/Data
Data Name="ConnectedStandbyInProgress"false/Data
Data Name="SystemSleepTransitionsToOn"1/Data
Data Name="CsEntryScenarioInstanceId"0/Data
/EventData
/Event


Hello Bev,

The BugcheckParameter1 looks like a null dereference occurred. The
SystemSleepTransitionsToOn is 1. Perhaps the system was about to go to
sleep and had some kind of issue.

If that is the case perhaps your friend can adjust their sleep settings
so it doesn't try to sleep. That might prevent the problem.


Already set to 'Never". Damn :-(


--
Cheers, Bev
"Nobody ever went broke underestimating the intelligence of the
American Public." -- H.L. Mencken

  #4  
Old November 28th 16, 07:42 AM posted to alt.comp.os.windows-10
The Real Bev[_2_]
external usenet poster
 
Posts: 140
Default "Bugcheck Code 126"

On 11/27/2016 10:11 PM, The Real Bev wrote:
On 11/27/2016 06:34 PM, David LaRue wrote:
The Real Bev wrote in news1g3vm$pn2$1@dont-
email.me:

Friend's Win10 machine keeps crashing -- several times a day, while

she
was working with it. Desktop computer, no heat problem. Bug check
0x7e. Googling has resulted in circular references,
incomprehensibility, and a couple of firefox/linux crashes at the
microsoft site, along with one possibility that the cause is a faulty
USB driver -- that just happened to be one guy's problem, but I saw
others for the 0x7e thing. The Event Viewer produced the following.

Can
anybody translate this into actual information?

the Event Viewer lists 9 events from 10/8/2016 9:21:03pm thru

11/25/2016
7:29:37pm

Level: Critical
Source: Kernel-Power
EventID: 41
Task Category: (63)
---------
details:
Event 41, Kernel-Power
(Friendly View)
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 4
Level 1
Task 63
Opcode 0
Keywords 0x8000400000000002
- TimeCreated
[ SystemTime] 2016-11-28T00:11:23.707890000Z
EventRecordID 67204
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer name
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 126
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff80139e515b0
BugcheckParameter3 0xffffa3819bfee378
BugcheckParameter4 0xffffa3819bfedba0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 1
CsEntryScenarioInstanceId 0

it also has Details in XML View

- Event

xmlns="http://schemas.microsoft.com/win/2004/08/events/event"
- System
Provider Name="Microsoft-Windows-Kernel-Power"
Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /
EventID41/EventID
Version4/Version
Level1/Level
Task63/Task
Opcode0/Opcode
Keywords0x8000400000000002/Keywords
TimeCreated SystemTime="2016-11-28T00:11:23.707890000Z" /
EventRecordID67204/EventRecordID
Correlation /
Execution ProcessID="4" ThreadID="8" /
ChannelSystem/Channel
ComputerBEWsDesktop64/Computer
Security UserID="S-1-5-18" /
/System
- EventData
Data Name="BugcheckCode"126/Data
Data Name="BugcheckParameter1"0xffffffffc0000005/Data
Data Name="BugcheckParameter2"0xfffff80139e515b0/Data
Data Name="BugcheckParameter3"0xffffa3819bfee378/Data
Data Name="BugcheckParameter4"0xffffa3819bfedba0/Data
Data Name="SleepInProgress"0/Data
Data Name="PowerButtonTimestamp"0/Data
Data Name="BootAppStatus"0/Data
Data Name="Checkpoint"0/Data
Data Name="ConnectedStandbyInProgress"false/Data
Data Name="SystemSleepTransitionsToOn"1/Data
Data Name="CsEntryScenarioInstanceId"0/Data
/EventData
/Event


Hello Bev,

The BugcheckParameter1 looks like a null dereference occurred. The
SystemSleepTransitionsToOn is 1. Perhaps the system was about to go to
sleep and had some kind of issue.

If that is the case perhaps your friend can adjust their sleep settings
so it doesn't try to sleep. That might prevent the problem.


Already set to 'Never". Damn :-(


Addendum:

In looking at the logs, what we interpreted as the log entry that
corresponds to crashing the system (as previously reported) was followed
in the logs 20 ms later by what appears to be a logon process --
smss.exe -- in c:\windows\system32\. This is a 64-bit system -- could
this be a 32-bit routine and could this be a/the problem? It seems
puzzling that what appears to be a fatal error could be followed
immediately (20 ms) by a logon process.

A google search indicates that smss.exe and associated system routines
are often the target of malware, but this one seems to be in the right
directory and have the right name. There are several older versions
there (with numbers in parentheses), but the latest version has no number.

--
Cheers, Bev
"Nobody ever went broke underestimating the intelligence of the
American Public." -- H.L. Mencken

  #5  
Old November 28th 16, 08:05 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default "Bugcheck Code 126"

The Real Bev wrote:
On 11/27/2016 10:11 PM, The Real Bev wrote:
On 11/27/2016 06:34 PM, David LaRue wrote:
The Real Bev wrote in news1g3vm$pn2$1@dont-
email.me:

Friend's Win10 machine keeps crashing -- several times a day, while
she
was working with it. Desktop computer, no heat problem. Bug check
0x7e. Googling has resulted in circular references,
incomprehensibility, and a couple of firefox/linux crashes at the
microsoft site, along with one possibility that the cause is a faulty
USB driver -- that just happened to be one guy's problem, but I saw
others for the 0x7e thing. The Event Viewer produced the following.
Can
anybody translate this into actual information?

the Event Viewer lists 9 events from 10/8/2016 9:21:03pm thru
11/25/2016
7:29:37pm

Level: Critical
Source: Kernel-Power
EventID: 41
Task Category: (63)
---------
details:
Event 41, Kernel-Power
(Friendly View)
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 4
Level 1
Task 63
Opcode 0
Keywords 0x8000400000000002
- TimeCreated
[ SystemTime] 2016-11-28T00:11:23.707890000Z
EventRecordID 67204
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer name
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 126
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff80139e515b0
BugcheckParameter3 0xffffa3819bfee378
BugcheckParameter4 0xffffa3819bfedba0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 1
CsEntryScenarioInstanceId 0

it also has Details in XML View

- Event
xmlns="http://schemas.microsoft.com/win/2004/08/events/event"
- System
Provider Name="Microsoft-Windows-Kernel-Power"
Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /
EventID41/EventID
Version4/Version
Level1/Level
Task63/Task
Opcode0/Opcode
Keywords0x8000400000000002/Keywords
TimeCreated SystemTime="2016-11-28T00:11:23.707890000Z" /
EventRecordID67204/EventRecordID
Correlation /
Execution ProcessID="4" ThreadID="8" /
ChannelSystem/Channel
ComputerBEWsDesktop64/Computer
Security UserID="S-1-5-18" /
/System
- EventData
Data Name="BugcheckCode"126/Data
Data Name="BugcheckParameter1"0xffffffffc0000005/Data
Data Name="BugcheckParameter2"0xfffff80139e515b0/Data
Data Name="BugcheckParameter3"0xffffa3819bfee378/Data
Data Name="BugcheckParameter4"0xffffa3819bfedba0/Data
Data Name="SleepInProgress"0/Data
Data Name="PowerButtonTimestamp"0/Data
Data Name="BootAppStatus"0/Data
Data Name="Checkpoint"0/Data
Data Name="ConnectedStandbyInProgress"false/Data
Data Name="SystemSleepTransitionsToOn"1/Data
Data Name="CsEntryScenarioInstanceId"0/Data
/EventData
/Event

Hello Bev,

The BugcheckParameter1 looks like a null dereference occurred. The
SystemSleepTransitionsToOn is 1. Perhaps the system was about to go to
sleep and had some kind of issue.

If that is the case perhaps your friend can adjust their sleep settings
so it doesn't try to sleep. That might prevent the problem.


Already set to 'Never". Damn :-(


Addendum:

In looking at the logs, what we interpreted as the log entry that
corresponds to crashing the system (as previously reported) was followed
in the logs 20 ms later by what appears to be a logon process --
smss.exe -- in c:\windows\system32\. This is a 64-bit system -- could
this be a 32-bit routine and could this be a/the problem? It seems
puzzling that what appears to be a fatal error could be followed
immediately (20 ms) by a logon process.

A google search indicates that smss.exe and associated system routines
are often the target of malware, but this one seems to be in the right
directory and have the right name. There are several older versions
there (with numbers in parentheses), but the latest version has no number.


Was a driver name associated with the bugcheck ?

Like maybe an NVidia video driver ?

Is the bug recurring, or "once only" ?

Paul
  #6  
Old November 28th 16, 05:49 PM posted to alt.comp.os.windows-10
The Real Bev[_2_]
external usenet poster
 
Posts: 140
Default "Bugcheck Code 126"

On 11/27/2016 11:05 PM, Paul wrote:
The Real Bev wrote:
On 11/27/2016 10:11 PM, The Real Bev wrote:
On 11/27/2016 06:34 PM, David LaRue wrote:
The Real Bev wrote in news1g3vm$pn2$1@dont-
email.me:

Friend's Win10 machine keeps crashing -- several times a day, while
she
was working with it. Desktop computer, no heat problem. Bug check
0x7e. Googling has resulted in circular references,
incomprehensibility, and a couple of firefox/linux crashes at the
microsoft site, along with one possibility that the cause is a faulty
USB driver -- that just happened to be one guy's problem, but I saw
others for the 0x7e thing. The Event Viewer produced the following.
Can
anybody translate this into actual information?

the Event Viewer lists 9 events from 10/8/2016 9:21:03pm thru
11/25/2016
7:29:37pm

Level: Critical
Source: Kernel-Power
EventID: 41
Task Category: (63)
---------
details:
Event 41, Kernel-Power
(Friendly View)
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 4
Level 1
Task 63
Opcode 0
Keywords 0x8000400000000002
- TimeCreated
[ SystemTime] 2016-11-28T00:11:23.707890000Z
EventRecordID 67204
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer name
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 126
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff80139e515b0
BugcheckParameter3 0xffffa3819bfee378
BugcheckParameter4 0xffffa3819bfedba0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 1
CsEntryScenarioInstanceId 0

it also has Details in XML View

- Event
xmlns="http://schemas.microsoft.com/win/2004/08/events/event"
- System
Provider Name="Microsoft-Windows-Kernel-Power"
Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /
EventID41/EventID
Version4/Version
Level1/Level
Task63/Task
Opcode0/Opcode
Keywords0x8000400000000002/Keywords
TimeCreated SystemTime="2016-11-28T00:11:23.707890000Z" /
EventRecordID67204/EventRecordID
Correlation /
Execution ProcessID="4" ThreadID="8" /
ChannelSystem/Channel
ComputerBEWsDesktop64/Computer
Security UserID="S-1-5-18" /
/System
- EventData
Data Name="BugcheckCode"126/Data
Data Name="BugcheckParameter1"0xffffffffc0000005/Data
Data Name="BugcheckParameter2"0xfffff80139e515b0/Data
Data Name="BugcheckParameter3"0xffffa3819bfee378/Data
Data Name="BugcheckParameter4"0xffffa3819bfedba0/Data
Data Name="SleepInProgress"0/Data
Data Name="PowerButtonTimestamp"0/Data
Data Name="BootAppStatus"0/Data
Data Name="Checkpoint"0/Data
Data Name="ConnectedStandbyInProgress"false/Data
Data Name="SystemSleepTransitionsToOn"1/Data
Data Name="CsEntryScenarioInstanceId"0/Data
/EventData
/Event

Hello Bev,

The BugcheckParameter1 looks like a null dereference occurred. The
SystemSleepTransitionsToOn is 1. Perhaps the system was about to go to
sleep and had some kind of issue.

If that is the case perhaps your friend can adjust their sleep settings
so it doesn't try to sleep. That might prevent the problem.

Already set to 'Never". Damn :-(


Addendum:

In looking at the logs, what we interpreted as the log entry that
corresponds to crashing the system (as previously reported) was followed
in the logs 20 ms later by what appears to be a logon process --
smss.exe -- in c:\windows\system32\. This is a 64-bit system -- could
this be a 32-bit routine and could this be a/the problem? It seems
puzzling that what appears to be a fatal error could be followed
immediately (20 ms) by a logon process.

A google search indicates that smss.exe and associated system routines
are often the target of malware, but this one seems to be in the right
directory and have the right name. There are several older versions
there (with numbers in parentheses), but the latest version has no number.


Was a driver name associated with the bugcheck ?


That was all the info the bugcheck offered :-(

Like maybe an NVidia video driver ?

Is the bug recurring, or "once only" ?


The rebooting happens several times a day -- when the machine is idle
rather than in use. She comes back into the room and sees that the
machine has rebooted. She looked at the bugcheck log(s) only once.

--
Cheers, Bev
Guns kill people like spoons make Rosie O'Donnell fat.
  #7  
Old November 28th 16, 06:00 PM posted to alt.comp.os.windows-10
Andy Burns[_6_]
external usenet poster
 
Posts: 1,318
Default "Bugcheck Code 126"

The Real Bev wrote:

Paul wrote:

Is the bug recurring, or "once only" ?


The rebooting happens several times a day -- when the machine is idle
rather than in use. She comes back into the room and sees that the
machine has rebooted. She looked at the bugcheck log(s) only once.


Configure it to produce dump files and then install WinDBG to inspect
them for clues?

  #8  
Old November 28th 16, 06:04 PM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 10,449
Default "Bugcheck Code 126"

On Mon, 28 Nov 2016 08:49:01 -0800, The Real Bev
wrote:

On 11/27/2016 11:05 PM, Paul wrote:
Was a driver name associated with the bugcheck ?


That was all the info the bugcheck offered :-(

Like maybe an NVidia video driver ?

Is the bug recurring, or "once only" ?


The rebooting happens several times a day -- when the machine is idle
rather than in use. She comes back into the room and sees that the
machine has rebooted. She looked at the bugcheck log(s) only once.


Sometimes, it's easier to review what's going on with a utility like
Nirsoft's BlueScreenView. Personally, I also tend to configure systems
not to reboot after a crash, but that's less important.

http://www.nirsoft.net/utils/blue_screen_view.html

  #9  
Old November 29th 16, 04:49 AM posted to alt.comp.os.windows-10
The Real Bev[_2_]
external usenet poster
 
Posts: 140
Default "Bugcheck Code 126"

On 11/28/2016 09:04 AM, Char Jackson wrote:
On Mon, 28 Nov 2016 08:49:01 -0800, The Real Bev
wrote:

On 11/27/2016 11:05 PM, Paul wrote:
Was a driver name associated with the bugcheck ?


That was all the info the bugcheck offered :-(

Like maybe an NVidia video driver ?

Is the bug recurring, or "once only" ?


The rebooting happens several times a day -- when the machine is idle
rather than in use. She comes back into the room and sees that the
machine has rebooted. She looked at the bugcheck log(s) only once.


Sometimes, it's easier to review what's going on with a utility like
Nirsoft's BlueScreenView. Personally, I also tend to configure systems
not to reboot after a crash, but that's less important.

http://www.nirsoft.net/utils/blue_screen_view.html


Thanks, that looks promising and NOT OVERLY DIFFICULT. Forwarded on.

--
Cheers, Bev
"The fact that windows is one of the most popular ways to
operate a computer means that evolution has made a general
****up and our race is doomed." -- Anon.


  #10  
Old December 4th 16, 06:13 PM posted to alt.comp.os.windows-10
The Real Bev[_2_]
external usenet poster
 
Posts: 140
Default SOLVED -- "Bugcheck Code 126"

On 11/28/2016 07:49 PM, The Real Bev wrote:
On 11/28/2016 09:04 AM, Char Jackson wrote:
On Mon, 28 Nov 2016 08:49:01 -0800, The Real Bev
wrote:

On 11/27/2016 11:05 PM, Paul wrote:
Was a driver name associated with the bugcheck ?

That was all the info the bugcheck offered :-(

Like maybe an NVidia video driver ?

Is the bug recurring, or "once only" ?

The rebooting happens several times a day -- when the machine is idle
rather than in use. She comes back into the room and sees that the
machine has rebooted. She looked at the bugcheck log(s) only once.


Sometimes, it's easier to review what's going on with a utility like
Nirsoft's BlueScreenView. Personally, I also tend to configure systems
not to reboot after a crash, but that's less important.

http://www.nirsoft.net/utils/blue_screen_view.html


Thanks, that looks promising and NOT OVERLY DIFFICULT. Forwarded on.


Outdated NVIDIA driver. Installed latest one. Crashes stopped. YAY!

--
Cheers, Bev
Jesus saves. Buddha makes incremental backups.
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 03:14 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.