1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista How to find out error msg

Discussion in 'Legacy Windows' started by sree2403, 2009/11/27.

  1. 2009/11/27
    sree2403

    sree2403 Inactive Thread Starter

    Joined:
    2009/01/12
    Messages:
    30
    Likes Received:
    0
    Sir,
    My sony vaio vgn cr24 laptop is preloaded with vista home premiun. Some times it is shutting down automatically in between. Can I find out the BSOD Msg when it is shutting down by changing any bios/other configurations. Plse help.

    Regards
    Sree
     
  2. 2009/11/27
    broni

    broni Moderator Malware Analyst

    Joined:
    2002/08/01
    Messages:
    21,701
    Likes Received:
    116
    ...if shutdown is caused by BSOD

    First, make sure your setting is correct...

    1. Click Start, point to Settings, and then click Control Panel (Start>Control Panel in Vista).
    2. Double-click System.
    3. Click (Advanced system settings link in Vista, then --->)the Advanced tab, and then click Settings under Startup and Recovery.
    4. Make sure, there is a checkmark in Write an event to the system log.
    5. In the Write debugging information list, click Small memory dump (64k).


    Then....

    Download BlueScreenView
    No installation required.
    Double click on BlueScreenView.exe file to run the program.
    When scanning is done, go Edit>Select All.
    Go File>Save Selected Items, and save the report as BSOD.txt.
    Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
     

  3. to hide this advert.

  4. 2009/11/28
    sree2403

    sree2403 Inactive Thread Starter

    Joined:
    2009/01/12
    Messages:
    30
    Likes Received:
    0
    Thank you Broni.
    Unexpected shutdown of my system is happening very rarely (only twice in three months). Anyway I an doing the above followups and come to u at next occurrence.

    Regards
    Sree
     
  5. 2009/11/28
    broni

    broni Moderator Malware Analyst

    Joined:
    2002/08/01
    Messages:
    21,701
    Likes Received:
    116
    Keep us posted :)
     
  6. 2009/11/29
    sree2403

    sree2403 Inactive Thread Starter

    Joined:
    2009/01/12
    Messages:
    30
    Likes Received:
    0
    Sir,
    Now my system is crashing very frequently. I have done all the above procedure as told by you but my bluescreenview is not showing any thing. Is this an OS problem or Hardware related ? Plse advice
     
  7. 2009/11/29
    broni

    broni Moderator Malware Analyst

    Joined:
    2002/08/01
    Messages:
    21,701
    Likes Received:
    116
    Download, and install SpeedFan: http://www.almico.com/sfdownload.php
    Post your computer temperatures:

    [​IMG]

    Provide processor info (hold Windows logo key, and hit Pause/Break key to find out).
     
  8. 2009/11/30
    sree2403

    sree2403 Inactive Thread Starter

    Joined:
    2009/01/12
    Messages:
    30
    Likes Received:
    0
    Sir,
    I installed Speedfan and while running it is not showing any fan speed in the left pane. At starting the temp shown are core0 37 deg c and core1 37 deg c. After a short duration it was 40 deg c each and it was again shooting up to above 50 and red indication came on the display. It is not showing any fan as in your display example. Waiting for your advice

    Regards
    Sree
     
  9. 2009/11/30
    broni

    broni Moderator Malware Analyst

    Joined:
    2002/08/01
    Messages:
    21,701
    Likes Received:
    116
    That's fine. Sometimes, fans won't show.
    Temps look normal for a laptop.

    Please download VEW and save it to your Desktop: http://images.malwareremoval.com/vino/VEW.exe

    Double-click VEW.exe then under Select log to query, select:
    Application
    System


    Under Select type to list, select:
    Critical (Vista only)
    Error


    Click the radio button for Number of events
    Type 20 in the 1 to 20 box
    Then click the Run button.
    Notepad will open with the output log.

    In Notepad, click Edit > Select all then Edit > Copy
    Reply to this post, click in the reply window and press Ctrl+V on your keyboard to paste the log.
     
  10. 2009/12/01
    sree2403

    sree2403 Inactive Thread Starter

    Joined:
    2009/01/12
    Messages:
    30
    Likes Received:
    0
    Sir,
    I will do the last step you mentioned. My Laptop is dual booting with Windows XP and Vista. Both the OS is randomly shutting down. Will come to you with VEW.exe results.

    Regards
    Sree
     
  11. 2009/12/01
    sree2403

    sree2403 Inactive Thread Starter

    Joined:
    2009/01/12
    Messages:
    30
    Likes Received:
    0
    Sir,
    I have run the VEW.exe and the result are follows:
    Vino's Event Viewer v01c run on Windows Vista in English
    Report run at 01/12/2009 19:29:01

    Note: All dates below are in the format dd/mm/yyyy

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'Application' Log - Critical Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'Application' Log - Error Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'Application' Date/Time: 20/08/2008 05:34:35
    Type: Error Category: 0
    Event: 12346 Source: VSS
    Volume Shadow Copy Error: An error 0x8000ffff was encountered while trying to initialize the Registry Writer. This may cause future shadow-copy creations to fail.

    Log: 'Application' Date/Time: 20/08/2008 05:37:58
    Type: Error Category: 0
    Event: 7 Source: VzCdbSvc
    Failed to load the plug-in module. (GUID = {56F9312C-C989-4E04-8C23-299DEE3A36F5})(Error code = 0x80042019)

    Log: 'Application' Date/Time: 20/08/2008 05:38:23
    Type: Error Category: 0
    Event: 5007 Source: WerSvc
    The target file for the Windows Feedback Platform (a DLL file containing the list of problems on this computer that require additional data collection for diagnosis) could not be parsed. The error code was 8014FFF9.

    Log: 'Application' Date/Time: 20/08/2008 05:43:05
    Type: Error Category: 3
    Event: 215 Source: ESENT
    WinMail (3336) WindowsMail0: The backup has been stopped because it was halted by the client or the connection with the client failed.

    Log: 'Application' Date/Time: 20/08/2008 05:47:03
    Type: Error Category: 0
    Event: 1008 Source: Microsoft-Windows-Perflib
    The Open Procedure for service "DFSR" in DLL "C:\Windows\System32\DfsrPerf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

    Log: 'Application' Date/Time: 20/08/2008 05:47:03
    Type: Error Category: 0
    Event: 1010 Source: Microsoft-Windows-Perflib
    The Collect Procedure for the "EmdCache" service in DLL "C:\Windows\system32\emdmgmt.dll" generated an exception or returned an invalid status. The performance data returned by the counter DLL will not be returned in the Perf Data Block. The first four bytes (DWORD) of the Data section contains the exception code or status code.

    Log: 'Application' Date/Time: 20/08/2008 05:47:06
    Type: Error Category: 0
    Event: 1008 Source: Microsoft-Windows-Perflib
    The Open Procedure for service "PNRPsvc" in DLL "C:\Windows\system32\pnrpperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

    Log: 'Application' Date/Time: 20/08/2008 05:47:06
    Type: Error Category: 0
    Event: 1005 Source: Microsoft-Windows-Perflib
    Unable to locate the open procedure "OpenIPSecPerformanceData" in DLL "C:\Windows\System32\ipsecsvc.dll" for the "PolicyAgent" service. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

    Log: 'Application' Date/Time: 20/08/2008 05:47:06
    Type: Error Category: 0
    Event: 1017 Source: Microsoft-Windows-Perflib
    Disabled performance counter data collection from the "PolicyAgent" service because the performance counter library for that service has generated one or more errors. The errors that forced this action have been written to the application event log. Correct the errors before enabling the performance counters for this service.

    Log: 'Application' Date/Time: 20/08/2008 05:47:14
    Type: Error Category: 0
    Event: 2004 Source: usbperf
    Usbperf data collection failed. Collect function called with usupported Query Type.

    Log: 'Application' Date/Time: 20/08/2008 05:48:56
    Type: Error Category: 0
    Event: 8194 Source: VSS
    Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005. This is often caused by incorrect security settings in either the writer or requestor process.

    Operation:
    Gathering Writer Data

    Context:
    Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Name: System Writer
    Writer Instance ID: {309958e5-595b-44ed-8bdc-890c4e7ca783}

    Log: 'Application' Date/Time: 20/08/2008 05:52:52
    Type: Error Category: 0
    Event: 2004 Source: usbperf
    Usbperf data collection failed. Collect function called with usupported Query Type.

    Log: 'Application' Date/Time: 20/08/2008 05:57:14
    Type: Error Category: 0
    Event: 1023 Source: Microsoft-Windows-Perflib
    Windows cannot load the extensible counter DLL Outlook. The first four bytes (DWORD) of the Data section contains the Windows error code.

    Log: 'Application' Date/Time: 20/08/2008 05:57:25
    Type: Error Category: 0
    Event: 2004 Source: usbperf
    Usbperf data collection failed. Collect function called with usupported Query Type.

    Log: 'Application' Date/Time: 20/08/2008 06:00:59
    Type: Error Category: 0
    Event: 7 Source: VzCdbSvc
    Failed to load the plug-in module. (GUID = {56F9312C-C989-4E04-8C23-299DEE3A36F5})(Error code = 0x80042019)

    Log: 'Application' Date/Time: 20/08/2008 06:01:09
    Type: Error Category: 0
    Event: 5007 Source: WerSvc
    The target file for the Windows Feedback Platform (a DLL file containing the list of problems on this computer that require additional data collection for diagnosis) could not be parsed. The error code was 8014FFF9.

    Log: 'Application' Date/Time: 20/08/2008 06:02:59
    Type: Error Category: 0
    Event: 1008 Source: Microsoft-Windows-Perflib
    The Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

    Log: 'Application' Date/Time: 20/08/2008 06:03:10
    Type: Error Category: 0
    Event: 2004 Source: usbperf
    Usbperf data collection failed. Collect function called with usupported Query Type.

    Log: 'Application' Date/Time: 20/08/2008 06:05:02
    Type: Error Category: 0
    Event: 1013 Source: MsiInstaller
    Product: Adobe Reader 8 -- Setup has detected that you already have a more functional product installed. Setup will now terminate.

    Log: 'Application' Date/Time: 20/08/2008 06:05:50
    Type: Error Category: 0
    Event: 2004 Source: usbperf
    Usbperf data collection failed. Collect function called with usupported Query Type.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Critical Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 30/08/2008 21:06:17
    Type: Critical Category: 0
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Error Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 20/08/2008 06:01:37
    Type: Error Category: 0
    Event: 7000 Source: Service Control Manager
    The Parallel port driver service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

    Log: 'System' Date/Time: 20/08/2008 06:29:52
    Type: Error Category: 0
    Event: 10010 Source: Microsoft-Windows-DistributedCOM
    The server {C2BFE331-6739-4270-86C9-493D9A04CD38} did not register with DCOM within the required timeout.

    Log: 'System' Date/Time: 26/08/2008 04:59:05
    Type: Error Category: 0
    Event: 7000 Source: Service Control Manager
    The Parallel port driver service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

    Log: 'System' Date/Time: 30/08/2008 18:59:00
    Type: Error Category: 0
    Event: 7000 Source: Service Control Manager
    The Parallel port driver service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

    Log: 'System' Date/Time: 30/08/2008 20:24:35
    Type: Error Category: 0
    Event: 6008 Source: EventLog
    The previous system shutdown at 13:22:57 on 30-08-2008 was unexpected.

    Log: 'System' Date/Time: 30/08/2008 20:26:00
    Type: Error Category: 0
    Event: 7000 Source: Service Control Manager
    The Parallel port driver service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

    Log: 'System' Date/Time: 30/08/2008 20:36:55
    Type: Error Category: 0
    Event: 10010 Source: Microsoft-Windows-DistributedCOM
    The server {03E0E6C2-363B-11D3-B536-00902771A435} did not register with DCOM within the required timeout.

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4375 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of setting package WUClient-SelfUpdate-Aux (Feature Pack) into Install Requested(Install Requested) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-Neutral from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-en-US-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-ja-JP-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-ar-sa-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-zh-CN-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-zh-TW-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-cs-CZ-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-da-DK-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-de-DE-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-el-GR-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-es-ES-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Log: 'System' Date/Time: 30/08/2008 20:47:23
    Type: Error Category: 0
    Event: 4385 Source: Microsoft-Windows-Servicing
    Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Aux-fi-FI-LP-Toplevel from package WUClient-SelfUpdate-Aux(Feature Pack) into Staged(Staged) state

    Regards
    Sree
     
  12. 2009/12/01
    broni

    broni Moderator Malware Analyst

    Joined:
    2002/08/01
    Messages:
    21,701
    Likes Received:
    116

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.