blue screen of death, can you help me to understand?

Hi

few seconds ago i got a bsod w7 64bit ultimate

i used BlueScreenView.exe

i got

i upload the minidump

 

I've seen that "IRQL_NOT_LESS_OR_EQUAL" 2-3 times over a year. Seems to be a temporary issue every time.

I'd generally not worry about BSODs unless they occur repeatedly at startup, which means disk imaging to the rescue.

 

The error is caused by a driver attempting to access memory at an invalid location.
It is usually a symptom of a buggy driver or system service.

Cheers, Nick

 

Full technical explanation:

http://msdn.microsoft.com/en-us/library/ms854226.aspx

Cheers, Nick.

 

thanks

 

but is there a program to read the minidump?

 

You already have blue screen view.

 

Everything you want:
http://www.dedoimedo.com/computers/windows-bsod.html

Mrk

 

yes i have for windows 7 but there is nothing about what did cause the bsod

 

oh thanks
there is a lot!
i'm starting to read , i will need time
have you the microsoft tool to analize my minidump?

 

Windows debugger is free for everyone.
Mrk

 

hi
i guess it's epfwwfp.sys ESET Personal Firewall Driver

i have only eset smart security v5 64bit last built

but is there a safe trusty version ?
i have no other securirty software to avoid such issue

 

Yup. Disconnect your hardware and disable the drivers so you can track down the buggy driver. Then update the driver or install compatible hardware.

 

Windows debugging code is written for geeks. As if most people have the foggiest idea of what caused a Windows crash! If the cause was identified in plain English - that's non-geek to most folks out there - it would be a lot easier to track down and solve Windows problems. Fortunately, with the robustness of modern Windows, BSOD crashes, like kernel panic on Linux and Mac OSX is nowadays rarely seen.

Cheers!

 

But that's what was asked.
How to to debug a kernel panic - with a geek tool.
Otherwise it's a paradox, no?
Mrk

 

Rather than jump thru a million hoops, I'd just ask myself what's the last change to the system, or software, I made right before the BSOD, then just undo or reverse it.

 

Since only an expert can try to figure out what a mini dump readout means, the rest of us lesser mortals have to resort to trial and error to solve a BSOD incident along with plenty of googling on incidents similar to the problem that you're having, since someone else may have already found the solution.

Debugging for non-geeks is a waste of time. Its just easier and faster to use guess work and some old fashioned problem hunting on the Internet to get it resolved quickly.

Of course, the info could be sent to the gods at Microsoft to provide a fix.

 

I don't think the problem is with MS.
My experience shows BSOD = HW problems/heating/third-party drivers.
Never seen an NT kernel panicking. Honest.

The fact it is listed in the OP does not mean that's where the problem originated. Would be interesting to analyze and see the full details.

Mrk

 

This applies to XP, but probably still applies for 7,

http://support.microsoft.com/kb/314063

MS site does have a complete listing for the stop codes, if you are inclined.

Usually bad memory card(s), incorrect/outdated driver and perhaps related to a very recent software installation.

 

you don't have to be an expert to understand the output of debugging tools for windows, i've used it a few times to understand what was causing bluescreens, and i'm no expert. i may not understand all it says, but i follow the most important part.

 

This blue screen decipher is worth a look.
http://www.resplendence.com/whocrashed

 

We're in agreement - Microsoft does provide updates through its Windows Update service so they could be of assistance if the third party hardware maker doesn't step up. The NT kernel is robust and stable and the BSOD is largely beyond Microsoft's control. Badly written hardware drivers are increasingly a thing of the past thanks to Microsoft's hardware certification program. Every piece of equipment designed to work with Windows has to have signed and compatible drivers. That doesn't mean there won't be problems. Just fewer of them for Windows users to encounter on a day to day basis.

 

Hi
seems that the cause was epfwwfp.sys , eset smart security v5 64bit driver

the point is v6 has fixed the problem ?

Ps can a bsod damage hardware or data?

 

You may lose data, if it has not been synced to disk.
HW damage is unlikely, unless there's a bug in the HW driver.
Mrk

 

thanks Mrk
may i ask you what do you mean

and