New
#1
Understanding the BSOD : How does "Caused by Adress" help me ?
Hello,
this topic may not be appropriate to this section, but I really don't know where to better but it..
My system is haunting me with erratic instability, but I can not put the finger on a faulty component or a faulty driver. (merry go round of (mem)testing with diffrent RAM, PSUs, Drivers, GPUs, Mainboards, CPU...)
Before the latest re-install if Windows nVidia Driver crashed and was restored, killing my working progress in CAD or even just firefox.
Now nvlddmkm.sys SEEMS to be happy (according to verifier), and instead of "driver has been restored" I get straight BSODs.
Some of them I understand (enabled "hands free EHCI" gets me "USBPORT.SYS" BUGCODE_USB_DRIVER, Disable makes it disapear)
TL;DR:
Question:
What keeps popping in "Bluescreenviewer" is "ntoskrnl.exe" and "Caused by Address" "ntoskrnl.exe+6f980"
Since I cant seem to get rid of "ntoskrnl" , and there is no other plain-Text output in the dumps (I can see with bluescreenvwr or the eventvwr..)
-> What does "Caused by Adress" mean ? <-
Can I determine a Hardwareressource, a device or a driver by the Adresses that "bluescreenview" tells me ?
Is it just an adresss/Object/function within the memory used up by the "ntoskrnl.exe" ?
If this aint helpin Can I get the faulty *WHATEVER* now from the BSOD parameters
At the moment this seems to be the only consistent Information of any crash.
I know it would be easier to post a dump. BUT THIS IS MY WHITE WHALE ! and also your dmpcollection.exe crashes...to BSOD.
answers appreciated
may the force be with you
Elwood