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

KtElwood

New member
Local time
12:36 PM
Messages
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" :eek:, 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 My Computer

At a glance

Win 7 Pro 64Xeon 1230 v32x4GB Corsair Value Select 2x2 GB Kingston Hy...ASUS GTX670 Mini
Computer type
PC/Desktop
Computer Manufacturer/Model Number
UNKNOWN
OS
Win 7 Pro 64
CPU
Xeon 1230 v3
Motherboard
GA H87 D3H @F10
Memory
2x4GB Corsair Value Select 2x2 GB Kingston Hyper X
Graphics Card(s)
ASUS GTX670 Mini
Hard Drives
WD-BLUE-1TB
'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 My Computer

At a glance

Windows 10 Proi5-650016GB DDR4 2133 Crucial Ballistix Sport LTMSI GeForce GTX 1060 GAMING X 6G
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom build
OS
Windows 10 Pro
CPU
i5-6500
Motherboard
Gigabyte B150-HD3P-CF
Memory
16GB DDR4 2133 Crucial Ballistix Sport LT
Graphics Card(s)
MSI GeForce GTX 1060 GAMING X 6G
Sound Card
Intel Display Audio
Monitor(s) Displays
Liyama ProLite XB2483HSU-B2
Screen Resolution
1920 x 1080
Hard Drives
Crucial MX200 500GB & Toshiba DT01ACA300 3TB
PSU
Corsair RM550x
Case
Fractal Design Define S
Cooling
Cooler Master TX3 i
Keyboard
Func KB-460 (MX Red)
Mouse
Corsair Gaming M65 RGB
Antivirus
Bitdefender Total Security 2016 + MBAM Pro + MBAE Pro
Browser
Google Chrome
Other Info
Creative Sound Blaster Tactic3D Rage V2 headset
Back
Top