Re: sudden reboot
- From: "anon" <vxpy7do02@xxxxxxxxxxxxxx>
- Date: Thu, 1 Feb 2007 14:44:00 -0800
See inline comments.
"Wesley Vogel" <123WVogel955@xxxxxxxxxxx> wrote in message news:%23HdOizhRHHA.1364@xxxxxxxxxxxxxxxxxxxxxxx
Hi anon,
My *guess* is a video driver.
How does that cause the problem (this is a one year old computer) and how do I fix it (new driver???)?
No new hardware and only MS updates.
0x0000000A Typically due to a bad driver, or faulty or incompatible
hardware or software.
See...
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
here...
TROUBLESHOOTING WINDOWS STOP MESSAGES
http://www.aumha.org/win5/kbestop.htm
Major problem is that this is VERY intermittent and these KBs refer to 'first time you reboot after...'
I assume that these are the services that were running:
Networking .NETFramework ASP.NET ASP.NET_1.1.4322 ContentFilter ContentIndex
Fax ISAPI Search PerfDisk PerfNet PerfOS4 hhPerf ProcPSched RemoteAccess
RSVP Spooler TapiSrv Tcpip TermService VMware WmiApRpl
How do I make these 'not needed' services not run - particularly which should be removed?
There are two stand-alone computers connected to a router (the two are not networked to a server/)
Is FAX service = 'this computer sends and/or receives FAXES'?
Maybe a comment in regard to each of the services on the list or just an explanation of the ones you think should not run (your choice of detail.)
If you think half of the crap should not run - I agree as they are using unnecessary resources.
You are helpful - I just need a little boost to know what to do next.
Networking: ???
.NET Framework
ASP.NET
ASP.NET_1.1.4322
ContentFilter: cidaemon.exe = Content Indexing service filter Daemon
ContentIndex: cisvc.exe = Content Index SerViCe or Indexing service
Fax: Fax service
ISAPI Search: Related to Content Indexing service
PerfDisk: Windows Disk Performance perfdisk.dll & perfmon.msc
PerfNet: Windows System Performance
PerfOS: Windows System Performance
ProcPSched: ???
RemoteAcces: Routing and Remote Access service
RSVP: QoS RSVP service
Spooler: Print spooler service
TapiSrv: Telephony sevice needed for the Fax service
Tcpip: TCP/IP Protocol Driver
TermService: Terminal Services
VMware: ????
WmiApRpl: WmiCollectPerfData Windows Mangement Instrumentation (WMI) related
to Windows System Performance
Half of this crap doesn't need to be running in my opinion.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In news:%23a2%23wSXRHHA.5064@xxxxxxxxxxxxxxxxxxxx,
anon <vxpy7do02@xxxxxxxxxxxxxx> hunted and pecked:
Appreciate any clarification you glean form this info.Networking.NETFrameworkASP.NETASP.NET_1.1.4322ContentFilterContentIndexFaxIS
BINGO -- BSD finally hit this morning. I was able to restart without error
(same as previous.)
I had started the computer and then left it for a while, after power saver
kicked in (screen went black and the power switch light was blinking) and
I wanted to wake it up, I hit a key to wake the computer up, the keyboard
and mouse acted as if the computer was waking up - but the BSD appeared as
follows.
Here is the information that appeared on the screen-
Problem detected and computer shut down.
IRQL_NOT_LESS_OR_EQUAL
lines of text
Technical information:
*** STOP: 0x0000000A (0x9D2D26BC, 0x00000002, 0x00000000, 0x8050E07A)
Beginning dump of physical memory
physical memory dump complete
Contact system administrator...
On reboot an error message appeared asking whether I wanted to report the
error to MS (I did) - these are the files is said it would send.
Three files saved for report to MS
One is zero bytes long, one 'is in use of another program' so cannot be
accessed, the third follows:
---file---
gE#.NET CLR Data.NET CLR
APISearchPerfDiskPerfNetPerfOS4
hhPerfProcPSchedRemoteAccessRSVPSpoolerTapiSrvTcpipTermServiceVMwareWmiApRpl
---end file---
"anon" <vxpy7do02@xxxxxxxxxxxxxx> wrote in message
news:uoJmNTYQHHA.1364@xxxxxxxxxxxxxxxxxxxxxxx
Did as suggested and will let you know what happens next.
There MUST have been a BSOD between the blank screen and the restart
procedure.
"Wesley Vogel" <123WVogel955@xxxxxxxxxxx> wrote in message
news:uSYU2PYQHHA.4736@xxxxxxxxxxxxxxxxxxxxxxx
This won't fix your problem, but it'll keep your machine from rebooting,
unless the rebooting is caused by a hardware problem. To fix that you
need
to fix the hardware problem.
It may also help reading a BSOD. Blue Screen Of Death.
Choosing recovery actions if Windows stops unexpectedly.
Right click My Computer | Properties | Advanced tab |
Click the Settings button under Startup and Recovery |
Under System Failure | UNCheck: Automatically restart |
Click OK | Click Apply | Click OK
Automatically restart
[[Specifies whether Windows will automatically reboot whenever the
system stops unexpectedly.
You must be logged on as a member of the Administrators group to set
recovery options.]]
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In news:OQHsSDYQHHA.4088@xxxxxxxxxxxxxxxxxxxx,
anon <vxpy7do02@xxxxxxxxxxxxxx> hunted and pecked:
When I press a key to exit from an automatic standby Computer has gone
to
screen saver, then blank (black) screen [normal], and then to the
blinking
light in the power switch. - (pressing a key usually turns on the
screen to previous state), instead the computer reboots instead of
just waking up.
The system error log is copied below.
This has happened twice in the last couple of days.
How to fix??
---copy--
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/26/2007
Time: 11:12:13 AM
User: N/A
Computer: GEORGENEW
Description:
Error code 1000000a, parameter1 917e68ec, parameter2 00000002,
parameter3
00000000, parameter4 8050e07a.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 39 31 eters 91
0030: 37 65 36 38 65 63 2c 20 7e68ec,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 35 30 00, 8050
0050: 65 30 37 61 e07a
.
- Follow-Ups:
- Re: sudden reboot
- From: Wesley Vogel
- Re: sudden reboot
- From: anon
- Re: sudden reboot
- References:
- Re: sudden reboot
- From: Wesley Vogel
- Re: sudden reboot
- Prev by Date: Re: Clock on pc time loss
- Next by Date: Re: slow pc - svchost
- Previous by thread: Re: sudden reboot
- Next by thread: Re: sudden reboot
- Index(es):