Error Caused by a Device Driver

[cpc2004]

Hi Eternal,

I've processed your minidumps and it is a hardware error. Your Windows have various bugcheck codes such as 0A, 24, 50, 8E and D1. One minidump is inaccessible and one minidump failied at IRQL x'1c' which is at clock level interrupt. According to my record it is hardware error. For similar symptom, 4 are related to CPU, 1 is M/B and one 1 is RAM.

The BSOD occurs when your XP was SP1. After you upgrade to SP2, your XP still gets BSOD. This is an another evidence it is a hardware error.

There have no reliable tool to diagnostic which hardware component is faulty. You can try Windows Memory Diagnostic but it is very new. Memtest86 is not reliable.
http://oca.microsoft.com/en/windiag.asp

 

[The Eternal]

thanks

Thanks for your input... and rapid response,

i guess ill try replacing the processor first becasue of the probability of the stats you provided, after that ill move to the memory and finally to the motherboard.

Thanks
Eternal.

 

[cpc2004]

I am sure this is a hardware problem. There has no good tools to find out hardware component is faulty. Memtest86 is not reliable. Even memtest86 reports faulty hardware and you don't whether it is ram or L2 cache memory of CPU.

My record is based upon my resolved cases. As my sample is small and it may be inaccurate. After you fix the problem, you must let me know the result. I update my record and my recommendation for this case will be more accurate.

According to experience, I will try this sequence CPU, M/B and then RAM.

 

[Boxer]

I just started getting more IRQ_less than or equal to errors. I thought after replacing the PSU and RAM that it would have fixed it. But to no avail. I have attached 3 new minidumps for you to look at.

Regards
Boxer.

 

[cpc2004]

Boxer,

I think you changed the video card from ATI to nVdia. One crash is probably caused by nVidia Display Card Driver, Your version of nVidia Display is unstable and I suggest you must install the latest nVidia Display Card Driver. Two minidumps crashed with bugcheck 0A at mudule SaiNtHid.sys. I have no idea what is SaiNtHid.sys

 

[cpc2004]

Thanks for your input... and rapid response,

i guess ill try replacing the processor first becasue of the probability of the stats you provided, after that ill move to the memory and finally to the motherboard.

Thanks
Eternal.

Hi Eternal,

Do you have any update of your problem. You feedback will help us to resolve similar problem.

 

[The Eternal]

update

Well, i ran the recomended windows memory test with both memory sticks in and it crashed a few times (which led me to think that is was a faulty CPU) but then i got a recomendation to try it with one stick at a time and it appeared to work perfectly computer and all for both sticks individually. Then i put the second chip back into a different slot (not running in dual channel mode) and first thing that happned was a BSOD. So we decided to RMA the MOBO and we'll see how things go from there.

ps. i am currently in Hawaii for the month and wont be doing anymore work on the computer. but soon as i am back... ill let you know how it goes.

 

[cpc2004]

Im using 77.72 atm :O should I downgrade to 61.77?

Do you have any update of your problem?

 

[DeanKeaton259]

Plz Help I have a Similar Problem

For the past few weeks, my computer has either restarted while playing games, watching videos, or listening to music, or has just frozen and I've had to reboot. I'm uploading a few of the minidumps, hopefully you guys can help.
I'm on a P4 intel 1.8 ghz with 512 ddr sdram

 

[cpc2004]

All of your minidumps are inaccessible by microsoft windbg and this is symptom of faulty ram.

 

[DeanKeaton259]

so you're 100% sure it's my ram that's bad? Is there some way i could test this out to be sure?

 

[cpc2004]

I cannot guranteer 100% this is ram problem. Most likely it is caused by faulty RAM. You have take your risk when you make any decision. You can reseat the memory stick or downclock the RAM. You can run the memtest but it is not reliable.

 

[cpc2004]

Thanks for replying,no i haven't,and to speak honestly i have no idea what it is This means that the problem is in zonealarm? :suspiciou Oh my god!I could never imagine this :blackeye:

Edit:AHA!You mean blue screen?No I haven't seen blue screen at all.But i haven't done the thing you suggest to avoid autorestart.Should I?

Hi Sonia,
If you don't have blue screen, how do you get the minidump? Whenever windows XP crashes, it will take a minidump unless you specify no dump. BTW do you have any update of your problem?

 

[cpc2004]

Much like everyone else here, I too am having the same IRQ_Not_Less_or_Equal BSODs... plus a few others. :suspiciou There is not a singe day in the week that my PC does not BSOD a minimum of 2 times. Playing any game only makes the BSODs worse. Besides the BSODs my applications crash for no reason at all too. Worse of all, sometimes my PC just violently dies as though someone had reset the power button. No BSOD message, no app. error.. nothing, just dies.

After getting these for months on end I swapped the mobo and the CPU with new ones. No luck. There is no difference in the behavior. Swapped RAM, same thing.

I tried uploading my Minidumps here but got errors when trying to upload the zip file. Anyhow, I uploaded it to my server.

In the word of princes Leia, cpc2004, "you're my only hope!"

http://hawaiikenji.mysite4now.com/minidump.zip

-Kenji :blackeye:

Kenji,

Do you have any update? Let me know if you need further help.

 

[The Eternal]

Ok,
So in the end... i ended up just replacing the MOBO. something to do with the memory handeling becaseu when i used only 1 chip ... it was fine... more than one...... our favorite BSOD. Everything is great and i am very happy little camper.

Thanks for all your help.
Mobo type: Gigabyte 8I955X Royal

 

[cpc2004]

Hi Eternal,

Thanks for sharing your experience with us.

cpc2004

 

[KingPrawn]

Hi Eternal

You problem sounds very similar to mine with the same motherboard. https://www.techspot.com/vb/topic29616.html

I am wondering if this is a problem with that particular board or if there are a few duds out?

Simon

 

[Storm_Force]

Hi

I am having the same problem as well Could someone take a look at the minidump fiiles for me, thanks. Just changed the setting so hopefully I will get the bsod instead of the restart which should help a bit.

 

[KingPrawn]

Stormforce when you say you are having the same problem. Do you mean you have the same motherboard?

 

[Storm_Force]

oops, no sorry I mean I am getting the random reboots then the Error Caused By A Device Driver.

My Specs:

mobo ABIT IC7-G
P4 2.4ghz
1gb ram (2x512)
1 x sata 250gb HD
1 x 70gb HD

Win XP Home with SP2

 

[Storm_Force]

OK just had 2 bsod, heres the pics.

BSOD1
BSOD2

 

[cpc2004]

When Windows crashes with blue screen, it writes a system event 1001 and a minidump to the folder \windows\minidump. Check system event 1001 and it has the content of the blue screen

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001. Copy the content and paste it back here

Zip 5 to 6 minidumps and attach the zip files here (note the limit of each attachment at this website is 100k). I will study the dump and find out the culprit.

 

[KingPrawn]

Here are my details from the BSOD I keep on getting. Please can you help me find the driver that is incorrect ?


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 17/07/2005
Time: 17:12:08
User: N/A
Computer: PLAZMA
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x71a5df52, 0x00000002, 0x00000008, 0x71a5df52). A dump was saved in: C:\WINDOWS\Minidump\Mini071705-01.dmp.

 

[Storm_Force]

Ok here's mine:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 27/07/2005
Time: 21:32:42
User: N/A
Computer: GAVINSPC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc000001d, 0xbf805e8c, 0xb8603b4c, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini072705-03.dmp.

and

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 27/07/2005
Time: 21:16:06
User: N/A
Computer: GAVINSPC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000000, 0x00000002, 0x00000001, 0x85e59255). A dump was saved in: C:\WINDOWS\Minidump\Mini072705-02.dmp.

and the corresponding minidump files:

 

[cpc2004]

Storm Force,

One of your minidump crashed with memory corruption and it is symptom of faulty ram or CPU.


Bugcheck 8E
Arg1: c000001d, The exception code that was not handled
Arg2: bf805e8c, The address that the exception occurred at
Arg3: b8603b4c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {

FAULTING_IP:
win32k!DC::bCompute+65
bf805e8c f0e819010000 lock call win32k!RGNOBJ::vGetSubRect (bf805fab)

TRAP_FRAME: b8603b4c -- (.trap ffffffffb8603b4c)
ErrCode = 00000000
eax=e1f573c8 ebx=00000001 ecx=00000000 edx=00000000 esi=e1f57008 edi=e1f57418
eip=bf805e8c esp=b8603bc0 ebp=b8603bf8 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!DC::bCompute+0x65:
bf805e8c f0e819010000 lock call win32k!RGNOBJ::vGetSubRect (bf805fab)
Resetting default scope

CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf804757 to bf805e8c

STACK_TEXT:
b8603bf8 bf804757 00000000 7ffd6000 b8603d54 win32k!DC::bCompute+0x65
b8603c08 bf80dba1 b8603d38 80559450 84bc0da8 win32k!DEVLOCKOBJ::bLock+0x79
b8603d54 804de7be 0000000d 0173dda8 0173dde4 win32k!NtGdiFlushUserBatch+0xb6
b8603d64 7c90eb94 badb0d00 0173dda8 b83ccd98 nt!KiFastCallEntry+0xca
WARNING: Frame IP not in any known module. Following frames may be wrong.
0173dde4 00000000 00000000 00000000 00000000 0x7c90eb94


FAILED_INSTRUCTION_ADDRESS:
win32k!DC::bCompute+65
bf805e8c f0e819010000 lock call win32k!RGNOBJ::vGetSubRect (bf805fab)

CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
39 errors : !win32k (bf805c0b-bf805f7b)
bf805c00 9a ce ff ff 8b 0d 70 9c 9a bf e9 *00 bc ff ff 90 ......p.........
bf805c10 90 90 90 90 8b ff 56 8b f1 83 3e *48 57 8b 3d 9c ......V...>HW.=.
bf805c20 ad 98 bf 74 19 8b 46 08 8b 80 94 *00 00 00 85 c0 ...t..F.........
bf805c30 74 05 8b 48 04 ff d7 8b 0e e8 97 *48 ff ff 83 7e t..H.......H...~
bf805c40 04 00 75 09 f6 46 11 01 5f 5e 75 *00 c3 8b 46 0c ..u..F.._^u...F....
bf805c60 4e 04 e8 6e bc ff ff eb db 90 90 *00 90 90 8b ff N..n............
bf805c70 55 8b ec 8b 45 08 8b 10 29 11 8b *48 29 51 08 8b U...E...)..H)Q.....
bf805d00 e0 8b 88 e4 01 00 00 33 d2 42 89 *00 e4 39 b8 0c .......3.B...9..
bf805d10 03 00 00 75 c0 89 7d fc ff 75 1c *48 75 18 ff 75 ...u..}..u.Hu..u
bf805d20 14 ff 75 10 ff 75 0c 56 ff d1 89 *00 e4 83 4d fc ..u..u.V......M.
bf805d30 ff 8b 45 e4 e8 ba ae ff ff c2 18 *48 8b 45 0c eb ..E........H.E..
bf805d40 b5 47 eb 3f 47 eb 44 89 7d f8 e9 *48 00 00 00 8d .G.?G.D.}..H....
bf805d50 4d f4 e8 bc fd ff ff 8b 45 f4 85 *00 74 03 89 45 M.......E...t..E
bf805d60 fc 83 7d fc 00 75 31 83 65 f8 00 *48 a9 00 00 00 ..}..u1.e..H....
bf805d70 33 ff 85 c9 89 4d d8 74 02 8b fb *00 c0 89 44 bd 3....M.t......D.
bf805d80 d8 75 be 85 d2 89 54 bd d8 75 b9 *00 86 10 04 00 .u....T..u......
bf805d90 00 85 c0 89 45 fc 74 b7 3b fb 0f *48 7b 01 00 00 ....E.t.;..H{...
bf805da0 8b 45 d8 89 45 f4 8d 45 f4 50 8d *00 fc e8 52 e5 .E..E..E.P....R.
bf805db0 00 00 85 c0 74 b1 33 ff 8b 4d fc *48 7c fc ff ff ....t.3..M.H|...
bf805dc0 8d 86 d8 03 00 00 50 8d 4d fc e8 *00 e9 00 00 85 ......P.M.......
bf805dd0 c0 0f 84 70 ff ff ff 8b 45 f0 83 *48 20 70 0f 85 ...p....E..H p..
bf805de0 d7 00 00 00 8d 45 fc 50 8d 4d f0 *00 3d e4 00 00 .....E.P.M..=...
bf805df0 85 c0 0f 84 c3 00 00 00 8b 45 fc *48 86 10 04 00 .........E.H.......
bf805e80 c0 75 28 8d 86 c0 03 00 00 50 8d *00 f0 e8 19 01 .u(......P......
bf805e90 00 00 80 66 18 ef ff b6 0c 04 00 *48 8b ce e8 c0 ...f.......H....
bf805ea0 f6 ff ff 5f 5b 8b 45 f8 5e c9 c3 *00 4d f4 89 45 ..._[.E.^...M..E
bf805eb0 f4 e8 46 e3 00 00 83 27 00 eb c8 *48 4d f4 e8 50 ..F....'...HM..P
bf805ec0 fc ff ff 39 7d f4 74 4e 53 8d 45 *00 50 8d 45 f0 ...9}.tNS.E.P.E.
bf805ed0 50 8d 4d f4 e8 fd e6 00 00 85 c0 *48 39 8d 45 f4 P.M........H9.E.
bf805ee0 50 8d 4d fc e8 1b e4 00 00 85 c0 *00 29 8b 45 fc P.M.........).E.
bf805ef0 89 86 10 04 00 00 8d 86 c0 03 00 *48 50 8d 4d fc ...........HP.M.
bf805f00 e8 a6 00 00 00 80 66 18 ef 8d 4d *00 e8 eb e2 00 ......f...M.....
bf805f10 00 e9 fe fe ff ff 89 7d f8 eb ee *48 ff 02 75 22 .......}...H..u"
bf805f20 8b 45 d8 89 45 ec 8b 45 dc 89 45 *00 53 8d 45 f4 .E..E..E..E.S.E.
bf805f30 50 8d 45 ec 50 8d 4d fc e8 99 e6 *48 00 e9 70 fe P.E.P.M....H..p.
bf805f40 ff ff 8d 4d f4 e8 c9 fb ff ff 8b *00 d8 89 45 e8 ...M..........E.
bf805f50 8b 45 dc 89 45 ec 8b 45 e0 33 ff *48 7d f4 89 45 .E..E..E.3.H}..E
bf805f60 e4 74 2a 53 8d 45 ec 50 8d 45 e8 *00 8d 4d f4 e8 .t*S.E.P.E...M..
bf805f70 62 e6 00 00 85 c0 74 15 53 8d 45 *48 50 8d 45 f4 b.....t.S.EHP.E.

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
STACK_COMMAND: .trap ffffffffb8603b4c ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE