Random BSOD's

Delutube allows you to view deleted YouTube videos

Published on March 16, 2007

A site called Delutube has taken advantage of the fact that "deleted" videos on YouTube apparently remain available for viewing up to an hour or so after they can no longer be accessed on YouTube.com itself Read more

Windows Crashes During Olympic Ceremony

Published on August 12, 2008

Microsoft Windows never lets us down when it comes to BSOD amusement and at the 2008 Summer Olympic Opening Ceremonies it strikes again With 70 million viewers watching, a record for non-U.S. Olympic Summer Games viewership, how many people do you think Read more

Ultra-X introduces harddrive cleaning utility

Published on June 29, 2004

Ultra-X, known for its professional hardware and software diagnostic tools, has introduced a simple, OS-independent tool to safely erase data from IDE harddrives. Read more

The hard drive turns 50

Published on September 13, 2006

The hard drive on Wednesday turned 50. Read more

Latest Reviews & Articles

Power Supply Roundup: Part II

Published on November 07, 2008

In Part I of our power supply roundup, we went through five mainstream PSUs rated at up to 700 W. Round two sees us tackle another seven mid-range units in an effort to determine which power supply deserves your attention. Read more

Roundup: The Best Overclocking Software

Published on November 06, 2008

Interested in overclocking but not quite sure where to start? We round up some of our favorite software utilities for tweaking processors, memory, graphics, and chipsets. Read more

Tom's Holiday Buyer's Guide 2008, Part 1

Published on November 05, 2008

Welcome to the first installment in our six-part Tom's Holiday Buyer's Guide. In Part 1, two beautiful models help showcase some of our favorite no-hassle hardware gifts for 2008. Read more

Round Up: Five Powerful, Light Ultraportables

Published on November 05, 2008

Executives, road warriors, and gadget geeks all lust after ultraportable notebooks. Five of these amazing machines battle it out in this roundup. Read more

All the Reviews & Articles

Random BSOD's

Word : Username : Filter :
Bottom
Author	Thread : Random BSOD's

Anonymous

More Information

04-19-2004 at 10:46:33 PM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Up until a few weeks ago, I had a happy computer..
Then, one day it crashed, and after resetting a few bios
settings (bus speed) it had lost, XP started again without
error.
However, since then It has been BSOD regulary - I've done
a repair install, uninstalled / reinstalled my video &
audio drivers, disabled caching of the ram in the bios,
yet the problem remains.... I get:
"The computer has rebooted from a bugcheck. The bugcheck
was: 0x000000d1 (0x00000000, 0x000000ff, 0x00000000,
0x0012f44a). A dump was saved in: C:\WINDOWS\MEMORY.DMP"
So, from what I can find on Google / MS, it's a bad
driver..
I convert the 12f44a to decimal to get the memory
address, but when I do a pstat to find the offending
driver for the load address, I come up blank...

Any ideas, would be GREATLY appreciated.

Thanks!

Related Product

Anonymous

More Information

04-20-2004 at 02:52:27 PM

Hide

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Hello

Try replacing your pc Power Supply maybe your pc is
running a bit warm.

Alvin

Healey wrote:

> Up until a few weeks ago, I had a happy computer..
> Then, one day it crashed, and after resetting a few bios
> settings (bus speed) it had lost, XP started again without
> error.
> However, since then It has been BSOD regulary - I've done
> a repair install, uninstalled / reinstalled my video &
> audio drivers, disabled caching of the ram in the bios,
> yet the problem remains.... I get:
> "The computer has rebooted from a bugcheck. The bugcheck
> was: 0x000000d1 (0x00000000, 0x000000ff, 0x00000000,
> 0x0012f44a). A dump was saved in: C:\WINDOWS\MEMORY.DMP"
> So, from what I can find on Google / MS, it's a bad
> driver..
> I convert the 12f44a to decimal to get the memory
> address, but when I do a pstat to find the offending
> driver for the load address, I come up blank...
>
> Any ideas, would be GREATLY appreciated.
>
> Thanks!

Anonymous

More Information

04-20-2004 at 02:52:28 PM

Hide

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Thanks for this,

But I'd still like to know how to determine which driver
is trying to incorrectly access memory.
Does someone know?

Thanks!

>-----Original Message-----
>Hello
>
>Try replacing your pc Power Supply maybe your pc is
>running a bit warm.
>
>Alvin
>
>
>Healey wrote:
>
>> Up until a few weeks ago, I had a happy computer..
>> Then, one day it crashed, and after resetting a few bios
>> settings (bus speed) it had lost, XP started again
without
>> error.
>> However, since then It has been BSOD regulary - I've
done
>> a repair install, uninstalled / reinstalled my video &
>> audio drivers, disabled caching of the ram in the bios,
>> yet the problem remains.... I get:
>> "The computer has rebooted from a bugcheck. The
bugcheck
>> was: 0x000000d1 (0x00000000, 0x000000ff, 0x00000000,
>> 0x0012f44a). A dump was saved in: C:\WINDOWS\MEMORY.DMP"
>> So, from what I can find on Google / MS, it's a bad
>> driver..
>> I convert the 12f44a to decimal to get the memory
>> address, but when I do a pstat to find the offending
>> driver for the load address, I come up blank...
>>
>> Any ideas, would be GREATLY appreciated.
>>
>> Thanks!
>
>.
>

Anonymous

More Information

04-21-2004 at 04:42:45 PM

Hide

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

You can set up a kernel debugger and be able to determine what the offending
module is. If not you can try to load the .dmp files into a user debugger
like WinDBG and try to determine what made the call to the bad address.
There is a lot to learn but this site should get you going as far as tools
and documentation.

http://www.microsoft.com/whdc/ddk/debugging/

Joshua Smith
DirectInput and OpenGL Test Labs
Microsoft
-----

Get Secure! www.microsoft.com/security

This posting is provided "AS IS" with no warranties, and confers no rights

"Healey" <anonymous@discussions.microsoft.com> wrote in message
news:19ba01c426e8$62c0d7d0$a501280a@phx.gbl...
> Thanks for this,
>
> But I'd still like to know how to determine which driver
> is trying to incorrectly access memory.
> Does someone know?
>
> Thanks!
>
>>-----Original Message-----
>>Hello
>>
>>Try replacing your pc Power Supply maybe your pc is
>>running a bit warm.
>>
>>Alvin
>>
>>
>>Healey wrote:
>>
>>> Up until a few weeks ago, I had a happy computer..
>>> Then, one day it crashed, and after resetting a few bios
>>> settings (bus speed) it had lost, XP started again
> without
>>> error.
>>> However, since then It has been BSOD regulary - I've
> done
>>> a repair install, uninstalled / reinstalled my video &
>>> audio drivers, disabled caching of the ram in the bios,
>>> yet the problem remains.... I get:
>>> "The computer has rebooted from a bugcheck. The
> bugcheck
>>> was: 0x000000d1 (0x00000000, 0x000000ff, 0x00000000,
>>> 0x0012f44a). A dump was saved in: C:\WINDOWS\MEMORY.DMP"
>>> So, from what I can find on Google / MS, it's a bad
>>> driver..
>>> I convert the 12f44a to decimal to get the memory
>>> address, but when I do a pstat to find the offending
>>> driver for the load address, I come up blank...
>>>
>>> Any ideas, would be GREATLY appreciated.
>>>
>>> Thanks!
>>
>>.
>>

Anonymous

More Information

04-22-2004 at 02:11:57 AM

Hide

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Healey wrote:

> Up until a few weeks ago, I had a happy computer..
> Then, one day it crashed, and after resetting a few bios
> settings (bus speed) it had lost, XP started again without
> error.
> However, since then It has been BSOD regulary - I've done
> a repair install, uninstalled / reinstalled my video &
> audio drivers, disabled caching of the ram in the bios,
> yet the problem remains.... I get:
> "The computer has rebooted from a bugcheck. The bugcheck
> was: 0x000000d1 (0x00000000, 0x000000ff, 0x00000000,
> 0x0012f44a). A dump was saved in: C:\WINDOWS\MEMORY.DMP"
> So, from what I can find on Google / MS, it's a bad
> driver..
> I convert the 12f44a to decimal to get the memory
> address, but when I do a pstat to find the offending
> driver for the load address, I come up blank...
>
> Any ideas, would be GREATLY appreciated.
>
> Thanks!

May be it is a good idea to run a comprehensive memory test first. For a
good tool, try http://www.memtest86.com/

E.P.

Anonymous

More Information

04-22-2004 at 10:19:38 AM

Hide

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

If the failure is due to a hardware problem like a power supply or heat
problem, you won't get anything interesting from the crash dump files.
It'll just be random failures.

So if you load all the dump files (one by one) in %windir%\minidump into
windbg and the stack for each crash looks different, the probability of a
hardware problem goes way up. On the other hand, if all the dump files show
the same stack trace for the failure, a software problem is more likely.

But if your not familiar with debugging, this will be a lot of work. The
first and easiest thing I would do is clean out the dust from the machine,
check the fans, and possibly add an external fan. The next step is to run
hardware diagnostics (memory, disk, etc), and if the problem is not resolved
yet, then I'd spend time looking at the dump files for a pattern. Replacing
hardware in the box should be a last resort...

-Andre
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2004 Microsoft Corporation. All rights
reserved.

"Joshua Smith [MSFT]" <joshsm@online.microsoft.com> wrote in message
news:uovXNg8JEHA.3380@TK2MSFTNGP09.phx.gbl...
> You can set up a kernel debugger and be able to determine what the
offending
> module is. If not you can try to load the .dmp files into a user debugger
> like WinDBG and try to determine what made the call to the bad address.
> There is a lot to learn but this site should get you going as far as tools
> and documentation.
>
> http://www.microsoft.com/whdc/ddk/debugging/
>
> Joshua Smith
> DirectInput and OpenGL Test Labs
> Microsoft
> -----
>
> Get Secure! www.microsoft.com/security
>
> This posting is provided "AS IS" with no warranties, and confers no rights
>
>
>
> "Healey" <anonymous@discussions.microsoft.com> wrote in message
> news:19ba01c426e8$62c0d7d0$a501280a@phx.gbl...
> > Thanks for this,
> >
> > But I'd still like to know how to determine which driver
> > is trying to incorrectly access memory.
> > Does someone know?
> >
> > Thanks!
> >
> >>-----Original Message-----
> >>Hello
> >>
> >>Try replacing your pc Power Supply maybe your pc is
> >>running a bit warm.
> >>
> >>Alvin
> >>
> >>
> >>Healey wrote:
> >>
> >>> Up until a few weeks ago, I had a happy computer..
> >>> Then, one day it crashed, and after resetting a few bios
> >>> settings (bus speed) it had lost, XP started again
> > without
> >>> error.
> >>> However, since then It has been BSOD regulary - I've
> > done
> >>> a repair install, uninstalled / reinstalled my video &
> >>> audio drivers, disabled caching of the ram in the bios,
> >>> yet the problem remains.... I get:
> >>> "The computer has rebooted from a bugcheck. The
> > bugcheck
> >>> was: 0x000000d1 (0x00000000, 0x000000ff, 0x00000000,
> >>> 0x0012f44a). A dump was saved in: C:\WINDOWS\MEMORY.DMP"
> >>> So, from what I can find on Google / MS, it's a bad
> >>> driver..
> >>> I convert the 12f44a to decimal to get the memory
> >>> address, but when I do a pstat to find the offending
> >>> driver for the load address, I come up blank...
> >>>
> >>> Any ideas, would be GREATLY appreciated.
> >>>
> >>> Thanks!
> >>
> >>.
> >>
>
>

Tom's Hardware Forums » Windows XP » Windows XP General Discussion » Random BSOD's

Go to:

Page generated in 0.415 seconds

Google Ads