Prev: Remove watermark from desktop
Next: gdi32.dll program hang (the ghost in the machine)
From: Charlie Russel - MVP on 28 Dec 2006 12:07
GIYF. :)

--
Charlie.
http://msmvps.com/xperts64


"GoingCrazy!" <GoingCrazy(a)discussions.microsoft.com> wrote in message
news:6D2AC309-B665-45D2-86BA-3ACD0D5B2AAF(a)microsoft.com...
> Now that is useful information! If I had known about googling error codes
> then I might have fixed these issues a long while back? I'll do this and
> get
> back... THANKS!
>
> "Charlie Russel - MVP" wrote:
>
>> What we need is the base STOP error code. It's a hex number, and for our
>> purposes here (as opposed to the developer trying to debug his or her
>> code),
>> we only need that one number. So, for example, you might get something
>> that
>> looks like:
>>
>> STOP: 0x0000007E (0xC0000005, 0x804E518E, 0xFC938104, 0xFC937E04)
>> SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
>>
>> All we care about is the 0x0000007E part. You take that code, plug it in
>> to
>> Google, and you're well on your way to knowing the cause. Not always,
>> obviously, because more than one thing can cause a given result.
>>
>> --
>> Charlie.
>> http://msmvps.com/xperts64
>>
>>
>> "GoingCrazy!" <GoingCrazy(a)discussions.microsoft.com> wrote in message
>> news:9E132846-5EB4-4131-9D93-A3EF9826B4A0(a)microsoft.com...
>> > OK fair enough, but I have no idea how to give you these "Crash codes"
>> > ? I
>> > get the blue screen of death with about a page of numbers and letters.
>> > I
>> > can't print screen them or copy them or frankly do anything but push
>> > the
>> > ON/OFF switch and restart the computer. If there is a place in the
>> > system
>> > where these codes are stored and I can cut and paste them, then please
>> > advise
>> > me on how to do this? Like I said, I am not a systems guy and all of
>> > this
>> > beating my head against the wall is new to me. From what I gather
>> > others
>> > are using the same hardware configurations as I am with none of these
>> > issues,
>> > and the OEMs are turning out updates to drivers on a weekly basis, so
>> > I'm
>> > not
>> > sure that it's a driver issue at this point? Maybe I'm missing
>> > something
>> > here? Is there a turbo button I forgot to push (smile)?
>> >
>> > "Charlie Russel - MVP" wrote:
>> >
>> >> As we've all said from the beginning. Please provide the crash codes.
>> >> We
>> >> can't help you if you won't tell us what the problem is. "crash" could
>> >> be
>> >> anything. It almost certainly is a hardware problem, but WHAT hardware
>> >> only
>> >> the stop error codes will tell us.
>> >>
>> >> Complaining about MS when it's a hardware or driver problem is not
>> >> going
>> >> to
>> >> help anyone, especially you. Providing the details of the problem
>> >> might
>> >> allow us to point you at a solution. (And just to be completely
>> >> clear -
>> >> MS
>> >> is NOT responsible for hardware drivers. The OEMs are.)
>> >>
>> >> --
>> >> Charlie.
>> >> http://msmvps.com/blogs/xperts64
>> >>
>> >> "GoingCrazy!" <GoingCrazy(a)discussions.microsoft.com> wrote in message
>> >> news:B19C23EA-4CB0-4A6E-A467-817FA89DF281(a)microsoft.com...
>> >> > You know who knows, and why should it matter? If MS is updating
>> >> > your
>> >> > system
>> >> > then why would they force drivers into it that will hose you up? I
>> >> > have
>> >> > since
>> >> > reloaded the most current driver for my Mother board and video card
>> >> > and
>> >> > the
>> >> > same system crashes keep happening. I keep reading the praise of
>> >> > MS,
>> >> > but
>> >> > in
>> >> > the same breath they say things like don't do a MS online update and
>> >> > the
>> >> > such??? I'm not a system wise man, but if it looks like "" and
>> >> > smells
>> >> > like
>> >> > ""
>> >> > then I'm not going to drink the kool aid!
>> >> >
>> >> > "Dshai" wrote:
>> >> >
>> >> >> I guess my first question is going to be whether or not the upgrade
>> >> >> from
>> >> >> MS
>> >> >> included any device drivers, this can and has caused past problems
>> >> >> for
>> >> >> myself and several others that I know.
>> >> >>
>> >> >> Dshai
>> >> >>
>> >> >> "DP" <nospamxx(a)xyzddd.com> wrote in message
>> >> >> news:ORrFJqWKHHA.1064(a)TK2MSFTNGP04.phx.gbl...
>> >> >> >
>> >> >> > You've gotten a number of good responses here. The only thing I
>> >> >> > would
>> >> >> > add
>> >> >> > to those would be a request for more system specs.
>> >> >> > You say you have AMD 4800 X2 64 bit processor. What else? How
>> >> >> > much
>> >> >> > ram;
>> >> >> > how is your video being done; hard drive size, etc.?
>> >> >> > Though your processor should not be an issue here, other factors
>> >> >> > may
>> >> >> > be
>> >> >> > part of the problem if they're not muscular enough to support the
>> >> >> > 64-bit
>> >> >> > dual-core processor and the 64-bit OS.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > "GoingCrazy!" <GoingCrazy!@discussions.microsoft.com> wrote in
>> >> >> > message
>> >> >> > news:886290CA-3988-442F-A880-E3023CF11E12(a)microsoft.com...
>> >> >> >>I purchased XP Pro x64 and installed it on my AMD 4800 system a
>> >> >> >>couple
>> >> >> >>of
>> >> >> >> months ago, however the system has become so unstable that it
>> >> >> >> just
>> >> >> >> crashes
>> >> >> >> without indication or reason... just sitting idle it will crash
>> >> >> >> and
>> >> >> >> reboot
>> >> >> >> it's self. I have downloaded and installed all new AMD drivers
>> >> >> >> to
>> >> >> >> no
>> >> >> >> avail!
>> >> >> >> Has anyone else experiences this and if so how do I fix this OS?
>> >> >> >> P.S>
>> >> >> >> computers works flawless on a LINUX OS!
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>>

From: GoingCrazy! on 29 Dec 2006 13:42
Looks like I need to close this thread out... I reloaded my OS and chose an
update when it finished my system seemed stable and was not crashing every
few minutes... however when I tried to copy a DVD or watch streaming video I
received a BSOD with error code 0xoooooooA.. I started another thread to get
answers to this issue. I don't want to keep raging about MS, I just want to
get this POS OS to work so I don't feel like I have completely wasted $100
and hours of my time! Thanks to everyone that at least tried to help!

"Charlie Russel - MVP" wrote:

> GIYF. :)
>
> --
> Charlie.
> http://msmvps.com/xperts64
>
>
> "GoingCrazy!" <GoingCrazy(a)discussions.microsoft.com> wrote in message
> news:6D2AC309-B665-45D2-86BA-3ACD0D5B2AAF(a)microsoft.com...
> > Now that is useful information! If I had known about googling error codes
> > then I might have fixed these issues a long while back? I'll do this and
> > get
> > back... THANKS!
> >
> > "Charlie Russel - MVP" wrote:
> >
> >> What we need is the base STOP error code. It's a hex number, and for our
> >> purposes here (as opposed to the developer trying to debug his or her
> >> code),
> >> we only need that one number. So, for example, you might get something
> >> that
> >> looks like:
> >>
> >> STOP: 0x0000007E (0xC0000005, 0x804E518E, 0xFC938104, 0xFC937E04)
> >> SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
> >>
> >> All we care about is the 0x0000007E part. You take that code, plug it in
> >> to
> >> Google, and you're well on your way to knowing the cause. Not always,
> >> obviously, because more than one thing can cause a given result.
> >>
> >> --
> >> Charlie.
> >> http://msmvps.com/xperts64
> >>
> >>
> >> "GoingCrazy!" <GoingCrazy(a)discussions.microsoft.com> wrote in message
> >> news:9E132846-5EB4-4131-9D93-A3EF9826B4A0(a)microsoft.com...
> >> > OK fair enough, but I have no idea how to give you these "Crash codes"
> >> > ? I
> >> > get the blue screen of death with about a page of numbers and letters.
> >> > I
> >> > can't print screen them or copy them or frankly do anything but push
> >> > the
> >> > ON/OFF switch and restart the computer. If there is a place in the
> >> > system
> >> > where these codes are stored and I can cut and paste them, then please
> >> > advise
> >> > me on how to do this? Like I said, I am not a systems guy and all of
> >> > this
> >> > beating my head against the wall is new to me. From what I gather
> >> > others
> >> > are using the same hardware configurations as I am with none of these
> >> > issues,
> >> > and the OEMs are turning out updates to drivers on a weekly basis, so
> >> > I'm
> >> > not
> >> > sure that it's a driver issue at this point? Maybe I'm missing
> >> > something
> >> > here? Is there a turbo button I forgot to push (smile)?
> >> >
> >> > "Charlie Russel - MVP" wrote:
> >> >
> >> >> As we've all said from the beginning. Please provide the crash codes.
> >> >> We
> >> >> can't help you if you won't tell us what the problem is. "crash" could
> >> >> be
> >> >> anything. It almost certainly is a hardware problem, but WHAT hardware
> >> >> only
> >> >> the stop error codes will tell us.
> >> >>
> >> >> Complaining about MS when it's a hardware or driver problem is not
> >> >> going
> >> >> to
> >> >> help anyone, especially you. Providing the details of the problem
> >> >> might
> >> >> allow us to point you at a solution. (And just to be completely
> >> >> clear -
> >> >> MS
> >> >> is NOT responsible for hardware drivers. The OEMs are.)
> >> >>
> >> >> --
> >> >> Charlie.
> >> >> http://msmvps.com/blogs/xperts64
> >> >>
> >> >> "GoingCrazy!" <GoingCrazy(a)discussions.microsoft.com> wrote in message
> >> >> news:B19C23EA-4CB0-4A6E-A467-817FA89DF281(a)microsoft.com...
> >> >> > You know who knows, and why should it matter? If MS is updating
> >> >> > your
> >> >> > system
> >> >> > then why would they force drivers into it that will hose you up? I
> >> >> > have
> >> >> > since
> >> >> > reloaded the most current driver for my Mother board and video card
> >> >> > and
> >> >> > the
> >> >> > same system crashes keep happening. I keep reading the praise of
> >> >> > MS,
> >> >> > but
> >> >> > in
> >> >> > the same breath they say things like don't do a MS online update and
> >> >> > the
> >> >> > such??? I'm not a system wise man, but if it looks like "" and
> >> >> > smells
> >> >> > like
> >> >> > ""
> >> >> > then I'm not going to drink the kool aid!
> >> >> >
> >> >> > "Dshai" wrote:
> >> >> >
> >> >> >> I guess my first question is going to be whether or not the upgrade
> >> >> >> from
> >> >> >> MS
> >> >> >> included any device drivers, this can and has caused past problems
> >> >> >> for
> >> >> >> myself and several others that I know.
> >> >> >>
> >> >> >> Dshai
> >> >> >>
> >> >> >> "DP" <nospamxx(a)xyzddd.com> wrote in message
> >> >> >> news:ORrFJqWKHHA.1064(a)TK2MSFTNGP04.phx.gbl...
> >> >> >> >
> >> >> >> > You've gotten a number of good responses here. The only thing I
> >> >> >> > would
> >> >> >> > add
> >> >> >> > to those would be a request for more system specs.
> >> >> >> > You say you have AMD 4800 X2 64 bit processor. What else? How
> >> >> >> > much
> >> >> >> > ram;
> >> >> >> > how is your video being done; hard drive size, etc.?
> >> >> >> > Though your processor should not be an issue here, other factors
> >> >> >> > may
> >> >> >> > be
> >> >> >> > part of the problem if they're not muscular enough to support the
> >> >> >> > 64-bit
> >> >> >> > dual-core processor and the 64-bit OS.
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > "GoingCrazy!" <GoingCrazy!@discussions.microsoft.com> wrote in
> >> >> >> > message
> >> >> >> > news:886290CA-3988-442F-A880-E3023CF11E12(a)microsoft.com...
> >> >> >> >>I purchased XP Pro x64 and installed it on my AMD 4800 system a
> >> >> >> >>couple
> >> >> >> >>of
> >> >> >> >> months ago, however the system has become so unstable that it
> >> >> >> >> just
> >> >> >> >> crashes
> >> >> >> >> without indication or reason... just sitting idle it will crash
> >> >> >> >> and
> >> >> >> >> reboot
> >> >> >> >> it's self. I have downloaded and installed all new AMD drivers
> >> >> >> >> to
> >> >> >> >> no
> >> >> >> >> avail!
> >> >> >> >> Has anyone else experiences this and if so how do I fix this OS?
> >> >> >> >> P.S>
> >> >> >> >> computers works flawless on a LINUX OS!
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >>
>
First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: Remove watermark from desktop
Next: gdi32.dll program hang (the ghost in the machine)