Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

**stop Messages**

  • 21-10-2007 8:31pm
    #1
    30something
    Closed Accounts Posts: 1,535 ✭✭✭


    Hi, this is my first post in your forum and I hope this question is in the right place.

    I got a new Laptop recently (reasonably good) with Vista Home version. After teething probs it seemed to be working okay. I recently tried a general back-up for the first time which failed due to the fact I had not enough disk space (I'm not good at computers but I think the system reserved a chunk of my hard drive to store the back up files and didn't reserve enough).

    anyway, since then about 60% of my shutdowns give me a **Stop Message**. I can full text of it if necessary but generally speaking its a blue screen that says a problem has been detected and that I should check I have adequate disk space (of which I use 15%!!) or maybe some driver is bust.

    It also gives this message at the end:

    "***STOP:0*0000008E (0*C0000005,0045A5F04B,0*A256FD64,0*00000000)"

    I have no clue what this means. It then says it is rescuing data for crash dump but this seems to never end. Usually I just leave it 5 mins and turn it off manually. 95% time when I reboot everything is fine, sometimes it prompts me to go to "safe mode" but it is also fine when I skip to normal boot.

    Any ideas?

    Mods, please transfer this if wrong place.

    Thanks for any help.


Comments

  • #2
    Static M.e.
    Registered Users, Registered Users 2 Posts: 3,099 ✭✭✭Static M.e.


    Go to start, Run, then type "eventvwr" and look for Critical / Warning events in the last few days.

    Post results.


  • #3
    Hagar
    Closed Accounts Posts: 16,786 ✭✭✭✭Hagar


    Just as an aside taking a backup of your data onto the same hard disk is virtually worthless. If the hard drive fails you will lose your live data and your backup at the same time. You really need to be burning the data onto a cd/dvd or copying onto an external disk.


  • #4
    30something
    Closed Accounts Posts: 1,535 ✭✭✭30something


    Static M.e. wrote: »
    Go to start, Run, then type "eventvwr" and look for Critical / Warning events in the last few days.

    Post results.

    Thanks for that, here's what I think are the relevant ones ...

    "Event ID" "Source" "Log" ...... "Total"

    6 ACPI SYSTEM 386

    33 SidebySide Application 179


  • #5
    Static M.e.
    Registered Users, Registered Users 2 Posts: 3,099 ✭✭✭Static M.e.


    The first one

    "This error message may occur on a computer that uses a Peripheral Component Interconnect (PCI) bridge that supports message-signaled interrupts but does not support line-based interrupts."

    2nd

    "I have been seeing these a lot lately and so far they have all seemed to relate to missing or improperly referenced libraries that were used during development of various software. Most often is seems to be caused by a redistributable package not being installed on the computer with the error.
    If the error refers to "Dependent Assembly Microsoft.VC80..." then it is Microsoft Visual C v8.0 (a.k.a. MS Visual C++ 2005). These are currently available from the Microsoft site. On those pages, you will also find links to similar downloads like .NET versions, and the VB6 run-times. These can help correct various SideBySide errors.

    Sometimes the SideBySide errors are caused by a faulty manifest for the application you are trying to run. If the author incorrectly hard-coded custom paths to these libraries while developing, Windows will look for that specific path, and may produce the error instead for searching for the files in various default places. "


  • #6
    parliament
    Closed Accounts Posts: 132 ✭✭parliament


    You say that you arent very experienced with technical stuff and that the laptop is new...I would suggest you head back to where you bought it and let them take care of it. No need to time and hassle and possible (in the eyes of the retailer) voiding any warranty you have.

    The error code you supplied indicates that you could possible have faulty hardware so there would be nothing you could do anyway without getting the retailer involved.


  • Advertisement
Advertisement