Bsod... Help Me!

Hi everyone, i'm noob of this forum...
is from a few day that sometimes i see the damn BSOD with strange error code and no connections with file or driver... can you help me? This is one fo that...
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 10/06/2005
Time: 23.48.38
User: N/A
Computer: ASGHARD
Description:
Error code 1000008e, parameter1 c0000005, parameter2 805745be, parameter3 f1837c08, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 38 30 35 37 34 35 62 65 805745be
0040: 2c 20 66 31 38 33 37 63 , f1837c
0048: 30 38 2c 20 30 30 30 30 08, 0000
0050: 30 30 30 30 0000
Help me pls! :hotbounce

It fails at ntoskrnl and that is why you don't see the module name at the blue screen. Zip 4 to 6 minidumps and attach the zip files here. You can find the minidumps at the folder \windows\minidump

I've zipped the minidump in 3 zip files....
I take only the dump file from aprile... i hope that is sufficient...

minidump 2

minidump 3...
I hope that this can help

Herian,

After analysis, after you upgrade XP to latest patch and upgrade nVidia Displayer Driver, your XP encountered a lot of BSOD. Your problem have multiple culprits. The first culprit is RAM and the second culprit is nVidia Displayer Driver.

Suggestion
1. Install nVidia Display Card Driver 61.77
http://www.nvidia.com/object/winxp_2k_61.77.html
2, I would expect your XP will crash less frequently. If you still cannot accept, replace the RAM.


Your XP encounter bugcheck D1 at IRQL 7 which is usually caused by hardware problem (ie usually is faulty RAM) and failing module is hal (hardware abstraction layer)
Mini060905-01.dmp BugCheck 100000D1, {0, 7, 1, f6bcc777}

Mini061005-02.dmp Bugcheck 1000008E, {c0000005, bfb6b898, f152e9c4, 0}
Probably caused by : nv4_disp.dll ( nv4_disp+198898 )

Thanks a lot guy :)
The last bsod happen yesterday when i try to update my audigy2 driver... start installation and zap... bsod!

To check ram i can use memtest86?

I forget to say that two days ago i unistall the nvidia drivers and reinstall it, and i haven't seen any BSOD related to nvidia drivers. But if you say that it is the problem i trust you :)

Now i check the ram with memtest86+ and we see what happens...
thanks again

I've tested ram with memtest86 for 3 hours and no problems... any idea or suggestion? Only change nvidia drivers?

P.s. I've setted the bios default settings, not OC

possibility of bad video ram on card itself.

How can i test it?

only way I know is try the card in another computer.

This way is not possible 'cause the bsod appear rarely, sometimes 1 every 2 days... There's no an event that make my monitor blue :cool:

Herian,

Do you have any update of your problem?

Thanks a lot to all of you, i solved the problem with the magical word... FORMAT :haha:
No hardware problem it seems... three weeks since format and noone problem... eccept this one
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 02/07/2005
Time: 0.32.22
User: NT AUTHORITY\SYSTEM
Computer: ASHARD
Description:
Windows saved user ASHARD\Herian registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This warning appear every time a shut down the pc... i think 'cause i've chosen to close automaticatilly the hung programs at the shut down... is it possible?

Hi Herian,

Excellent. Your problem is resolved. As you know windows crashes maybe relarted hardware or software error.

I've summaries all the analysis report of all your dumps. Your version of nVidia and Zone Alarm has BSOD record. This is the first time I find IRQL 7 crashes with BSOD. In addition TCPIP is a stable module and it is unlikley to crash unless it is software. Maybe the caller passes invalid parameter to TCPIP and crash windows. This is reason I think it is hardware record. I will be aware if similar problem occurs, it may be software problem.

You installed too many software which are high risk software. From your minidump you installed Zone Alarm, Symantec AV and nVidia Display Driver. They are almost the latest version, it may cause a lot of unknown problem. According to experience, those software developer do not well test their software before they release the software patches. Especially ZoneAlarm has a lot of problem.

Maybe you upgrade ZoneAlarm and nVidia Display card driver to the latest version when you re-install windows. You may encounter upgrade ZoneAlarm later when you upgrade ZoneAlarm. Do not assume the latest software resolve the problem as new version of softtware may be incompatible with other software. As the software developer may not test all the different software combination at their lab. You need a stable Windows. If you feel your windows is stable, turn off the auto update.

The following posts are problem relating to a ZoneAlarm. There have a one post in this forum, de-install ZoneAlarm resolve his BSOD problem.
http://www.techspot.com/vb/topic16994-pg9.html&pp=20
http://www.techspot.com/vb/topic17691-pg14.html&pp=20

Mini042305-01.dmp 50 (ed56e80e, 00000001, bf806c2c, 00000000) win32k!DC::vReleaseVis+0x31
Mini052605-01.dmp 50 (e494d000, 00000000, bfa57d70, 10000000) nv4_disp+84d70 TIMESTAMP: 424ddded
Mini050305-01.dmp D1 (45850fdc, 00000002, 00000001, ebc0e677) tcpip!IPRcvComplete+2d1 (access low memory)
Mini060605-01.dmp 8E (c0000005, bfa7e2bb, f14aea18, 00000000) nv4_disp+ab2bb TIMESTAMP: 424ddded
Mini060705-01.dmp 50 (e47e6000, 00000000, bfa57d70, 00000001) nv4_disp+84d70 TIMESTAMP: 424ddded
Mini060805-01.dmp 0A (f34ecfef, 000000ff, 00000001, 8053e41c) nt!KiTrap07+b0
Mini061005-01.dmp 0A (00000000, 00000002, 00000001, 804f9982) nt!KeWaitForSingleObject+0x186
Mini060905-01.dmp D1 (00000000, 00000007, 00000001, f6bcc777) ha10kx2k+44777
Mini060905-02.dmp D1 (00000001, 00000002, 00000000, f4988bf7) vsdatant+2e621 TIMESTAMP: 42657a33
Mini061005-02.dmp 8E (c0000005, bfb6b898, f152e9c4, 00000000) nv4_disp+198898 TIMESTAMP: 424ddded
Mini061005-03.dmp 8E (c0000005, 805745be, f1837c08, 00000000) nt!IopXxxControlFile+1dc
Mini061105-01.dmp 8E (c0000005, 805745be, f1418c08, 00000000) nt!IopXxxControlFile+1dc

No hardware problem it seems... three weeks since format and noone problem... eccept this one

Event ID: 1517



Are you running Microsoft Antispyware? If so that is your cause of Event ID:1517. (I just spent about 3 hours tracking that down today.) :D

Hi Herian,

Recently I find a lot of BSODs at Techspot are relating to ZoneAlarm (ie Wed Apr 20 05:37:55 2005). Can you tell me what version of ZoneAlarm are you using now? Your feeback will help us to resolve similar problem.