Click here to Skip to main content
14,360,787 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
 
GeneralRe: I have this suspicion Pin
honey the codewitch14-Sep-19 10:06
memberhoney the codewitch14-Sep-19 10:06 
GeneralRe: I have this suspicion Pin
Sander Rossel14-Sep-19 10:14
professionalSander Rossel14-Sep-19 10:14 
GeneralRe: I have this suspicion Pin
honey the codewitch14-Sep-19 10:10
memberhoney the codewitch14-Sep-19 10:10 
GeneralRe: I have this suspicion Pin
Sander Rossel14-Sep-19 10:14
professionalSander Rossel14-Sep-19 10:14 
GeneralRe: I have this suspicion Pin
Norman Landing14-Sep-19 9:53
memberNorman Landing14-Sep-19 9:53 
GeneralRe: I have this suspicion Pin
honey the codewitch14-Sep-19 10:07
memberhoney the codewitch14-Sep-19 10:07 
GeneralRe: I have this suspicion Pin
BillWoodruff14-Sep-19 22:36
mveBillWoodruff14-Sep-19 22:36 
GeneralWin10 woes: The Never-ending Story Pin
raddevus14-Sep-19 5:28
mvaraddevus14-Sep-19 5:28 
I can't tell if it is my new hardware ( Original post in lounge with H/W list[^] ) or Win10.

I wiped the machine completely and reinstalled Win10. Now, it is no longer the graphics card faulting but something else. Previously, ever single error pointed to a graphics card problem. That is no longer true from the Memory.dmp to the app crashes I've seen. Also, there are far fewer crashes now.

Whatever it is, FireFox is the most consistent on crashing from the problem. That's exciting, isn't it? Roll eyes | :rolleyes:

Yet Another Attempt (YAA) At Fixing Win 10
I ran the steps at : https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system[^]

Check out the results. I cannot tell if it did do something and should expect it to be fixed or not.
https://i.stack.imgur.com/k55Nz.png[^]
I guess I should just be blindly optimistic now.

I've definitely gone thru the Stages of Grief with my new computer.
Denial - No, this isn't happening. It's a brand new computer with a activated win10 installation! Unsure | :~
Anger - This cannot be happening!! It's a brand new computer with activated win10 installation!!!!! Mad | :mad:
Bargaining - Don't let this happen. Let the computer work.... Sigh | :sigh:
Guilt - This is happening because I bought the wrong hardware, right?Confused | :confused:
Sorrow - Computers don't really work. It's all just a trick to make you think technology works. It doesn't matter anyways. I'll just take up knitting. Cry | :((
Acceptance - It's fine. I understand that I may or may not be able to use my computer. All computing is unreliable and untrustworthy. I'm going outside. Roll eyes | :rolleyes:

EDIT
A few moments after I posted, bot a BSOD and when I ran WinDgb I saw this.
These are totally different errors from what I saw before the windows refresh.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: ffff09fb3a1bacca, Actual security check cookie from the stack
Arg2: 0000f1f82e75fcaa, Expected security check cookie
Arg3: ffff0e07d18a0355, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

Debugging Details:
------------------

KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-6CFRJ0I
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 7

Key : Analysis.Memory.CommitPeak.Mb
Value: 64

Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: f7
BUGCHECK_P1: ffff09fb3a1bacca
BUGCHECK_P2: f1f82e75fcaa
BUGCHECK_P3: ffff0e07d18a0355
BUGCHECK_P4: 0
SECURITY_COOKIE: Expected 0000f1f82e75fcaa found ffff09fb3a1bacca
PROCESS_NAME: System
STACK_TEXT:
fffff803`146e5018 fffff803`1fa495d7 : 00000000`000000f7 ffff09fb`3a1bacca 0000f1f8`2e75fcaa ffff0e07`d18a0355 : nt!KeBugCheckEx
fffff803`146e5020 fffff803`2003a199 : 00000000`00010000 00000000`00000000 00010000`00000000 00000000`00000000 : nvlddmkm+0x1095d7
fffff803`146e5060 fffff803`2003b3ce : fffff803`146e5360 00000000`04380780 00000000`04380780 fffff803`146e5360 : nvlddmkm+0x6fa199
fffff803`146e50e0 fffff803`2003613f : 00000000`04380780 00000000`00000007 fffff803`146e5270 ffffb58f`5bcb5000 : nvlddmkm+0x6fb3ce
fffff803`146e5150 fffff803`20048305 : 00000000`00000000 ffffb58f`597c1000 ffffb58f`2e0d0000 fffff803`146e55f0 : nvlddmkm+0x6f613f
fffff803`146e54d0 fffff803`2006b732 : ffffb58f`5be72900 fffff803`146e6a88 ffffb58f`597c1000 ffff09fb`3a1ba54a : nvlddmkm+0x708305
fffff803`146e5a10 fffff803`2006c704 : fffff803`146e6a00 fffff803`00000000 ffffb58f`5be729e0 ffffb58f`597c1000 : nvlddmkm+0x72b732
fffff803`146e5b00 fffff803`2006c44f : ffffb58f`597c1000 00000000`00000000 ffffb58f`597c1000 00000000`00000000 : nvlddmkm+0x72c704
fffff803`146e5c10 fffff803`2007056d : ffffb58f`59822000 fffff803`146e5da0 ffffb58f`59822000 fffff803`146e5da0 : nvlddmkm+0x72c44f
fffff803`146e5ca0 fffff803`1bc3a083 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x73056d
fffff803`146e65b0 fffff803`1bc3da69 : ffffb58f`5b162a80 00004a70`a4e9d900 fffff803`146e6a80 fffff803`1e830b56 : dxgkrnl!ADAPTER_DISPLAY::DdiSetVidPnSourceAddressWithMultiPlaneOverlay3+0x203
fffff803`146e6670 fffff803`1e82aa7e : ffffffff`ffffffb5 fffff803`0e9c230b 00000000`ffffffff 00000000`00000000 : dxgkrnl!ADAPTER_DISPLAY_DdiSetVidPnSourceAddressWithMultiPlaneOverlay3+0x9
fffff803`146e66a0 fffff803`0e9c22f8 : ffffb58f`59c3a000 ffffb58f`5be97000 ffffb58f`5b1626a0
...
SYMBOL_NAME: nvlddmkm+1095d7
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1095d7
FAILURE_BUCKET_ID: 0xF7_MISSING_GSFRAME_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2ffeac14-357b-96a5-98b2-2e606f12e8c0}
Followup: MachineOwner

modified 14-Sep-19 10:51am.

GeneralRe: Win10 woes: The Never-ending Story Pin
Randor 14-Sep-19 5:59
professional Randor 14-Sep-19 5:59 
GeneralRe: Win10 woes: The Never-ending Story Pin
lopatir14-Sep-19 6:13
memberlopatir14-Sep-19 6:13 
GeneralRe: Win10 woes: The Never-ending Story Pin
raddevus14-Sep-19 7:30
mvaraddevus14-Sep-19 7:30 
GeneralRe: Win10 woes: The Never-ending Story Pin
Slacker00714-Sep-19 6:38
professionalSlacker00714-Sep-19 6:38 
GeneralRe: Win10 woes: The Never-ending Story Pin
raddevus14-Sep-19 7:51
mvaraddevus14-Sep-19 7:51 
GeneralRe: Win10 woes: The Never-ending Story Pin
BillWoodruff14-Sep-19 22:57
mveBillWoodruff14-Sep-19 22:57 
Generalfor those of you purists that don't like break, continue and goto Pin
honey the codewitch14-Sep-19 4:51
memberhoney the codewitch14-Sep-19 4:51 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
Jörgen Andersson14-Sep-19 5:07
protectorJörgen Andersson14-Sep-19 5:07 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
honey the codewitch14-Sep-19 5:08
memberhoney the codewitch14-Sep-19 5:08 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
Jörgen Andersson14-Sep-19 5:12
protectorJörgen Andersson14-Sep-19 5:12 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
honey the codewitch14-Sep-19 5:16
memberhoney the codewitch14-Sep-19 5:16 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
Jörgen Andersson14-Sep-19 5:18
protectorJörgen Andersson14-Sep-19 5:18 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
honey the codewitch14-Sep-19 5:22
memberhoney the codewitch14-Sep-19 5:22 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
Jörgen Andersson14-Sep-19 5:49
protectorJörgen Andersson14-Sep-19 5:49 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
honey the codewitch14-Sep-19 6:01
memberhoney the codewitch14-Sep-19 6:01 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
OriginalGriff14-Sep-19 5:07
protectorOriginalGriff14-Sep-19 5:07 
GeneralRe: for those of you purists that don't like break, continue and goto Pin
honey the codewitch14-Sep-19 5:09
memberhoney the codewitch14-Sep-19 5:09 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.