BSOD twice while normally using laptop

cay you post it following the Blue Screen of Death (BSOD) Posting Instructions?

=====
@arc so... technically i dont have BSOD anymore now as i said on the previous post that i did clean install with a new SSD.

sorry if i was all over the place.

Let me tell you the history of me using this notebook. Every couple of months i get BSOD. When i get BSOD i just clean install my windows. the first 2-3 months was okay, but then the 4th months i got BSOD, its always the same eror, IRQL less or equal. I was forced to clean install windows every couple of months to avoid this BSOD, rinse wash repeat.

Koolkat solved that, that apparently it was due to my atheros driver.

I dont wanna go through it again so now that im on a new clean install notebook, i'd like to learn where does koolkat and you and the BSOD team can read that error that koolkat was quoting.

is it from the dmp file from the dump folder generated by the SF diagnostic tool?

i'd like to learn how to read that before moving forward with updating my windows and installing programs.

===
The reason i want to learn is beacuse I'm confused as to how come the atheros wireless driver has leftover since i installed the wireless driver from the CD stock driver. and then I updated that through asus live-update utility (as suggested by the notebook manual). I did not get creative with anything at all.
===

so now.. (before the BSOD ever happen again), i'm on a fresh new installed notebook and hvnt update my windows or install many programs now. i'd like to know before i do those things how check whether i have (yet another) atheros driver leftover again or not..

may i ask how to do that? i wanted to know which file on the dump folder generated by SF Diag tool should i read to found that problem koolkat was quoting (or hopefully not found, since its a new machine).

i followed the tutorial here Configuring the "Debugging Tools"

but when i typed cd debuggers on the command prompt it returned "the system cannot find the path specified", even though i followed the instruction verbatim including installing debbugger package on c:\debuggers

did i downloaded the incorrect debugging tools or smthn from this link? Download and Install Debugging Tools for Windows
i chose this one Download the Microsoft Windows SDK for Windows 7 and checked everything when i downloaded it.
i havent download this one Download Windows Symbol Packages
Do i have to download the windows symbol packages as well? and did i chose the wrong download link?

i use this tutorial Configuring the "Debugging Tools" but i got stucked here C:\>cd debuggers
C:\debuggers>windbg.exe -IA

System not recognized internal or external command etc etc was what i got


again, truly sorry for the inconvenience and being all over the place


basically i just would like to know where on the dump folders did koolkat got this quote

Code:

fffff880`0a6515e8 fffff880`05d88c7eUnable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
athrx+0x104c7e

Code:

lmvm athrx
start end module name
fffff880`05c84000 fffff880`05f2e000 athrx T (no symbols)
Loaded symbol image file: athrx.sys
Image path: \SystemRoot\system32\DRIVERS\athrx.sys
Image name: athrx.sys
Timestamp: Tue Oct 04 12:49:29 2011 (4E8AAC79)
CheckSum: 002B1FA7
ImageSize: 002AA000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

terribly apologize for being really all over the place @arc and @koolkat77

cheers,

KP

@arc if my post is too long and confusing, let me know i have edited it just now to make it more readable. Let me know if you still need the dump file from my fresh new SSD install notebook

cheers,

KP~!

Other than the dump file, how can you test the timestrap of the atheros driver?

After a clean install, there will be no leftover as the drive/partition is formatted.

Arc said:

Other than the dump file, how can you test the timestrap of the atheros driver?

After a clean install, there will be no leftover as the drive/partition is formatted.

i think when you read my comment the 1st time, i havent finish editing it and it was still alll over the place so you didnt get my question, so im sorry for that.

terribly sorry for not being clear.

that is exactly what im asking, how to read the dmp file? on the folder generated by the SF diag tool there are txt files and dmp files. i assumed the error koolkat was quoting, koolkat found on the dmp file? is it?

i've followed the tutorial to learn how to read dmp file myself, but i got stuck while doing it. which is what i posted earlier. really sorry if its not clear. I've just recently edited my post actually to make it more concise for you to read.

the second part of your answer about the timestamp, i got it from koolkat quote

fffff880`0a6515e8 fffff880`05d88c7eUnable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athrx.sys *** ERROR: Module load completed but symbols could not be loaded for athrx.sys athrx+0x104c7e

so i wanna know whether i have that error again on my fresh new machine or not

about this part of your reply " After a clean install, there will be no leftover as the drive/partition is formatted."

i wrote above...

Let me tell you the history of me using this notebook. Every couple of months i get BSOD. When i get BSOD i just clean install my windows. the first 2-3 months was okay, but then the 4th months i got BSOD, its always the same eror, IRQL less or equal. I was forced to clean install windows every couple of months to avoid this BSOD, rinse wash repeat.

Koolkat solved that, that apparently it was due to my atheros driver. My confusion was because ive installed the driver from the driver CD and i updated the driver the way asus manual told me to updated it. thru live update utility.

but every few months, i got the same BSOD. I dont wanna go through it again so now that im on a new clean install notebook, i'd like to learn where does koolkat and you and the BSOD team can read that error that koolkat was quoting.

is it from the dmp file from the dump folder generated by the SF diagnostic tool?

so basically every couple of months after using the notebook, i got BSOD, then i do clean install, rinse wash repeat. now i just installed SSD and im really tired of having clean install every few months due to that atheros timestamp driver koolkat found.


how can i read dmp file myself of my new notebook install is my question actually. and where did koolkat and you can find the problem i have? is it from the txt files or from the dmp files on that folder?


cheers,

KP!

Yes, the quoted part is form your dump file.

An IRQL Less or not Equal bsod may be saused by any driver, not necessarily the Atheros one.
At the same time, all the so called driver updating utilities are kinda craps. Moreover, ASUS bundled "utilities" are all craps. They never help you, but cause problems and conflicts. We avoid those, we suggest to avoid those. Hopefully this time there will be no more crashes caused by Atheros, specially in the absence of Kaspersky.

Reading a dump data properly needs a time and patience to learn. I guess you have got your windbg installed and configured? Now, follow it: Debugging A BSOD - My way

For practice, take any random dump from any of the threads and proceed. Compare your reading with the other peoples readings. Gradually you will get it.

Answer to your first question: If you execute the setup.exe, it will automatically update the existing driver.

Ansewr to the second question: Installation procedure depends on the format of driver file. If it is .exe one, just double click it. But if it is a .sys, follow Driver Install - Device Manager

And, it does not matter what pattern of windbg you are getting ... a part of SDK or a part of WDK. you will install the debugger tool only, so the package does not matter.

Before associating the dump files with windbg, what you have to do in the elivated command prompt, you have to stay on the proper root. I replied you in the other thread.

Even if the dumps are not associated with windbg, you can open windbg, then File > Open Crash Dump and browse to the dump and open it. The result will be the same.

It will not appear at itself. You need to dig the data to a depth to get it and for that you need a great lot of practice and time to devote on the program.