Blue Screen telling me to contact Bill Gates???

[Guest]

My computer will lock-up at completely random times. When the lock-up occurs
the screen will go blank or do some black&white checkerboard-mess, and if
there is music playing or game sounds at the moment of crash the speakers
will output a machine-gun-like noise. Occasionally, but not very often I
will actually get a Blue Screen stop error. These are the ones I have
recorded 50, D1, 24, 12, 7F (insert into 0x000000??), as the different errors
with 7F showing up the most. The crashes have been occurring since I built
this system (in March), but the Blue Screens only began showing up when I got
Kingston to send me replacements Ram chips.

The Blue Screen looks typical except for the last line which I have never
seen before, and the local computer shop tells me they have never heard of it
before either.

Beginning Dump of Physical memory
Physical memory dump complete.
Contact your system administration or technical support group or Bill
Gates for further assistance.

I have run the following programs in an attempt to locate a virus or other
bad program. Ad-Aware 6 Pro, Norton Antivirus (the pre-install scan), Trend
Micro House Call, and Trend Micro Internet Security 11 (which was installed
shortly after my last clean install of XP).

The Computer
Motherboard - Soyo SY-KT600 DRAGON Ultra Platinum
CPU - AMD Athlon XP 3200+ 400FSB
Ram - 3 x Kingston 512MB (KVR400X64C25/512)
Video Card - Ati Radeon 9800 Pro 128MB
HD - Seagate 120GB SATA
Generic CDRW and Floppy
Case - Xoxide X-Dreamer II with 5 fans
PSU - Antec NeoPower 480Watt

I had the system tested at a local shop back in April, and was told the
motherboard was the problem because the system would run stable if all of my
components were installed on a different board. Sent the board back to Soyo
($56 shipping) and was told by them (after losing my motherboard for 5 days,
and then another 5 days of testing and phone calls) that there was nothing
wrong with it, and they sent it back. After that I talked to Kingston and
they agreed to replace all 3 of my Ram. I currently am only using 2 of the
chips because the system seems more unstable when the third is installed. I
have the most recent drivers installed for all of my components except for
the motherboard. The motherboard drivers are up to date except for the BIOS.
When I flash the BIOS with the most recent version, the system becomes
extremely unstable. The current BIOS is one step back from the most recent.
Also, if I go into the BIOS and load the Fail-Safe settings, the system will
not boot past POST for more than about 10 seconds, in which time I have to
race the clock to load the BIOS load the Optimized Defaults, and Save and
Exit or else reset the BIOS via jumper and attempt to beat the clock again.

I would greatly appreciate....oh let’s be honest...after this much headache
and frustration I would almost worship anyone that could help me fix my
system.

My next step is to buy a new motherboard and cpu and try again... I may
purchase the same ones as current to test for bad components or maybe go with
something different that will allow me to use the Ram that I currently have.

Thank you very much to everyone that responds.

Jeremy

 

[DL]

With a msg like that, it looks like a virus/trojan

 

[David Candy]

If it truely is random crashes then it is a hardware problem. But numbers aren't good enough. The full message is required.

 

[Guest]

I have scanned the system with Norton (downloaded today), Trend Micro online
Housecall (today also), and have active Trend Micro Inet Security. If these
did not find anything wrong, would it still be likely to be virus/trogan
problem?

 

[Miss Perspicacia Tick]

Monet 138 wrote:
These are the ones I have recorded 50, D1, 24,

12, 7F (insert into 0x000000??), as the different errors with 7F

12 - TRAP_CAUSE_UNKNOWN

By its very nature, this error means that the cause of the identified
problem is unknown. Especially try to track it down by noting the history of
the problem, when it appeared, and what changes were made to the system
since the problem first appeared, as well as noting what activity you are
attempting at the time the error message appears.

24 - NTFS_FILE_SYSTEM

A problem occurred within NTFS.SYS, the driver file that allows the system
to read and write to NTFS file system drives. There may be a physical
problem with the disk, or an Interrupt Request Packet (IRP) may be
corrupted. Other common causes include heavy hard drive fragmentation, heavy
file I/O, problems with some types of drive-mirroring software, or some
antivirus software. I suggest running ChkDsk or ScanDisk as a first step;
then disable all file system filters such as virus scanners, firewall
software, or backup utilities. Check the file properties of NTFS.SYS to
ensure it matches the current OS or SP version. Update all disk, tape
backup, CD-ROM, or removable device drivers to the most current versions.

50 - PAGE_FAULT_IN_NONPAGED_AREA

Requested data was not in memory. An invalid system memory address was
referenced. Defective memory (including main memory, L2 RAM cache, video
RAM) or incompatible software (including remote control and antivirus
software) might cause this Stop message, as may other hardware problems
(e.g., incorrect SCSI termination or a flawed PCI card).

7F - UNEXPECTED_KERNEL_MODE_TRAP

One of three types of problems occurred in kernel-mode: (1) Hardware
failures. (2) Software problems. (3) A bound trap (i.e., a condition that
the kernel is not allowed to have or intercept). Hardware failures are the
most common cause (many dozen KB articles exist for this error referencing
specific hardware failures) and, of these, memory hardware failures are the
most common.

D1 - DRIVER_IRQL_NOT_LESS_OR_EQUAL


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.


For more information on these errors, including links to appropriate KB
articles and other troubleshooting resources, please see MVP Jim Eshelman's
extensive and detailed troubleshooter which can be found at
http://aumha.org/win5/kbestop.htm.

 

[Miss Perspicacia Tick]

If it truely is random crashes then it is a hardware problem. But
numbers aren't good enough. The full message is required.

Numbers are perfectly good enough. The stop code is all that's needed - the
rest of the error is just a waste of space.

 

[David Candy]

Except it often includes the filename that is crashing
STOP: C0000221 unknown hard error
<path>\<file name>