PC Review


Reply
 
 
Flavio
Guest
Posts: n/a
 
      8th Dec 2003
Hi all,
Ever since I got my computer (clone) I've been having
BOSD. The most usual form is

DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP: 0x000000D1
HSF_DP.SYS

I've also seen:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP: 0x000000D1
HSFHWCD2.SYS
------------

STOP: 0x0000008E
NV4_disp.dll
------------

MAXIMUM_WAIT_OBJECTS_EXCEEDED
STOP: 0x0000000C
------------

BAD_POOL_CALLER
------------

I have an ASUS A7V333 Mobo, with 256MB of generic RAM,
Athlon XP 1800+, Chaintek GeForce4 Ti4400, XP Home, all
the newest drivers. I tried replacing the memory (I had
originally 512MB, but 2 generic chips 256 MB and diff
specs one PC2700 and the other PC2100 - now I left the
PC2100, assuming it might be a speed problem) I tried
several BIOS options, but still bad. ONly thing I
haven't tried is flashing my BIOS - I'm a little
concerned of just disabling the whole system.

These BOSD are very frequent, at least once a day.

Any suggestions?
(E-Mail Removed)

THANKS!!!
 
Reply With Quote
 
 
 
 
Malke
Guest
Posts: n/a
 
      8th Dec 2003
Flavio wrote:

> Hi all,
> Ever since I got my computer (clone) I've been having
> BOSD. The most usual form is
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL
> STOP: 0x000000D1
> HSF_DP.SYS
>
> I've also seen:
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL
> STOP: 0x000000D1
> HSFHWCD2.SYS
> ------------
>
> STOP: 0x0000008E
> NV4_disp.dll
> ------------
>
> MAXIMUM_WAIT_OBJECTS_EXCEEDED
> STOP: 0x0000000C
> ------------
>
> BAD_POOL_CALLER
> ------------
>
> I have an ASUS A7V333 Mobo, with 256MB of generic RAM,
> Athlon XP 1800+, Chaintek GeForce4 Ti4400, XP Home, all
> the newest drivers. I tried replacing the memory (I had
> originally 512MB, but 2 generic chips 256 MB and diff
> specs one PC2700 and the other PC2100 - now I left the
> PC2100, assuming it might be a speed problem) I tried
> several BIOS options, but still bad. ONly thing I
> haven't tried is flashing my BIOS - I'm a little
> concerned of just disabling the whole system.
>
> These BOSD are very frequent, at least once a day.


This error indicates a problem with a driver or your RAM. Update all
drivers, including motherboard drivers. If that doesn't work, then test
the RAM with something like memtest86. Flashing your BIOS will do
nothing for you regarding Windows because this is a Windows error. If
your RAM is faulty, flashing your BIOS will also not cure the problem.
It doesn't matter if your RAM is new - it can still be faulty, not the
proper type for your m/b, and you should keep RAM all the same type.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
 
Reply With Quote
 
Plato
Guest
Posts: n/a
 
      9th Dec 2003
Malke wrote:
>
> nothing for you regarding Windows because this is a Windows error. If
> your RAM is faulty, flashing your BIOS will also not cure the problem.


If your ram is bad, then flashing a bios with bad ram can phark your
bios.







--
http://www.bootdisk.com/
 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DRIVER_IRQL BOSD David Veltrubsky Windows XP 8 27th Sep 2011 08:45 PM
Re: BOSD vista ultimate Jim Windows Vista General Discussion 0 27th Oct 2009 02:45 PM
BOSD Harry Windows XP General 7 1st Aug 2007 06:27 AM
BOSD, Stop Error Need Help Please =?Utf-8?B?Sm9obiBLaWxpSw==?= Windows Vista Hardware 0 25th Feb 2007 04:28 AM
Re: Help! SCSI drive & XP crash BOSD Michael W. Ryder Windows XP Hardware 0 25th Jun 2003 10:50 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 02:16 PM.