[SOLVED] Random BSOD: crash address ntoskrnl.exe+175510?

[gotdurt]

Howdy, I recently started having a BSOD issue with an old Dell Optiplex 755 running Win 10; stop code "critical structure corruption".

The crashes are seemingly random, happening anywhere from a couple a day to once a week, and seem to be when the system is idle (only one has happened while I was actually using the machine). I haven't made any changes in recent history.

I ran the Windows memory diagnostic (passed), updated graphics driver (had issues in the distant past), and checked the dump file with Blue Screen View:

File: 011719-23531-01.dmp
Crash Time: 1/17/2019 10:13:34 AM
Bug Check Code: 0x00000109
P1: a3a01e63`75af8541
P2: 00000000`00000000
P3: 3cb0c7f4`c7823b92
P4: 00000000`00000101
Caused by Driver: ntoskrnl.exe
Caused by Address: ntoskrnl.exe+175510
Processor: x64
Crash Address: ntoskrnl.exe+175510
Path: C:\WINDOWS\Minidump\011719-23531-01.dmp
Processors: 2
Major Version: 15
Minor Version: 16299
File Size: 274,828
File Time: 1/17/2019 10:17:16 AM

Thoughts?

 

[Colif]

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

You are on an old version of win 10, could think about upgrading.

see if this helps:
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

Go to c windows/minidump
copy that minidump file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read

 

[gotdurt]

Nevermind, got it working... I think... scan doesn't appear to be doing anything so I'll give it some time.

 

[gotdurt]

SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

Ran both and didn't find anything, restarted anyway.

Go to c windows/minidump
copy that minidump file to documents

The minidump folder is empty.

 

[Colif]

idle is when PC is running background tasks that help it keep PC working.
did you have the view set to show hidden files and folders when you look in minidump? i think they normally show without it on but maybe help

when PC only has XP and VIsta drivers to choose from, it could be any driver. try running this and see if it makes a dump file

Before running this,
1) search for “Create a restore point” and create a restore point
2) Create a bootable USB of Win 10 installer to use as a boot drive. download the Windows 10 media creation tool and use it to make a win 10 installer on USB
In case no one looks at this for a while, you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.
Once it bsod, upload the minidump file and we see what it shows us.

Steps 1 & 2 are just precautions as sometimes driver verifer can put you in a boot loop. If this happen, follow these steps to get out of it
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore and roll system back to restore point created in step 1. PC should boot normally.

 

[gotdurt]

idle is when PC is running background tasks that help it keep PC working.
did you have the view set to show hidden files and folders when you look in minidump? i think they normally show without it on but maybe help

Yes, hidden files are shown. However, it crashed a few times within an hour this morning (the first time it has done this), and it made new dump files in the minidump folder:
https://www.dropbox.com/sh/o6nnj3co0bqeqcn/AAAVW1gcaT7tJsL8qQSuWUxAa?dl=0

Meanwhile, I'll go ahead and run the driver verifier and see if it reveals anything.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/rL1M.html

File: 011919-23437-01.dmp (Jan 19 2019 - 10:52:12)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: Unknown_Image (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 16 Min(s), and 53 Sec(s)

File: 011919-23234-01.dmp (Jan 19 2019 - 02:53:12)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: Unknown_Image (Process: System)
Uptime: 0 Day(s), 13 Hour(s), 13 Min(s), and 48 Sec(s)

File: 011919-22937-01.dmp (Jan 19 2019 - 10:23:58)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: Unknown_Image (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 17 Min(s), and 07 Sec(s)

I'm not sure how helpful these dumps will be, all 3 dumps proved "inconclusive".

BIOS information was not included in the dump file. This can sometimes mean an outdated BIOS is being used.

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Colif]

Critical Structure Corruption appears it can be a memory error.

Try running memtesst86 on each of your ram sticks, one stick at a time, up to 8 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

just to make sure Windows Memory diagnostics is right

Try checking hdd - open command prompt (Admin)
type chkdsk c: /f /r and press enter
2 paragraphs will pop up, type Y and press enter to agree to running at startup
restart PC and let it run check.

try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

 

[gotdurt]

It may be too late, it's progressing quickly. I've been stuck on trying to create a Win 10 installer USB, but it keeps crashing in the middle of the process.

Something I have noticed though, is that my KVM switch (Iogear gcs632u) seems to have been kind of buggy on the side of this machine, and these bugs have also been getting progressively worse. I did some research on it, and supposedly there aren't any drivers for it. I'll see if I can dig up another mouse and keyboard ad test without it.

 

[gotdurt]

Checked for new dump files, added to the link above. One of them appears to be USB port related, which might explain the KVM trouble?

 

[gardenman]

I ran the new dump files through the debugger and got the following information: https://pste.eu/p/A1ku.html

Spoiler

File: 012019-23984-01.dmp (Jan 20 2019 - 10:57:05)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: Unknown_Image (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 12 Min(s), and 43 Sec(s)

File: 012019-23203-01.dmp (Jan 20 2019 - 10:42:47)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: Unknown_Image (Process: https://www.google.com/search?q=)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 00 Sec(s)

File: 012019-23000-01.dmp (Jan 20 2019 - 00:43:19)
BugCheck: [DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 02 Min(s), and 15 Sec(s)

File: 011919-24406-01.dmp (Jan 19 2019 - 23:23:45)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: Unknown_Image (Process: csrss.exe)
Uptime: 0 Day(s), 0 Hour(s), 46 Min(s), and 09 Sec(s)

File: 011919-23703-01.dmp (Jan 19 2019 - 21:06:34)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: Unknown_Image (Process: System)
Uptime: 0 Day(s), 3 Hour(s), 14 Min(s), and 10 Sec(s)

File: 011919-23640-01.dmp (Jan 19 2019 - 17:51:28)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: Unknown_Image (Process: csrss.exe)
Uptime: 0 Day(s), 1 Hour(s), 24 Min(s), and 21 Sec(s)

File: 011919-23421-01.dmp (Jan 19 2019 - 13:24:00)
BugCheck: [CRITICAL_STRUCTURE_CORRUPTION (109)]
Probably caused by: Unknown_Image (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 35 Min(s), and 10 Sec(s)

This driver didn't show up last time:
Sep 26 2011 - e1e6032e.sys - Intel(R) PRO/1000 Adapter NDIS 6 Deserialized driver

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Colif]

Try making the installer on a working PC?

USB drivers are built into windows 10 so its possible that if you run driver verifer, it might identify the cause for us.

csrss.exe = the client service which is what your user runs on. Windows cannot run without it.

test your ram and hdd, as if it is blaming something different each time it can mean its physical corruption that is the cause.

This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.

 

[gotdurt]

I was waiting until I had an installer ready before running the driver verifier. I'll go ahead and run it anyway, I'll worry about the installer if there's a problem; I can download from my other machine overnight, if needed (I need it for work during the day, especially since I'm down to one machine).

I tried testing the HDD several times yesterday, it would not get past 10%, and when I let it run overnight, I came back to a blue screen anyway.

Tested the processor, it passed everything except the brand string (had to skip to run the rest) and SPBC module.

Will do driver verifier and RAM today.

 

[gotdurt]

Well, that figures. I spent what little free time I had yesterday backing up my C drive between crashes, and ran the driver verifier this morning... 8 hours later, it still hasn't crashed. Hopefully it'll crash soon and I'll have something to report.

 

[gotdurt]

So it never crashed, but when I came in this morning, the left monitor was off and none of the USB ports worked... at first I thought it was the KVM switch, but when I tried to plug-in a wired mouse to shut it down, I couldn't find a live USB port... not sure what that would have to do with the left monitor though.

I restarted the verifier, trying again.

 

[Colif]

Something I have noticed though, is that my KVM switch (Iogear gcs632u) seems to have been kind of buggy on the side of this machine, and these bugs have also been getting progressively worse. I did some research on it, and supposedly there aren't any drivers for it. I'll see if I can dig up another mouse and keyboard ad test without it.

Have you tested without kvm yet?

what is wrong with left monitor? i looked through thread and didn't see you mention it before?

It is a strange problem, If DV doesn't crash its pointing us at a hardware problem again

Try removing superantispyware as its from 2011 and way too old for windows 10. It may not be cause but can cause problems,

 

[gotdurt]

Have you tested without kvm yet?

I didn't... once I discovered that all of the USB ports were dead (not just the keyboard and mouse, which is what had me considering the KVM), I backed off that theory temporarily, plus it would require taking my other work machine offline in order to test it (I'm still trying to conduct business through all of this).

what is wrong with left monitor? i looked through thread and didn't see you mention it before?

Nothing, that was the first time I had an issue with it. That kind of leads me back to the KVM, or maybe the graphics card... but not sure why either of those would cause problems with all USB ports at once.

It is a strange problem, If DV doesn't crash its pointing us at a hardware problem again

Yes, and unfortunately, it has set me back enough with work that I went ahead and replaced the machine... I'm still using the same KVM and graphics card, and have been working on setting up Windows, software, etc. since yesterday, and so far no problems. If I start having the same issues, I know where the problem lies...

I've had quite a few other PCs during the time that I've been using this one, and until now it has by far been my most stable, dependable machine, so think after 12 years, it is time to retire it, at least from work duty. Thanks for your time and help, Colif.

 

[Colif]

replacing PC is one fix but not everyone can afford it. Good luck in future

 

[gotdurt]

It's just a newer Dell Optiplex 990 that I bought used for $100; much cheaper than the time I was losing from the computer being down.
I did, however, rule out the KVM or Graphics card; I had to set the old machine back up temporarily because I forgot to save some CAD profiles... I did so without those components, and it crashed twice .