Understanding the BSOD : How does "Caused by Adress" help me ?


  1. Posts : 1
    Win 7 Pro 64
       #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
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    'Probably caused by' displays the last driver from the call stack that is not from the Windows kernel. If there is none, it defaults to either of the kernel driver, often ntoskrnl.exe.
    Under no circumstances is a Windows kernel driver ever the cause. If it would be you would have a lot more problems than 'just' BSODs.

    The BSOD parameters and probably caused by line could push you into the right direction, but it is up to you to work with it.


    "+6f980" is the offset of the driver. Like fffff880`033b66f0 + 6f980 = fffff880`03426070, the position of the driver's start point.
    Code:
    3: kd> ? fffff880`033b66f0 + 6f980
    Evaluate expression: -8246282526608 = fffff880`03426070
    Can I determine a Hardwareressource, a device or a driver by the Adresses that "bluescreenview" tells me ?
    No to hardware,
    Yes to device and driver, a driver controls a device.


    may the force be with you
    What force?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:36.
Find Us