WHYYYYYYYYYYYYYYYY!! (BSOD)

[Guest]

hello,
Im new, after getting a brand new custom built PC, 2 months in and it crashes!
Basically, Ive picked up some technical 'lingo' and understand that its a
Blue screen of death. I was playing Medieval 2 when... BSOD. The errors vary,
for the first day, I could log on, do something for 2 mins and then windows
explorer goes and the blue sceen comes up with 'MEMORY_MANAGEMENT' and
0x0000001A. Another weird crash was 'unknown hard error - ntdll.dll' (also
BSOD). There were others that I dont remember but another one I do was
'IRQL_NOT_EQUAL_OR_LESS'. Can someone explain? I cant believe that after just
2 months....

 

[Guest]

Oh, and I forgot to say that everytime I restart the BSOD appears. Cant even
log on, having to use another PC for this. Oh, and also I trying switching
the RAM between the slots and for some 15 minutes it was fine, but then...
it starts to lagg really bad and the multi meter shows that both my cores are
at 100%! I thought core 2 duo was supposed to be fast! What is going on??

 

[Alias]

Oh, and I forgot to say that everytime I restart the BSOD appears. Cant even
log on, having to use another PC for this. Oh, and also I trying switching
the RAM between the slots and for some 15 minutes it was fine, but then...
it starts to lagg really bad and the multi meter shows that both my cores are
at 100%! I thought core 2 duo was supposed to be fast! What is going on??

When you get the BSOD, you will see a long number. Copy it and then
Google it and it will tell you what the problem is.

Alias

 

[Arie]

Random crashes are normally a sign of a problem with the hardware.

Start by testing your memory. Run http://www.memtest86.com/ or
http://oca.microsoft.com/en/windiag.asp .

Arie Slob,
MVP, Windows Shell/User
https://mvp.support.microsoft.com/profile/Arie.Slob

Microsoft Certified Professional
http://www.microsoft.com/mcp

http://www.helpwithwindows.com
http://www.windowsbbs.com
http://www.windowsnewsletter.com

 

[R. C. White]

Hi, Red Star.

The BSOD is very useful for tracking down software problems, like bad code
in drivers and applications. It is sometimes useful in spotlighting some
kinds of hardware problems, like defective memory. But when the problem is
in hardware (bad or loose cables; failing hard drive; weak power supply;
heat buildup - and many others), the BSOD is not very useful, except that
when the BSOD codes are inconsistent - like the ones you are seeing - then
we start to suspect the hardware.

Can you have your PC's builder take a good look at it? Preferably in its
normal working location, because the problem may be an environmental think,
like electrical interference from some other equipment nearby. Heat buildup
can be from lack of airflow, which would not be obvious if you carried the
machine to the shop. Or, if you're not worried about your warranty, you can
open the case and have a look for yourself. Unplug and re-plug all the
connections that you can see (after unplugging the computer itself and
grounding yourself, of course). Surprisingly enough, many hardware problems
are solved just by unplugging a loose cable and plugging it in again. Kind
of like solving many kinds of software problems by simply rebooting.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP
(Running Windows Live Mail beta in Vista Ultimate x64)

 

[Peter Foldes]

Trouble shooting this many different BSOD error as you posted is very difficult at best. From what you have posted and those errors will warrant a complete reformat and re-install. Just alone the ntdll.dll error warrants this above

 

[Stephan Rose]

hello,
Im new, after getting a brand new custom built PC, 2 months in and it crashes!
Basically, Ive picked up some technical 'lingo' and understand that its a
Blue screen of death. I was playing Medieval 2 when... BSOD. The errors vary,
for the first day, I could log on, do something for 2 mins and then windows
explorer goes and the blue sceen comes up with 'MEMORY_MANAGEMENT' and
0x0000001A. Another weird crash was 'unknown hard error - ntdll.dll' (also
BSOD). There were others that I dont remember but another one I do was
'IRQL_NOT_EQUAL_OR_LESS'. Can someone explain? I cant believe that after just
2 months....

First thing that comes to my mind is bad memory.

Find a utility called "memtest86" and run that on your machine. You'll
want to burn it to a bootable CD.

http://www.memtest86.com/download.html

Here, on that site you can find bootable ISO Images to burn to a CD to
boot your computer with.

Use that and have it test your memory. Don't be afraid to let it run over
night for several hours.

If it comes back with any errors, get new ram.

If it doesn't come back with any errors....then that opens a much larger
can of worms with possibilities what might be wrong.

--
Stephan
2003 Yamaha R6

å›ã®ã“ã¨æ€ã„出ã™æ—¥ãªã‚“ã¦ãªã„ã®ã¯
å›ã®ã“ã¨å¿˜ã‚ŒãŸã¨ããŒãªã„ã‹ã‚‰

 

[Guest]

Thats a lot of sruff to try, thanx, but the one that worries me most is
buying new ram! I just upgraded, can it be broken already?!!!

 

[Charlie Tame]

Thats a lot of sruff to try, thanx, but the one that worries me most is
buying new ram! I just upgraded, can it be broken already?!!!

Haven't read the original question but...

RAM is easily damaged by static...
RAM is sometimes faulty when you get it...
RAM has very critical timing requirements, unless you but identical RAM
from the same manufacturer (Of the RAM not the computer) you have the
risk of compatibility problems. Ideally buy 2 new sticks (Or whatever)
from the same place at the same time. The sticks may run fine on their
own but not together.

 

[Peter Foldes]

Nothing to do with your RAM. When you get that many errors as that including BSOD's and especially
***unknown hard error - ntdll.dll** then I would say do not even try to look for a fix. Backup your important Data and reformat.

 

[Charlie Tame]

Nothing to do with your RAM. When you get that many errors as that including BSOD's and especially
***unknown hard error - ntdll.dll** then I would say do not even try to look for a fix. Backup your important Data and reformat.

When something has physically been changed (Poster mentioned RAM) and
problems that weren't noticed before appear I'd say that's a good place
to start looking. If it IS the RAM then backup / restore won't fix
anything, although it may appear to for a while. If you've ever had a
stick of RAM go faulty these are typical symptoms. Note wishing to argue
but I don't think the possibility should be ignored since RAM can
potentially damage anything.

 

[Guest]

Thats not true, I went to msconfig limit to 1536mb in boot tab and all my
Bsods disaappear.