BSOD at random times

Hello, first, sorry for my poor english.

I hope someone can help me here:

I'm getting some IRQL_NOT_LESS_OR_EQUAL Blue Screen. That happens every two or three days, and always displays the same error. Sometimes happens when i'm loading MSN, IE and other apps.

Ok, so i stored the MEMORY.DMP and analyzed with WinDBG and this is what i got:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {d7c8, 2, 0, 804e6043}

Probably caused by : ntoskrnl.exe ( nt!KiInsertQueueApc+6c )

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000d7c8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804e6043, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: 0000d7c8

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiInsertQueueApc+6c
804e6043 8b5f04 mov ebx,dword ptr [edi+4]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: csrss.exe

TRAP_FRAME: fd3dbc54 -- (.trap fffffffffd3dbc54)
ErrCode = 00000000
eax=fe83e2c0 ebx=00000000 ecx=80c9d790 edx=00000000 esi=80c9d790 edi=0000d7c4
eip=804e6043 esp=fd3dbcc8 ebp=fd3dbcd8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KiInsertQueueApc+0x6c:
804e6043 8b5f04 mov ebx,dword ptr [edi+4] ds:0023:0000d7c8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 804e6043 to 804e187f

STACK_TEXT:
fd3dbc54 804e6043 badb0d00 00000000 80e5a878 nt!KiTrap0E+0x233
fd3dbcd8 804e5451 fe83e2c0 00000001 00000000 nt!KiInsertQueueApc+0x6c
fd3dbcf8 80583208 fe83e2c0 fe83e2c0 00000000 nt!KeInsertQueueApc+0x40
fd3dbd28 80582cdf 80c9d790 c0000005 fd3dbd64 nt!PspTerminateThreadByPointer+0xcb
fd3dbd54 804de7ec 00000000 c0000005 0057fff4 nt!NtTerminateProcess+0xd5
fd3dbd54 7c91eb94 00000000 c0000005 0057fff4 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0057fff4 00000000 0000008c 00000000 00000000 0x7c91eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiInsertQueueApc+6c
804e6043 8b5f04 mov ebx,dword ptr [edi+4]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiInsertQueueApc+6c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42251106

FAILURE_BUCKET_ID: 0xA_nt!KiInsertQueueApc+6c

BUCKET_ID: 0xA_nt!KiInsertQueueApc+6c

Followup: MachineOwner
---------

eax=ffdff13c ebx=00000002 ecx=00000000 edx=40000000 esi=804e6043 edi=0000d7c8
eip=804e187f esp=fd3dbc3c ebp=fd3dbc54 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KiTrap0E+0x233:
804e187f f7457000000200 test dword ptr [ebp+70h],20000h ss:0010:fd3dbcc4=00010246
ChildEBP RetAddr Args to Child
fd3dbc54 804e6043 badb0d00 00000000 80e5a878 nt!KiTrap0E+0x233 (FPO: [0,0] TrapFrame @ fd3dbc54)
fd3dbcd8 804e5451 fe83e2c0 00000001 00000000 nt!KiInsertQueueApc+0x6c (FPO: [Non-Fpo])
fd3dbcf8 80583208 fe83e2c0 fe83e2c0 00000000 nt!KeInsertQueueApc+0x40 (FPO: [Non-Fpo])
fd3dbd28 80582cdf 80c9d790 c0000005 fd3dbd64 nt!PspTerminateThreadByPointer+0xcb (FPO: [Non-Fpo])
fd3dbd54 804de7ec 00000000 c0000005 0057fff4 nt!NtTerminateProcess+0xd5 (FPO: [Non-Fpo])
fd3dbd54 7c91eb94 00000000 c0000005 0057fff4 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ fd3dbd64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
0057fff4 00000000 0000008c 00000000 00000000 0x7c91eb94
start end module name
804d7000 806ebb00 nt ntoskrnl.exe Tue Mar 01 19:04:06 2005 (42251106)
806ec000 8070c380 hal halaacpi.dll Tue Aug 03 23:59:05 2004 (41107B29)
bf800000 bf9c1200 win32k win32k.sys Wed Oct 05 18:09:50 2005 (43446B4E)
bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 00:00:51 2004 (41107B93)
bf9d4000 bfc4a000 SiSGRV SiSGRV.dll Sat Sep 03 04:02:30 2005 (431974B6)
f9f9e000 f9fc7f00 kmixer kmixer.sys Wed Aug 04 00:07:46 2004 (41107D32)
fa294000 fa2d4080 HTTP HTTP.sys Fri Oct 08 17:18:26 2004 (41672042)
fa2fd000 fa34e300 srv srv.sys Mon May 09 18:22:19 2005 (427FFEBB)
fa417000 fa443400 mrxdav mrxdav.sys Wed Aug 04 00:00:49 2004 (41107B91)
fa559000 fa56d400 wdmaud wdmaud.sys Wed Aug 04 00:15:03 2004 (41107EE7)
fa8d6000 fa8ed480 dump_atapi dump_atapi.sys Tue Aug 03 23:59:41 2004 (41107B4D)
Unloaded modules:
f9f9e000 f9fc8000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f9f9e000 f9fc8000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f9f9e000 f9fc8000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fa17a000 fa1a4000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fa17a000 fa1a4000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fa17a000 fa1a4000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fd899000 fd89a000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fa50c000 fa536000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fa536000 fa559000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
faaa5000 faab2000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
faab5000 faac3000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fd6d8000 fd6da000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fa403000 fa417000 Parport.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
fd35c000 fd367000 imapi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fd49c000 fd4a1000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
fcf41000 fcf44000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000

Just trimmed the --> start end module name
because it was too long.

Any suggestions?, i know is some Driver related problem, but can't find what it is.

Thanks a lot in advance, and if more info is needed, i'll post it here

 

i'm not sure about that error log you posted up.....but i just did a couple of searches using the term: "IRQL_NOT_LESS_OR_EQUAL ".

I found a ton of people are having the same problem. There are a ton of forum posts on that problem and the threads are huge, some are about three to four pages. I'm pretty sure you'll definelty find some answers there.

I punched those terms into google and thats where i got the results.

 

Hi, GaussTek. Welcome to Windows BBS!

I'm sorry to say we don't seem to have crash dump analysis experts around here lately.

If you are always getting a STOP: 0x0000000A blue screen error (which I think is what your posted dump shows), then the following Microsoft Knowledgebase article might help you solve your particular problem.

Troubleshooting a Stop 0x0000000A error in Windows XP

• Scroll down to the "A Stop 0x0A error after Windows XP is already installed" section.

If you installed any new hardware immediately prior to to the time your crashes started occurring, then I would be inclined to suggest doing the following part of Microsoft's instructions first:

You should be able to find drivers for your newly added hardware at that hardware manufacturer's website.

Event Viewer can be accessed as follows:
Click Start. > Click Control Panel. > Open Administrative Tools. > Open Event Viewer.

If you have any questions, feel free to ask.

Good luck! Please keep us posted.

 

GaussTek,

Please keep in mind, I am NOT an expert regarding crash dumps.

I just found this thread that seems to be similar to yours, I think.

Your Dump:

Their Dump:

The expert recommendation in that thread I linked is to update the motherboard's BIOS (among other things that I would be hesitant to try).

I suppose it wouldn't hurt to check for a BIOS update for your particular motherboard at your motherboard manufacturer's website. Sometimes, older BIOS versions have trouble with newer hardware, I think.

If you don't know what your EXACT motherboard manufacturer and model number is, then you can find out by downloading and running Belarc Advisor. When you run Belarc Advisor, it will take several seconds to inventory your computer's information and then it will open up a browser window with your computer's information. Your motherboard information will be in the "Main Circuit Board" section near the top of the 2nd column of your Belarc Advisor report.

Be sure to carefully follow the motherboard manufacturer's instructions about how to flash your BIOS (if a newer version is available for your EXACT motherboard model).

 

GaussTek,

I would try updating your video drivers before a BIOS update (there seems to be a 'hint' of a graphics problem related to your crash). The Belarc Advisor utility that Mailman suggested is a very good program for identifying hardware and will help you identify your video card if you're not sure what it is. Go to the manufacturer's website and download your video drivers. Check to see if there are any specific instructions for installation (i.e. uninstalling 'old' drivers before installing new ones, etc).

B

 

An 0x8E error in addition to an 0x)A would have nailed it for me, so I am voting for Mr. B's suggestion to update your video adapters, including all of his suggestions about cleaning old driver remants, etc.

The extreme gamers do a real service to the user community in pounding the heck out of video adapters and their drivers. I always Google the name and version number of a possible new adapter driver to see what the community has found.

With Video drivers it is often the case that the brand newest driver is not the one you want -- you want the one a few versions ago in many cases.

The Video adapter folks really abuse the user community by making them test their products after release.

When in doubt, choose the driver that is WHQL certified.

-------------------------------

As a side note:

It was this in the dumpchk that gave me pause:

DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: csrss.exe

If you start seeing 0x8E errors as well as your 0x0A errors, uninstall Windows Defender if it is installed.
Reinstall a newly download version.



.

 

Thanks for all the responses, and sorry for not answering before. Sorry (again) for my bad english.

Yeah, it seems i forgot to mention some things:

The PC is relatively new, i bought it like a month ago and it's ensambled (not by me). It does have WinXP SP2 (also wasn't installed by me). Keep in mind this PC is just for surfing the NET, use Office and MSN (which it does very well, besides the BSOD), so that's why it does have very low specs. I have a PC for gaming and it's working fine, but most time is in use, so that's why i got this:

AMD Geode NX 1750 (On board CPU). Motherboard PCCHIPS 863G. 256 RAM, SIS Mirage Graphics (Integrated), HD 40 GB Seagate.

So, the first two weeks it was working great, but then started to randomly reseting by itself (i didn't add new hardware or something). The first thing i did was opening the Case, but everything seemed to be fine, also checked the RAM and did memtest like an hour, but didn't show any errors. So, i decided to keep it like that. Then happened again, and decided to activate the memory dumps, then i got the BSOD and discovery it was the IRQL error.

Yeah, i googled first, and then concluded it was a Driver error because the Memory was fine (like i said, i ran some memory tests). I thought checking the memory dump was gonna be easy and i will discover the faulty driver (because i don't have a lot of time to checking every driver), but didn't understood very well, and that's why i posted it here.

SO (sorry for the long text), i just follow your recommendations, and started updating the VGA Driver (for the SIS Mirage Graphics): Checked PCChips Website, selected my MotherBoard model, and the only driver that seems needed update was precisely the VGA Driver, so downloaded it, uninstalled the old drivers, installed the new ones and it seems working fine.

BUT like i said, the errors come up randomly, so i'll wait a few days, and if i get the BSOD again, i'll post the dump here if something changed.

Oh, and also checked the BIOS at the PCChips web, and it seems older than the one i have installed (just checked the date with the utility). So that's weird. Perhaps i don't have the right BIOS installed? It's safe to update, even if it seems older??

I don't have Windows Defender installed (or seems i don't). And a side note: checked event viewer, and doesn't show any errors, just got some weird Application Popups in every boot . They say: Machine Check: Regs. Got like six of them, but it shows them as Information. Any idea if it's related to the problem?

THANKS alot again for your help!!.

 

I agree. That does seem weird. I would be inclined to contact your PC builder and ask about the apparent BIOS revision discrepancy.

If the PC was built by a commercial organization that produces PCs under a brand name, then perhaps the organization created their own modified BIOS revision for their builds that might not match the motherboard manufacturer's available BIOS revision(s).

Even if your PC builder is a commercial organization, I would still be inclined to ask about the apparent BIOS revision discrepancy.

I would suggest not doing this until you have investigated further to determine whether it would be safe or advisabe to do so. CAUTION: Experimenting with the BIOS can possibly render your PC unbootable, which could require purchasing a new BIOS chip for your motherboard.

Please keep us posted.

 

Yeah, it's a commercial organization or sort of.
It's an online store located on my country. You just choose the components you want and then they send to you the PC "fully working ".

Ok, so about the BIOS, just checked with PC Wizard to confirm:

Manufacturer: American Megatrends Inc.
Version: 080010
Date: 22 December 2005

And from the PCChips Web:
Downloads --> MotherBoard --> OnBoard CPU --> M863G --> BIOS -->
BIOS Name BIOS for M863G V7.1C
Version 050908S
Release Date 2005/09/08
file name: 050908S.rom

It uses aminf342.exe to flash the BIOS (AMI Flash Utility). So it is the same manufacturer. Also checked again the MotherBoard model and confirmed is M863G.

So yeah, i will call the store tomorrow to check about the BIOS. It does have warranty, but dunno if applies to this, i mean... sometimes works fine, sometimes i got the error, and probably it's just software/driver/bios error. Anyway, at the moment i haven't got any BSOD.

I'll post when it comes more. Thanks again!

 

Sorry for double posting, got another BSOD today, and already updated the video drivers. This time is a bit different. Dump Log:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {4, 2, 1, 804dbe9b}

Probably caused by : rdbss.sys ( rdbss!RxTimerDispatch+be )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804dbe9b, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 00000004

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiInsertTimerTable+4e
804dbe9b 894204 mov dword ptr [edx+4],eax

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

TRAP_FRAME: 8054ff64 -- (.trap ffffffff8054ff64)
ErrCode = 00000002
eax=f997d1b8 ebx=00000000 ecx=f9a30ba8 edx=00000000 esi=f997d1a0 edi=80559868
eip=804dbe9b esp=8054ffd8 ebp=8054ffe0 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!KiInsertTimerTable+0x4e:
804dbe9b 894204 mov dword ptr [edx+4],eax ds:0023:00000004=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 804dbe9b to 804e187f

STACK_TEXT:
8054ff64 804dbe9b badb0d00 00000000 026a9fab nt!KiTrap0E+0x233
8054ffe0 804dbeff fff79b90 ffffffff 028a10ae nt!KiInsertTimerTable+0x4e
8054fffc 804dc3cb fff79b90 ffffffff f997d1d0 nt!KiInsertTreeTimer+0x7d
8055001c 804dc402 0097d1a0 fff79b90 ffffffff nt!KeSetTimerEx+0x4b
80550038 f9973405 f997d1a0 fff79b90 ffffffff nt!KeSetTimer+0x18
80550064 804dc4fd f997d1e0 00000000 a025f31c rdbss!RxTimerDispatch+0xbe
80550180 804dc378 80558e80 80558c20 ffdff000 nt!KiTimerListExpire+0x122
805501ac 804dbbd4 80559280 00000000 000dd869 nt!KiTimerExpiration+0xaf
805501d0 804dbb4d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x46
805501d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x26


STACK_COMMAND: kb

FOLLOWUP_IP:
rdbss!RxTimerDispatch+be
f9973405 8b45f4 mov eax,dword ptr [ebp-0Ch]

SYMBOL_STACK_INDEX: 5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: rdbss

IMAGE_NAME: rdbss.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4180480f

SYMBOL_NAME: rdbss!RxTimerDispatch+be

FAILURE_BUCKET_ID: 0xA_W_rdbss!RxTimerDispatch+be

BUCKET_ID: 0xA_W_rdbss!RxTimerDispatch+be

Followup: MachineOwner
---------


Any Ideas? If you need more info, just tell me... Thanks a lot again!

 

Hi, GaussTek.

According to Tek-Tips:

Also keep in mind the newest graphics (video) drivers are not necessarily the best for a system. One of our hardware experts, mattman, has told me in another thread:

Therefore, consider trying older graphics drivers if they're available for your particular graphics card.

mattman also recommended (in the same thread) that graphics drivers should be uninstalled in Safe Mode (preferably via Add or Remove Programs) and installed in Normal Mode.

 

Possible Resolutions:

A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.

A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.

If you encounter a Stop 0xA message while upgrading to Windows XP, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.

Troubleshooting a Stop 0x0000000A Error in Windows XP
http://support.microsoft.com/default...;en-us;Q314063

.



.

 

Hello mailman, I sure hope I'm right I think it would be well worth trying those suggestions , graphics drivers can become corrupted.

I might bring another angle, and I have only suggested this once or twice because I don't have a great deal of troubleshooting experience with XP (I keep mine isolated from the internet and free of any programs that I have known to have caused problems in the past...although troubleshooting the Win XP machines where I work, without having Administrator rights...that's fun ).

Basic IRQs are set by the BIOS during startup. When Windows loads the drivers for "higher level" hardware it starts sharing the IRQ allocations. It might sound to me like some of the shares are not working and there is a resource conflict. GaussTek, if you have add-in (PCI) cards, move them into different PCI slots. Put any soundcards or (dialup) modems into the last slots, near the edge of the motherboard, others can go closer to the motherboard connectors (the first slots). Moving them around will reallocate the resources and also reinstall the drivers for those pieces of hardware (the drivers will be reinstalled automatically). I have had very little experience with PCchips motherboards, but check in the BIOS/Startup settings if any hardware that you may not use can be disabled, this may free up resources for other hardware. Use the motherboard manual to check if items can be disabled (examples might be built-in audio, LAN or say, Firewire).

The other area I would consider is motherboard/chipset drivers. These are the top of the driver hierarchy. If you have a good set of chipset drivers installed you won't be banging your head wondering why any other drivers or hardware don't seem to work. Check if there are any updates for the chipset drivers at the PCchips website (and I might also look at the chipset manufacturer's website...SiS?). Everest in my signature will help you identify the hardware (and it might help further because you said *the BIOS upgrade seemed to predate your current version...be careful if they may be specifying a revision model of the motherboard*) In fact, I would hold off on the BIOS upgrade/flash until any other areas were exhausted. If you have not made any major changes to hardware, I could not see the BIOS suddenly becoming faulty.

Matt

 

IRQLs are not IRQs.

Completely different animals with no relationship.