![]() |
|
#1
|
||||
|
||||
|
code: 0*0000008e(0*c0000005, 0*8055a340, 0*b8503c38, 0*00000000)
os: xp product: eav latest version someone said this issue can be done by deleting ehdrv.sys. I've never tried. but why the blue screen occur?
__________________
I'll come for u ,ess5.0 . |
|
#2
|
||||
|
||||
|
Collect a memory dump. I do not know who to submit the dump file to, though.
You may also attempt a Clean Boot State in order to troubleshoot the culprit to selectively itemise the item that may be causing your issue. When Marcos sees this thread he will advise where to submit the dump file. Regards,
__________________
siljaline MS MVP Alum . MVPS HOSTS . Rename Hosts . ESET for Business . 10 Immutable Laws of Security . System Lookup . ESET Threat Blog . MBAM Last edited by siljaline : April 3rd, 2010 at 12:31 AM. Reason: adding additional information |
|
#3
|
|||
|
|||
|
All memory dumps from BSOD we've got so far were caused by an outdated 3rd party driver or a badly written driver that caused BSOD in conjunction with the ESET self-defense driver. In order for us to tell if it's the same problem and to figure out which driver is the problematic one, we'll need to get a kernel or better complete memory dump from BSOD for perusal as mentioned above.
|
|
#4
|
||||
|
||||
|
thanks guys
__________________
I'll come for u ,ess5.0 . |
|
#5
|
||||
|
||||
|
Glad to help
Regards, Quote:
__________________
siljaline MS MVP Alum . MVPS HOSTS . Rename Hosts . ESET for Business . 10 Immutable Laws of Security . System Lookup . ESET Threat Blog . MBAM |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|