Vast Amount of Blue Screens

Harblkips · Mar 1, 2009

I know theres probably a million threads about blue screens, but I think my problem is different. (Probably heard that before too.)

I bought my computer in November, and since then I've had a bunch of blue screens, most giving different codes. I ran Memtest86 and it found nothing (I ran it once for 6 hours then another for 9).

Heres some of my error codes, just recently:
0x000000be
0x000000d1
0x0000004e
0x0000001e
0x000000c5
0x0000003b

I don't know what most of them mean, I've read that ram is the main problem for some of these, so I don't know what to think. My computer is a HP Pavilion Desktop, running Vista Home Premium x64, I have an AMD Tricore, and 4 GBs of ram. Any ideas? Thanks!

Submarine · Mar 1, 2009

0x0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY "A driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware. If a driver file is named in the error message, try to correct the problem by disabling, removing, or rolling back the driver"

This points against a driver. Any clue from Event Viewer or "Problem Reports..."?

Have you installed anything new just before this started?

You may be able to fix it by doing a system restore to before this started.

lordbob75 · Mar 1, 2009

Hello Harblkips,

Here is the best suggestion: Take it back.

If you really don't want to do that, then we will do what we can:
d1: DRIVER_IRQL_NOT_LESS_OR_EQUAL (driver error)
4e: PFN_LIST_CORRUPT (driver error)
1e: KMODE_EXCEPTION_NOT_HANDLED (memory error)
c5: DRIVER_CORRUPTED_EXPOOL (paged memory error)
3b: SYSTEM_SERVICE_EXCEPTION (paged memory error)

Some of these are common, and some are not. The best solution is again, to take it back for a new one.

~Lordbob

rive0108 · Mar 1, 2009

These STOP errors apparently caused by access violations; bad drivers; bad physical memory; corruption; device errors; code errors; and an attempt to write in read-only Memory, leads me to believe you might have bad physical memory, but I suspect Windows Corruption is more likely [either due to malware and/or the misuse of a registry Cleaner]. Your system is no longer stable, and I suggest you backup all your User data while you still have the chance... You are probably not far from catastrophic system failure.

I suggest you reformat/reInstall Vista- use a good antivirus program, and stop using a registry Cleaner, and if necessary, replace defective physical memory stick(s)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL -bad driver(s) The system attempted to access pageable memory using a kernel process IRQL
that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

Error code: 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED
error message indicates that an error condition was detected by the kernel and Windows was unable to continue running because of this error condition. The types of problems that can cause a "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message are very similar to the problems that cause a "STOP 0x0000000A" error message, such as bad pointers, invalid addresses and other types of access violations. The STOP 0x0000001E bug check identifies an error that occurred in a section of code where no error handling routines exist.

Stop 0x0000004e PFN_List_Corrupt. The page frame number (PFN) list is corrupted, typically caused by passing a bad memory descriptor list. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists

error code: 0x000000be: Attempted to write to Read-only memory Usually caused by a buggy device driver

error message 0x000000C5: DRIVER_CORRUPTED_EXPOOL -The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool

error message SYSTEM_SERVICE_EXCEPTION It indicates an exception was raised in a system service which was not handled by the system service.

Harblkips · Mar 1, 2009

I do run Tune Up Utilities Registry Cleaner from time to time, could that really cause it?
For virus protection I use AVG Free, should I use something else?

rive0108 · Mar 1, 2009

Note-
To check your physical memory sticks, use Vista's Memory Diagnotic tool - You may want to replace them if they fail on top of reinstalling Vista. If a stick is bad, it cannot be fixed- only replaced.

Here is how:
Start> Control Panel> Click "Classic View" (top left corner)> click "Administrative Tools">Click "Memory Diagnostics"

If you determine your Memory is ok, then just reinstall Vista, use a top of the line antivirus/antimalware program (NOD32, Norton, Avira, Avast!, etc.)- and NO REGISTRY CLEANERS.

rive0108 · Mar 1, 2009

Harblkips said:
I do run Tune Up Utilities Registry Cleaner from time to time, could that really cause it?
For virus protection I use AVG Free, should I use something else?

AVG is ok, but did not fare very well in recent antivirus comparative testing: http://www.vistax64.com/system-security/172321-vista-sp1-antivirus-performance.html

Registry cleaners for those who dont know how to use them can quickly kill a system. Read this regarding Registry Cleaners:http://www.vistax64.com/software/212354-do-not-use-registry-cleaners-post974945.html#post974945
Almost every registry cleaner is not able to distinguish between unwanted and legitimate entries, letting it "clean" without oversight is the real issue. If you know the function of the entries it wants to "clean" and clean them it works fine. If you do not know the function then you do not let it "clean" them- rule of thumb. [or you may find yourself re-installing Windows due to corruption]

roy69 · Mar 2, 2009

Do as has been suggested. - Take it back.
A memory error can in time cause all sorts of problems. The longer the memory error goes on the worst things can get (depending what part of RAM is bad).
I would not suggest using a registry or any tune up utility unless you know what you are doing, I always advise people to check the results before applying. I have seen to many systems requireing a complete reinstall because users have just accepted the programs recommendations.

Harblkips · Mar 2, 2009

Thanks for all your input guys, it's very helpful. I'm going to start backing up all my things and try a clean install. If that does not work then I'll bring it back, good ol' warranty.

I'll keep you updated.

lordbob75 · Mar 2, 2009

Good choice.

~Lordbob

Harblkips · Mar 9, 2009

Okay I reinstalled Vista, and just went along regular business to check if everything was fixed. So far all is well, except one problem that baffles me. Whenever I start my computer up the screen goes black and nothing happens. So I power off, and reboot and hit "Start Windows Normally" and everything works fine. I got two blue screens on start up since the reinstall, a c5 and a d1. Could this be from my new video card? It was doing this before the reinstall as well. Or could it be because i had dual booted Vista and Windows 7 from the same hard drive (Which i stopped so all i have now is Vista.) Again, thanks for all your help!

lordbob75 · Mar 9, 2009

Harblkips, that looks like a bad driver. Something is trying to load at startup, and it doesn't like it. Did this happen on the first boot?

~Lordbob

Harblkips · Mar 9, 2009

Yep, First Boot, then second one works fine. I had a feeling it was the driver, this one game I play crashes randomly because the "display driver stopped responding" guaranteed to happen every time I play. I know I have the latest version of the driver, from nvidia at least, maybe theres one from Asus?

H2SO4 · Mar 9, 2009

Don't be tempted to assume that all errors, and in particular all crashes, stem from the same underlying root cause on your machine. They _might_, or they might not. It's impossible to tell without a closer look.

Also, troubleshooting BSoDs by just looking at stop codes (that first 0xA, 0xD1, ox50... number) is for the most part an exercise in pointless frustration. Yes, there are some stop codes which inevitably point at borked hardware (0x9c for example), but the vast majority do not fall into that category - they might be either software or hardware, and nobody can tell for sure without more info.

In your \Windows\minidump folder, you might find memory dump (*.dmp) files corresponding to these latest, post-rebuild crashes. If you zip up and upload a few of the latest ones, it may be possible to give you a better guess/analysis

lordbob75 · Mar 9, 2009

H2SO4 said:
Don't be tempted to assume that all errors, and in particular all crashes, stem from the same underlying root cause on your machine. They _might_, or they might not. It's impossible to tell without a closer look.

Also, troubleshooting BSoDs by just looking at stop codes (that first 0xA, 0xD1, ox50... number) is for the most part an exercise in pointless frustration. Yes, there are some stop codes which inevitably point at borked hardware (0x9c for example), but the vast majority do not fall into that category - they might be either software or hardware, and nobody can tell for sure without more info.

In your \Windows\minidump folder, you might find memory dump (*.dmp) files corresponding to these latest, post-rebuild crashes. If you zip up and upload a few of the latest ones, it may be possible to give you a better guess/analysis

*Grumbles*
Your right...

~Lordbob

Harblkips · Mar 9, 2009

I looked at them myself (I don't know anything about them I just wanted a gander) they seem to be about the same thing. All about a file called ntoskrnl.exe. Anyway, here they are.

H2SO4 · Mar 10, 2009

No obvious answers in there I'm afraid, or at least they're not obvious to me

Two of the dumps show what's called a pool corruption problem. Something is mangling memory, except that by the time that use of the corrupted data leads to a crash, the original culprit is long gone.

I'd suggest following Flavius's excellent advice here:

http://www.vistax64.com/973966-post8.html

Once you're running in that special mode, you may get even more BSoDs for a while, but the difference is that the dumps may reveal the memory corruptor at the time it's doing "bad".

It still could be hardware though.

lordbob75 · Mar 10, 2009

Hey H2SO4, how do you read the dump? I was just getting no file extension...

~Lordbob

H2SO4 · Mar 10, 2009

lordbob75 said:
Hey H2SO4, how do you read the dump? I was just getting no file extension...

~Lordbob

Hey Lordbob

Here's a "walkthrough":

How to read the small memory dump files that Windows creates for debugging

Except some of those instructions are ugly and dated and they'll lead to tears, so here's what I suggest you do instead:

1) Download that debugger package and "custom" install it to c:\debuggers

2) Run "c:\debuggers\windbg -IA" That'll register the WinDBG debugger as the default handler for DMP files.

3) Just double-click any DMP file. It should now open in WinDBG. Eventually it'll give you a prompt.

4) type (with that leading full stop): .symfix+ c:\SymCache

5) .reload

6) !analyze -v

That !analyze command is an automated mechanism which does its best to tell you what actually caused the crash. In say 50% of software-caused crashes, it's smart enough to find the answer.

Have fun with it

lordbob75 · Mar 10, 2009

Thanks. Have some rep.

~Lordbob

(oops, or not.)

Vast Amount of Blue Screens

New Member

My Computer

Member

My Computer

Lord of Bobs

My Computer

My Computer

New Member

My Computer

My Computer

My Computer

47,65,65,6B

My Computer

New Member

My Computer

Lord of Bobs

My Computer

New Member

My Computer

Lord of Bobs

My Computer

New Member

My Computer

A bit of a numpty

My Computer

Lord of Bobs

My Computer

New Member

Attachments

My Computer

A bit of a numpty

My Computer

Lord of Bobs

My Computer

A bit of a numpty

My Computer

Lord of Bobs

My Computer