More blue screens...

Discussion in 'Windows Vista General Discussion' started by Marshall, Jul 3, 2006.

  1. Marshall

    Marshall Guest

    Hi guys,

    I've been searching the net high and low for solutions to my problem and no
    such luck as yet! Firstly, I do understand that I am running a beta, and it
    will be buggy. But it would seem that I am having some more dramas than most
    people in regards to the blue screen errors.

    My blue screen problem appears randomly, and I cannot see a pattern in it's
    occurrence. The error report states the following:

    ------------------------------------------------------------------------------------------------
    Problem signature
    Problem Event Name: BLUESCREEN
    OS Version: 6.0.5384.2.0.0.256.1
    Locale ID: 3081

    Files that help describe the problem (some files may no longer be available)
    Mini070306-06.dmp
    sysdata.xml
    Version.txt

    View a temporary copy of these files
    Warning: If a virus or other security threat caused the problem, opening a
    copy of the files could harm your computer.

    Extra information about the problem
    BCCode: 1000008e
    BCP1: C0000046
    BCP2: 8208A531
    BCP3: 996B57B4
    BCP4: 00000000
    OS Version: 6_0_5384
    Service Pack: 0_0
    Product: 256_1

    ------------------------------------------------------------------------------------------------

    So... This error is the same error that is always recorded from what I can
    see (all error logs say the same thing). I don't understand what exactly is
    causing the error?

    I am also running the recommended avast! virus protection if that helps...

    Any ideas... anyone??

    Thanks for your time!
    -Marshall
     
    Marshall, Jul 3, 2006
    #1
    1. Advertisements

  2. Marshall

    Marshall Guest

    All apologies for the excessive posts... the board told me it had failed and
    I hit resubmit...
     
    Marshall, Jul 3, 2006
    #2
    1. Advertisements

  3. Marshall

    Chad Harris Guest

    Marshall:

    The location of the log for your error connected with the BSOD would be

    \windows\system32\logfiles\srt\srttrail.log

    If you have a Vista DVD, there is a promising "feature" or utility in Vista
    called Win RE or Windows Recovery Environment.

    ***Accessing Windows RE (Repair Environment):***

    1) Insert Media into PC (the DVD you burned)

    2) ***You will see on the Vista logo setup screen after lang. options in the
    lower left corner, a link called "System Recovery Options."***

    3) Select your OS for repair.

    4) Its been my experience that you can see some causes of the crash from
    theWin RE feature:

    You'll have a choice there of using:

    1) Startup Repair
    2) System Restore
    3) Complete PC Restore

    Fabricant is also a feature but I'm not sure what its status is in Beta
    2/5456.5 currently.

    Good luck,

    CH
     
    Chad Harris, Jul 3, 2006
    #3
  4. Marshall

    Marshall Guest

    Hi Chad,

    Thankyou for the help, unfortunately it hasn't yielded a positive result!

    Here is what my log file says..
    ------------------------------------------------------------------------------------------------
    Session Summary:
    System Disk = \Device\Harddisk0
    WinDir = C:\Windows
    AutoChk Run = 0
    Root causes = 1

    Test Performed:
    ---------------------------
    Name: Disk meta data test
    Result: Completed successfully. Error code = 0x0
    Time taken = 31 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 78 ms

    Test Performed:
    ---------------------------
    Name: Determine target OS
    Result: Completed successfully. Error code = 0x0
    Time taken = 156 ms

    Test Performed:
    ---------------------------
    Name: Quick volume metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 156 ms

    Test Performed:
    ---------------------------
    Name: Boot manager log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Event log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 110 ms

    Test Performed:
    ---------------------------
    Name: Reentry state check
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Boot status test
    Result: Completed successfully. Error code = 0x0
    Time taken = 15 ms

    Root cause found:
    ---------------------------
    Boot status indicates that the OS booted successfully.

    ---------------------------
    --------------------------
    ------------------------------------------------------------------------------------------------

    Now just to clarify, I did try the windows repair environment but was
    unsuccessful in resolving any issues... I didn't do system restore etc as I
    didn't want to revert to a previous state on my pc.... I have done a restore
    prior to this and it was unsuccessful also...

    Any ideas?

    Thanks again
    -Marshall
     
    Marshall, Jul 3, 2006
    #4
  5. Marshall

    Chad Harris Guest

    Marshall--

    The data in the log is encoded/or encrypted in a sense enough so that I
    can't make any reasonable sense out of it. Someone from the Win RE/recovery
    type teams might be able to. Apparently you don't have a no boot situation
    but rather you have intermittent BSOD stops that may be crescendoing in
    frequency.

    Obviously HDW drivers are frequent causes of these, but I have no error
    message to go on in the traditional stop error sense. I'd urge you to try a
    couple things:

    Since Win RE offers 3 possibilities to try I'd try all of them--I can't know
    what you mean when you said you tried the "win repair environment" and there
    are at least two entities besides SR here. I have no idea whether Fabricant
    is workable in Vista at this time.

    1) Startup Repair
    2)System Restore
    3) Complete PC Restore

    You can try system restore last. My attitude toward it is that I try every
    potential viable restore point to get back. You say you don't want to use
    SR, but if you get to a place where the BSOD interruptions stop, that's much
    better than where you are now. I don't follow your logic in not wanting to
    use a restore point if it gets you out of this situation.

    Theoretically, System restore in vista is deeper, more systemic, and more
    powerful making use of Volume Shadow Services.

    An additional move you might try since you have not indicated that you
    cannot boot to Windows, but "have a blue screen problem that appears
    randomly", is that while in Windows, go to the run box and type in the run
    box driver verifyer and I want you to use the directions in this article to
    disable deadlock detection and inspection of any software drivers associated
    with Avast. Be clear that this in no way keeps Avast from running
    effectively, but it stops what I have seen cause a percent of blue screens
    in XP and possibly in Vista which is deadlock detection and inspection of
    antivirus program software drivers by driver verifier enabled.

    I have seen this aid in a variety of BSOD situations in XP even when a
    repair install (an option not in Vista and replaced by the more robust Win
    RE components) had been done successfully. I have seen individuals on the
    MSFT device teams state nearly all BSODs are due to drivers and I certainly
    respectfully believe that is a vast over-simplification. I don't have a
    stop error here are meaningful error messages. Win RE will often offer some
    explanations of the problem more specific than the info that's not helpful
    to us right now from the log. Follow these steps:

    1. Click Start, click Run, and then type verifier.
    2. After Driver Verifier Manager starts, click Display Existing
    Settings, and then confirm that Deadlock Detection is turned on.
    3. Click Back.
    4. Click Create Custom Settings, and then click Next.
    5. Click Select Individual settings from a full list, and then click
    Next.
    6. Click the settings that you want to turn on, make sure the Deadlock
    Detection check box is not selected, and then click Next.
    7. Click the drivers that you want to verify, and then click Next or
    Finish if you choose all drivers on your computer.
    8. Restart the computer.


    When you create custom settings you want to make sure that deadlock
    detection is set to off, and then when you select settings from a full list
    any Avast entries should be unchecked. That means the Avast software
    drivers won't be inspected.

    Again this has nothing to do with Avast running effectively on your Vista
    box/boot.

    Good luck,

    CH
     
    Chad Harris, Jul 3, 2006
    #5
  6. Marshall

    Marshall Guest

    Chad,

    Firstly, thankyou for the detailed and helpful replies so far, it is most
    appreciated!

    I'll try to break down what I have done so that I can help you understand
    what I am getting at - all apologies if I wasn't too clear in past posts!

    Hardware drivers are standard vista defaults, apart from my soundcard which
    is a C-Media onboard sound card (on the motherboard), and my video card (ATI
    Radeon X600, using the drivers that ATI provided for Vista Beta 2). When I
    reviewed my system performance it stated that 'drivers may be slowing your pc
    down when starting' and these drivers were identified by windows as being my
    C-Media sound card drivers. I have searched around and cannot find a newer
    version of the sound card drivers.

    As for the wwindows repair environment, I followed your advice and tried
    only the option that said 'startup repair'. It failed to find anything that
    it could fix. I cannot see this 'Fabricant' that you mention either?

    Now as for the system restore, my understanding is that similar to XP, it
    will restore my PC to an earlier point in time, is this correct? And as for
    me saying I don't want to use it, I think thats just me being frustrated and
    lazy - You're right, I need to try it again if it fixes the problem! I tried
    it earlier when I had a problem with a program that I installed and it did
    help, but alas it did not fix my blue screen problem.

    Sorry I didn't clarify, I CAN boot to windows, and I am using it, but
    randomly I get a blue screen when using other applications and my PC then
    restarts.

    Now, with this deadlock detection, when I run verifier and tell it to
    display current settings, every option is set to 'no' (as in not enabled), so
    when I am checking, deadlock detection is not on...

    Now when you say to tell it what drivers that I want it to verify, what
    would you suggest that I tell it to do? At the minute when I have hit display
    settings EVERY option is turned off (they all say 'no')... (once again
    apologies as I think I'm missing the point here?)

    Thankyou for your time!
    -Marshall
     
    Marshall, Jul 3, 2006
    #6
  7. Marshall

    Chad Harris Guest

    Marshall--

    1) If those sound card drivers work, I would be skeptical they are slowing
    down anything. MSFT is going to make a big marketing deal out of the rating
    system-- the so-called system assessment tool which is possibly as nebulous
    as it is meaningless. At some MSFT conferences long time employees who know
    Vista well are not supporting this tool as very meaningful.

    http://www.microsoft.com/technet/scriptcenter/topics/vista/winsat.mspx

    2) If you haven't added a driver recently and have been running for a while
    with the drivers you have, I wouldn't be inclined to blame those for these
    blue screens. It sounds like your driver setup is fine.

    3) I meant to ask you to go to type eventvwr.msc in the run box and click on
    system and use the down arrow and see if any error stands out at the time of
    your blue screens. Then do the same for application.

    4) If startup repair didn't work, I strongly urge you to try Complete PC
    Restore, and finally system restore. System restore in Vista works on a
    similar premise to SR in XP, but it has been made more powerful and is
    constructed borrowing from the server systems using Volume Shadow services.
    It also could be run from Win RE outside Windows if you couldn't boot.
    System restore will go to an eariler time and the idea is to go to a time
    before the trouble happened. You don't lose anything except potentially
    hotfixes or security updates since the time of the restore point and there
    aren't many of those in Vista so they would be easily updated and possibly
    shortcuts you made since the restore point. I see no downside whatsoever to
    using it, but try Complete PC Restore first. When you do try system
    restore, try every restore point you have, prior to your problem. using the
    more desirable one timewise first. You can undo a restore if you don't
    like it, but I can't imagine any downside for you and it only takes a few
    minutes--it's not a lot of complicated work--just a couple clicks.

    SR may not always work, but it is sure worth trying in this situation.
    Restore points can be corrupted in XP by involuntary shutdowns. In Vista I'm
    nor sure if that happens with Volume shadow service based restore points,
    but if you have a dual boot, and go to XP, you will lose Vista restore
    points.

    5) As to Driver Verifier, we want deadlock detection off in this situation
    ***and the only drivers I want you to uncheck using step #4 in the series I
    gave you and on is any driver that is listed with Avast Antivirus.*** We
    are just stopping their inspection not their activity.

    This has it's basis in several MSKBs and discussions I have seen on Verifier
    and antivirus driver detection causing this type of behavior with random
    blue screens.

    Let me know if Event Viewer yields any information as to errors. Give both
    Complete PC Restore and all system restore points if Complete PC restore
    doesn't work a shot.

    CH
     
    Chad Harris, Jul 3, 2006
    #7
  8. Marshall

    Marshall Guest

    Chad,

    Thanks again for the suggestions - next in line is the PC restoration
    options (with complete PC restore being considered also). I don't want to
    jinx things, but I haven't had a blue screen in 24 hours..... That is NOT a
    complaint haha!

    Interestingly enough, I took your advice and tried driver verifier. I
    enabled all checks except for deadlock detection, and told it to check all
    drivers except avast! and my PC would not boot into windows. I kept getting a
    blue screen, then reboot. I then chose to enter with the last known working
    settings and so far so good...?

    I know this proves nothing, and no one solution has contributed to this that
    I can see? But I am sort of expecting a blue screen any moment... (it will
    come, I'm sure)...

    As for the event log, the error events that are most prevalent are from
    source 'microsoft-windows-eventlog'. Following are some samples of what I can
    find in the 'details' tab.

    ------------------------------------------------
    System

    - Provider

    [ Name] Microsoft-Windows-Eventlog
    [ Guid] {fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}

    EventID 103

    Version 0

    Level 2

    Task 0

    Opcode 0

    Keywords 0x8000000000000000

    - TimeCreated

    [ SystemTime] 2006-07-02T14:42:33.888Z

    EventRecordID 37943

    Correlation

    - Execution

    [ ProcessID] 1020
    [ ThreadID] 1188

    Channel System

    Computer Scotty-PC

    Security


    - UserData

    - EventsDropped

    Reason 34


    -------------------------------------------------------------
    - System

    - Provider

    [ Name] Microsoft-Windows-Eventlog
    [ Guid] {fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}

    EventID 103

    Version 0

    Level 2

    Task 0

    Opcode 0

    Keywords 0x8000000000000000

    - TimeCreated

    [ SystemTime] 2006-07-02T15:11:41.794Z

    EventRecordID 38630

    Correlation

    - Execution

    [ ProcessID] 1012
    [ ThreadID] 1204

    Channel System

    Computer Scotty-PC

    Security


    - UserData

    - EventsDropped

    Reason 34


    -----------------------------
    - System

    - Provider

    [ Name] Microsoft-Windows-Eventlog
    [ Guid] {fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}

    EventID 103

    Version 0

    Level 2

    Task 0

    Opcode 0

    Keywords 0x8000000000000000

    - TimeCreated

    [ SystemTime] 2006-07-03T07:36:49.915Z

    EventRecordID 56291

    Correlation

    - Execution

    [ ProcessID] 988
    [ ThreadID] 1132

    Channel System

    Computer Scotty-PC

    Security


    - UserData

    - EventsDropped

    Reason 34


    -----------------------------------------------------------------------------------------------

    Ok, now I will admit that this means nothing to me! All I am noticing really
    is that out of the 17 listed events, all seem to list 'eventsdropped, reason
    - 34'...
    Perhaps this means something to you?

    Once again, thanks and fingers crossed things go smoothly from here on in,
    but I am definitely interested to hear your suggestions about what to do with
    this?

    Regards,
    -Marshall
     
    Marshall, Jul 4, 2006
    #8
  9. Marshall

    Marshall Guest

    Chad,

    Thanks again for the suggestions - next in line is the PC restoration
    options (with complete PC restore being considered also). I don't want to
    jinx things, but I haven't had a blue screen in 24 hours..... That is NOT a
    complaint haha!

    Interestingly enough, I took your advice and tried driver verifier. I
    enabled all checks except for deadlock detection, and told it to check all
    drivers except avast! and my PC would not boot into windows. I kept getting a
    blue screen, then reboot. I then chose to enter with the last known working
    settings and so far so good...?

    I know this proves nothing, and no one solution has contributed to this that
    I can see? But I am sort of expecting a blue screen any moment... (it will
    come, I'm sure)...

    As for the event log, the error events that are most prevalent are from
    source 'microsoft-windows-eventlog'. Following are some samples of what I can
    find in the 'details' tab.

    ------------------------------------------------
    System

    - Provider

    [ Name] Microsoft-Windows-Eventlog
    [ Guid] {fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}

    EventID 103

    Version 0

    Level 2

    Task 0

    Opcode 0

    Keywords 0x8000000000000000

    - TimeCreated

    [ SystemTime] 2006-07-02T14:42:33.888Z

    EventRecordID 37943

    Correlation

    - Execution

    [ ProcessID] 1020
    [ ThreadID] 1188

    Channel System

    Computer Scotty-PC

    Security


    - UserData

    - EventsDropped

    Reason 34


    -------------------------------------------------------------
    - System

    - Provider

    [ Name] Microsoft-Windows-Eventlog
    [ Guid] {fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}

    EventID 103

    Version 0

    Level 2

    Task 0

    Opcode 0

    Keywords 0x8000000000000000

    - TimeCreated

    [ SystemTime] 2006-07-02T15:11:41.794Z

    EventRecordID 38630

    Correlation

    - Execution

    [ ProcessID] 1012
    [ ThreadID] 1204

    Channel System

    Computer Scotty-PC

    Security


    - UserData

    - EventsDropped

    Reason 34


    -----------------------------
    - System

    - Provider

    [ Name] Microsoft-Windows-Eventlog
    [ Guid] {fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}

    EventID 103

    Version 0

    Level 2

    Task 0

    Opcode 0

    Keywords 0x8000000000000000

    - TimeCreated

    [ SystemTime] 2006-07-03T07:36:49.915Z

    EventRecordID 56291

    Correlation

    - Execution

    [ ProcessID] 988
    [ ThreadID] 1132

    Channel System

    Computer Scotty-PC

    Security


    - UserData

    - EventsDropped

    Reason 34


    -----------------------------------------------------------------------------------------------

    Ok, now I will admit that this means nothing to me! All I am noticing really
    is that out of the 17 listed events, all seem to list 'eventsdropped, reason
    - 34'...
    Perhaps this means something to you?

    Once again, thanks and fingers crossed things go smoothly from here on in,
    but I am definitely interested to hear your suggestions about what to do with
    this?

    Regards,
    -Marshall
     
    Marshall, Jul 4, 2006
    #9
  10. Marshall

    Marshall Guest

    Just on another note Chad, a window called 'Problem reports and solutions'
    appeared when I turned the PC on. It listed two problems... This one was
    'new'/...

    -----------------------------
    Error caused by a device driver


    --------------------------------------------------------------------------------

    Thank you for sending an error report to Microsoft.

    Error report summary

    Error type: Windows stop error (A message appears on a blue screen with
    error code information)
    Solution available? No (see Next steps)
    What does this error mean? Windows has encountered an error from which it
    cannot recover and needs to restart
    Cause: Unknown device driver
    Computer symptoms: A message appears on a blue screen with error code
    information (for example: e.g. 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED)
    Additional steps: Important: Please continue to send error reports so
    analysts at Microsoft can study and try to correct the problem as quickly as
    possible


    Information about this error

    You received this message because a device driver installed on your computer
    caused the Windows operating system to stop unexpectedly. This type of error
    is referred to as a "stop error." A stop error requires you to restart your
    computer.



    Next steps

    We have analyzed your error report and at this time are unable to determine
    the exact cause of the error. However, Microsoft will continue to analyze
    this error report to try to determine the specific cause of the error. If we
    are able to find the cause and correct it, and you encounter the same
    problem, you will receive an updated response that includes instructions for
    resolving the problem.

    Article ID : 10
    Last Review : December 21, 2005
    Revision : 2.0



    Related Links
    Additional Technical Information
    Troubleshoot driver problems


    Rate this response
    Provide Feedback


    ----------------------------------------------------------

    The other was just a 'Fixed in future windows vista release' and no details.
    Not sure if this helps at all!

    -Marshall


     
    Marshall, Jul 5, 2006
    #10
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.