0x7c918fea [Windows XP]

Prev: TFS 2008: cannot export to Excel!
Next: Where did this Folder Come From

From: Curt Christianson on 18 Jan 2008 00:24

Sorry Bob,

*Two* mistakes in a row--way too much caffiene1

--
HTH,

Curt

http://dundats.mvps.org/
http://dundats.proboards27.com/index.cgi
http://www.aumha.org/

"Bob I" <birelan(a)yahoo.com> wrote in message
news:eN0xjcSWIHA.4712(a)TK2MSFTNGP04.phx.gbl...
> Did it reappear on a second bootup?
>
> mc wrote:
>
>> My system is running XP Pro sp2 with the latest patch that I am aware of
>> (I have automatic download on for updates). This morning the following
>> error message popped up during the start up:
>>
>> he instructions at "0x7c918fea" referenced memory at "0x00000010". The
>> memory could not be written.
>>
>> Cannot seem to find that error message in the Microsoft knowledge base.
>> Would appreciate any insight.
>>
>> Thanks.
>

From: user on 18 Jan 2008 06:23

Curt Christianson wrote:
> Sorry Bob,
>
> *Two* mistakes in a row--way too much caffiene1
>

some of that posting re memory not written
doesn't show on my reply...odd.

anyways...it's most likely due to an added
or new component installed that is trying
to place part of itself into a locked area,
or it's going completely out of bounds and
attempting to enter an area doesn't exist.
(mostly guesses from common experience)

hunt for
startup manager

and then check any new installed items in
systray (bottom right of display window)
if necessary press F8 (i think) during
pre boot of OS and enter safe mode then
remove the culprit (can always re install
the program later if you get wrong one).

then run sfc /check to ensure correct
system files are in use
system file checker

also try adaware (lavasoft free edition)
in case some malware is 'bugging' windows.

things like above should be edited for
clarity and sticky post made regularly.

hth

From: mc on 18 Jan 2008 08:39

Thank you for the detailed advise. I am ploughing through them now.
Meanwhile I just noticed an interesting pattern, thought it might mean
something to you. The memory error and all the subsequent errors occurs when
cold boot (power off/on), but seems to cure itself when simply restart. It
comes back when power off/on again.

"nass" wrote:

>
>
> "mc" wrote:
>
>
> System Error/Warning Events
> ================
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7009
> Date: 1/17/2008
> Time: 8:30:45 AM
> User: N/A
> Computer: MOSES-D620
> Description:
> Timeout (30000 milliseconds) waiting for the NICCONFIGSVC service to
> connect.
>
> NICCONFIGSVC: is the Power management settings for network adapters on Dell
> systems.
>
>
> ================
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 1/17/2008
> Time: 8:30:45 AM
> User: N/A
> Computer: MOSES-D620
> Description:
> The NICCONFIGSVC service failed to start due to the following error:
> The service did not respond to the start or control request in a timely
> fashion.
>
> Event ID 7000 appears in the System log and the ISA Server Storage service
> http://support.microsoft.com/kb/884495
>
> Event ID 7009 — Basic Service Operations
> http://technet2.microsoft.com/windowsserver2008/en/library/611a83e2-02de-4f9a-996a-0022c4f2fbe31033.mspx?mfr=true
>
> ================
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10010
> Date: 1/17/2008
> Time: 8:30:53 AM
> User: NT AUTHORITY\SYSTEM
> Computer: MOSES-D620
> Description:
> The server {E85062FB-914A-40A2-8801-5DD803045204} did not register with DCOM
> within the required timeout.
>
> Make sure the "Windows Management Instrumentation Service" is Started Auto
>
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1453453&SiteID=1
>
> An event ID 10010 error message may be logged many times in the event log
> http://support.microsoft.com/kb/909444
>
> http://support.microsoft.com/kb/873375
>
>
> ================
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7034
> Date: 1/17/2008
> Time: 8:32:29 AM
> User: N/A
> Computer: MOSES-D620
> Description:
> The Venturi Client service terminated unexpectedly. It has done this 1
> time(s).
>
> Update the software for Venturi:
> http://www.venturiwireless.com
>
>
> ================
> Event Type: Warning
> Event Source: Print
> Event Category: None
> Event ID: 20
> Date: 1/17/2008
> Time: 12:33:32 PM
> User: NT AUTHORITY\SYSTEM
> Computer: MOSES-D620
> Description:
> Printer Driver Dell Laser Printer 5100cn PCL6 for Windows NT x86 Version-2
> was added or updated. Files:- dlxcrzhk.dll, dlxcrzhu.dll, dlxcrzp.ddd,
> dlxcrz.hlp, dlxcrzhl.dll, dlxcrzhm.dll, dlxcrjdm.dll, dlxcrzhr.xrs,
> dllzjnie.dll, dlzddmif.dll, dlzdhb32.dll, dllznie1.dll, dlzpmc2.dll,
> dlzadcmn.dll, dlzarl32.dll, dlzC5102.dll, dlxcrz.cfg, dlxcrz.cnt, dlxcrz.xrs,
> dlxcrz.cdd.
>
> This a warning can be ignored if you don't have problem with the printer.
>
> ================
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 1/17/2008
> Time: 12:54:31 PM
> User: N/A
> Computer: MOSES-D620
> Description:
> The DataSvr2 service failed to start due to the following error:
> The system cannot find the file specified.
>
> Do you have Wave Systems Corp: An identity protection application installed
> on your system?.
>
>
> ================
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 1/17/2008
> Time: 12:54:31 PM
> User: N/A
> Computer: MOSES-D620
> Description:
> The DgiVecp service failed to start due to the following error:
> The system cannot find the file specified.
>
> Open Services control panel and Disable this service there.
>
> <MS::>
> From: Shain Wray (shainw_at_microsoft.com)
>
> Hello,
>
> It looks like this is a driver that is failing to startup - dgivecp.sys.
> It appears to be installed from either ViewAhead's TeamMFP software or some
> FujiXerox Workcenter app. Either way, as this is not a Microsoft driver,
> then you can disable it if you do not have an application dependency on it.
> You could test this by disabling the driver by doing the following -
>
> 1. Go to Start\Run and type devmgmt.msc
> 2. Click on View and choose to Show Hidden Devices
> 3. Now click the plus next to Non-Plug and Play Drivers
> 4. Do you now see an items listed as DGIVecp? If not, we will have to see
> what this is associated with by going to the registry.
>
> If we need to go into the registry, go to the following location -
>
> 1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
> 2. Look for an entry listed as DgiVecp
> 3. If you find this, then change the Start data value to 4.
> 4. Reboot the system and see if the message is gone.
>
> Let me know how this goes.
>
> Best regards,
>
> --
> Shain Wray
> Microsoft PSS Security Team
> </MS::>
>
> ================
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 1/17/2008
> Time: 12:54:31 PM
> User: N/A
> Computer: MOSES-D620
> Description:
> The SSPORT service failed to start due to the following error:
> The system cannot find the file specified.
>
> The same steps as:
> "The DgiVecp service failed to start due ...... as above"
>
> ================
> Event Type: Error
> Event Source: SideBySide
> Event Category: None
> Event ID: 32
> Date: 1/17/2008
> Time: 12:55:44 PM
> User: N/A
> Computer: MOSES-D620
> Description:
> Dependent Assembly Microsoft.VC80.MFCLOC could not be found and Last Error
> was The referenced assembly is not installed on your system.
>
> http://www.eventid.net/display.asp?eventid=59&eventno=4228&source=SideBySide&phase=1
>
> http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en
> http://forum.piriform.com/index.php?act=Print&client=printer&f=8&t=13581
> ================
> Event Type: Error
> Event Source: SideBySide
> Event Category: None
> Event ID: 59
> Date: 1/17/2008
> Time: 12:55:44 PM
> User: N/A
> Computer: MOSES-D620
> Description:
> Resolve Partial Assembly failed for Microsoft.VC80.MFCLOC. Reference error
> message: The referenced assembly is not installed on your system.
>
> http://support.microsoft.com/kb/923014
>
> http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=118163
> ================
> Event Type: Error
> Event Source: SideBySide
> Event Category: None
> Event ID: 59
> Date: 1/17/2008
> Time: 12:55:44 PM
> User: N/A
> Computer: MOSES-D620
> Description:
> Generate Activation Context failed for
> C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_dec6ddd2\MFC80.DLL.
> Reference error message: The operation completed successfully.
>
>
> ================
>
> No Security Error/Warning Events
> ================
>
> Application Error/Warning Events:
> ================
> Event Type: Warning
> Event Source: MSSQL$MICROSOFTSMLBIZ
> Event Category: (8)
> Event ID: 19011
> Date: 1/17/2008
> Time: 8:29:32 AM
> User: N/A
> Computer: MOSES-D620
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQL$MICROSOFTSMLBIZ )
> cannot be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote computer.
> You may be able to use the /AUXSOURCE= flag to retrieve this description; see
> Help and Support for details. The following information is part of the event:
> (SpnRegister) : Error 1355.
>
> The MSSQL$MICROSOFTBCM service may log event warning 19011 in the event
> http://support.microsoft.com/kb/828246
>
> An "Event ID ( 19011 ) in Source ( MSSQL$MSFW ) cannot be found" message
> http://support.microsoft.com/kb/840473
> How to troubleshoot Business Contact Manager Setup issues:
> http://support.microsoft.com/kb/901163
>
> ================
> Event Type: Error
> Event Source: AutoEnrollment
> Event Category: None
> Event ID: 15
> Date: 1/17/2008
> Time: 8:30:30 AM
> User: N/A
> Computer: MOSES-D620
> Description:
> Automatic certificate enrollment for local system failed to contact the
> active directory (0x8007054b). The specified domain either does not exist or
> could not be contacted.
> Enrollment will not be performed.
>
> Certificate Autoenrollment in Windows Server 2003
> http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/autoenro.mspx
>
> http://www.eventid.net/display.asp?eventid=15&eventno=1397&source=AutoEnrollment&phase=1
>
> ================
> Event Type: Error
> Event Source: Application Hang
> Event Category: (101)
> Event ID: 1002
> Date: 1/17/2008
> Time: 8:32:12 AM
> User: N/A
> Computer: MOSES-D620
> Description:
> Hanging application OUTLOOK.EXE, version 11.0.8169.0, hang module hungapp,
> version 0.0.0.0, hang address 0x00000000.
>
> Do a repair on Office Suite
>
> ================
> Event Type: Warning
> Event Source: Userenv
> Event Category: None
> Event ID: 1517
> Date: 1/17/2008
> Time: 8:33:38 AM
> User: NT AUTHORITY\SYSTEM
> Computer: MOSES-D620
> Description:
> Windows saved user OXXFORDNJ\MCheung registry while an application or

From: Bob I on 18 Jan 2008 09:05

Humm, differences would be power draw, or spin up time on the Harddrive.
What happens if you open the BIOS during a cold boot, effecting a
time delay before windows tries to load?

mc wrote:

> Thank you for the detailed advise. I am ploughing through them now.
> Meanwhile I just noticed an interesting pattern, thought it might mean
> something to you. The memory error and all the subsequent errors occurs when
> cold boot (power off/on), but seems to cure itself when simply restart. It
> comes back when power off/on again.
>
> "nass" wrote:
>
>
>>
>>"mc" wrote:
>>
>>
>>System Error/Warning Events
>>================
>>Event Type: Error
>>Event Source: Service Control Manager
>>Event Category: None
>>Event ID: 7009
>>Date: 1/17/2008
>>Time: 8:30:45 AM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>Timeout (30000 milliseconds) waiting for the NICCONFIGSVC service to
>>connect.
>>
>>NICCONFIGSVC: is the Power management settings for network adapters on Dell
>>systems.
>>
>>
>>================
>>Event Type: Error
>>Event Source: Service Control Manager
>>Event Category: None
>>Event ID: 7000
>>Date: 1/17/2008
>>Time: 8:30:45 AM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>The NICCONFIGSVC service failed to start due to the following error:
>>The service did not respond to the start or control request in a timely
>>fashion.
>>
>>Event ID 7000 appears in the System log and the ISA Server Storage service
>>http://support.microsoft.com/kb/884495
>>
>>Event ID 7009 â Basic Service Operations
>>http://technet2.microsoft.com/windowsserver2008/en/library/611a83e2-02de-4f9a-996a-0022c4f2fbe31033.mspx?mfr=true
>>
>>================
>>Event Type: Error
>>Event Source: DCOM
>>Event Category: None
>>Event ID: 10010
>>Date: 1/17/2008
>>Time: 8:30:53 AM
>>User: NT AUTHORITY\SYSTEM
>>Computer: MOSES-D620
>>Description:
>>The server {E85062FB-914A-40A2-8801-5DD803045204} did not register with DCOM
>>within the required timeout.
>>
>>Make sure the "Windows Management Instrumentation Service" is Started Auto
>>
>>http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1453453&SiteID=1
>>
>>An event ID 10010 error message may be logged many times in the event log
>>http://support.microsoft.com/kb/909444
>>
>>http://support.microsoft.com/kb/873375
>>
>>
>>================
>>Event Type: Error
>>Event Source: Service Control Manager
>>Event Category: None
>>Event ID: 7034
>>Date: 1/17/2008
>>Time: 8:32:29 AM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>The Venturi Client service terminated unexpectedly. It has done this 1
>>time(s).
>>
>>Update the software for Venturi:
>>http://www.venturiwireless.com
>>
>>
>>================
>>Event Type: Warning
>>Event Source: Print
>>Event Category: None
>>Event ID: 20
>>Date: 1/17/2008
>>Time: 12:33:32 PM
>>User: NT AUTHORITY\SYSTEM
>>Computer: MOSES-D620
>>Description:
>>Printer Driver Dell Laser Printer 5100cn PCL6 for Windows NT x86 Version-2
>>was added or updated. Files:- dlxcrzhk.dll, dlxcrzhu.dll, dlxcrzp.ddd,
>>dlxcrz.hlp, dlxcrzhl.dll, dlxcrzhm.dll, dlxcrjdm.dll, dlxcrzhr.xrs,
>>dllzjnie.dll, dlzddmif.dll, dlzdhb32.dll, dllznie1.dll, dlzpmc2.dll,
>>dlzadcmn.dll, dlzarl32.dll, dlzC5102.dll, dlxcrz.cfg, dlxcrz.cnt, dlxcrz.xrs,
>>dlxcrz.cdd.
>>
>>This a warning can be ignored if you don't have problem with the printer.
>>
>>================
>>Event Type: Error
>>Event Source: Service Control Manager
>>Event Category: None
>>Event ID: 7000
>>Date: 1/17/2008
>>Time: 12:54:31 PM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>The DataSvr2 service failed to start due to the following error:
>>The system cannot find the file specified.
>>
>>Do you have Wave Systems Corp: An identity protection application installed
>>on your system?.
>>
>>
>>================
>>Event Type: Error
>>Event Source: Service Control Manager
>>Event Category: None
>>Event ID: 7000
>>Date: 1/17/2008
>>Time: 12:54:31 PM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>The DgiVecp service failed to start due to the following error:
>>The system cannot find the file specified.
>>
>>Open Services control panel and Disable this service there.
>>
>><MS::>
>>From: Shain Wray (shainw_at_microsoft.com)
>>
>>Hello,
>>
>>It looks like this is a driver that is failing to startup - dgivecp.sys.
>>It appears to be installed from either ViewAheadâs TeamMFP software or some
>>FujiXerox Workcenter app. Either way, as this is not a Microsoft driver,
>>then you can disable it if you do not have an application dependency on it.
>>You could test this by disabling the driver by doing the following -
>>
>>1. Go to Start\Run and type devmgmt.msc
>>2. Click on View and choose to Show Hidden Devices
>>3. Now click the plus next to Non-Plug and Play Drivers
>>4. Do you now see an items listed as DGIVecp? If not, we will have to see
>>what this is associated with by going to the registry.
>>
>>If we need to go into the registry, go to the following location -
>>
>>1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
>>2. Look for an entry listed as DgiVecp
>>3. If you find this, then change the Start data value to 4.
>>4. Reboot the system and see if the message is gone.
>>
>>Let me know how this goes.
>>
>>Best regards,
>>
>>--
>>Shain Wray
>>Microsoft PSS Security Team
>></MS::>
>>
>>================
>>Event Type: Error
>>Event Source: Service Control Manager
>>Event Category: None
>>Event ID: 7000
>>Date: 1/17/2008
>>Time: 12:54:31 PM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>The SSPORT service failed to start due to the following error:
>>The system cannot find the file specified.
>>
>>The same steps as:
>>"The DgiVecp service failed to start due ...... as above"
>>
>>================
>>Event Type: Error
>>Event Source: SideBySide
>>Event Category: None
>>Event ID: 32
>>Date: 1/17/2008
>>Time: 12:55:44 PM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>Dependent Assembly Microsoft.VC80.MFCLOC could not be found and Last Error
>>was The referenced assembly is not installed on your system.
>>
>>http://www.eventid.net/display.asp?eventid=59&eventno=4228&source=SideBySide&phase=1
>>
>>http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en
>>http://forum.piriform.com/index.php?act=Print&client=printer&f=8&t=13581
>>================
>>Event Type: Error
>>Event Source: SideBySide
>>Event Category: None
>>Event ID: 59
>>Date: 1/17/2008
>>Time: 12:55:44 PM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>Resolve Partial Assembly failed for Microsoft.VC80.MFCLOC. Reference error
>>message: The referenced assembly is not installed on your system.
>>
>>http://support.microsoft.com/kb/923014
>>
>>http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=118163
>>================
>>Event Type: Error
>>Event Source: SideBySide
>>Event Category: None
>>Event ID: 59
>>Date: 1/17/2008
>>Time: 12:55:44 PM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>Generate Activation Context failed for
>>C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_dec6ddd2\MFC80.DLL.
>>Reference error message: The operation completed successfully.
>>
>>
>>================
>>
>>No Security Error/Warning Events
>>================
>>
>>Application Error/Warning Events:
>>================
>>Event Type: Warning
>>Event Source: MSSQL$MICROSOFTSMLBIZ
>>Event Category: (8)
>>Event ID: 19011
>>Date: 1/17/2008
>>Time: 8:29:32 AM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>The description for Event ID ( 19011 ) in Source ( MSSQL$MICROSOFTSMLBIZ )
>>cannot be found. The local computer may not have the necessary registry
>>information or message DLL files to display messages from a remote computer.
>>You may be able to use the /AUXSOURCE= flag to retrieve this description; see
>>Help and Support for details. The following information is part of the event:
>>(SpnRegister) : Error 1355.
>>
>>The MSSQL$MICROSOFTBCM service may log event warning 19011 in the event
>>http://support.microsoft.com/kb/828246
>>
>>An "Event ID ( 19011 ) in Source ( MSSQL$MSFW ) cannot be found" message
>>http://support.microsoft.com/kb/840473
>>How to troubleshoot Business Contact Manager Setup issues:
>>http://support.microsoft.com/kb/901163
>>
>>================
>>Event Type: Error
>>Event Source: AutoEnrollment
>>Event Category: None
>>Event ID: 15
>>Date: 1/17/2008
>>Time: 8:30:30 AM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>Automatic certificate enrollment for local system failed to contact the
>>active directory (0x8007054b). The specified domain either does not exist or
>>could not be contacted.
>>Enrollment will not be performed.
>>
>>Certificate Autoenrollment in Windows Server 2003
>>http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/autoenro.mspx
>>
>>http://www.eventid.net/display.asp?eventid=15&eventno=1397&source=AutoEnrollment&phase=1
>>
>>================
>>Event Type: Error
>>Event Source: Application Hang
>>Event Category: (101)
>>Event ID: 1002
>>Date: 1/17/2008
>>Time: 8:32:12 AM
>>User: N/A
>>Computer: MOSES-D620
>>Description:
>>Hanging application OUTLOOK.EXE, version 11.0.8169.0, hang module hungapp,
>>version 0.0.0.0, hang address 0x00000000.
>>
>>Do a repair on Office Suite
>>
>>================
>>Event Type: Warning
>>Event Source: Userenv
>>Event Category: None
>>Event ID: 1517
>>Date: 1/17/2008
>>Time: 8:33:38 AM
>>User: NT AUTHORITY\SYSTEM
>>Computer: MOSES-D620
>>Description:
>>Windows saved user OXXFORDNJ\MCheung registry while an application or

First | Prev |
Pages: 1 2 3 4 5
Prev: TFS 2008: cannot export to Excel!
Next: Where did this Folder Come From