BSOD daily, KMode Exception, Mem Manage, Crit. structure.

Ryder · Jun 18, 2016

[EDIT part deux... I made a text file of the last 9 minidump files with Bluescreenview... and have attached that instead]

[EDIT: the ZIP file dm_log_collector created... is sadly empty... only just noticed. I restarted my machine, and ran it immediately.... that failed. I downloaded dm_log_collector again. empty ZIP.... again. This seems like a totally bizarre failure. No idea what to do next.]

Hi all,

Win 8.1, in a Digital Storm PC, over 1 year old. Multiple BSOD each day. WhoCrashed reports various Errors:

-KMode Exception not handled
-Memory Management
-Critical Structure Corruption
-Page Fault in Nonpaged Area

No warning, not related to any particular software, however I always have Chrome running. Chrome is also acting up... pages become unresponsive.

I don't overclock.

Core temps are stable ~33% generally, but can get very hot if I abuse the system (prime 95) to the point of failure. I don't know if it's memory or CPU (other?) that dies... but prime 95 can do it... but I am rarely at those temps, and I don't consider them part of my daily multiple BSODs

Should I be suspecting memory?

Thank you for your kind help.

axe0 · Jun 19, 2016

Please upload a new zip, the current one is empty.

Ryder · Jun 19, 2016

Ohfergoodnesssakes..... why would that be? I ran it again.... says it was very busy doing things, and then dumps an empty zip to the desktop every time. I downloaded the collector again.... ran it after restart... still no content in the ZIP. Anyone have any ideas on what to do about this? Is there an older version I might try?

Ryder · Jun 19, 2016

NEW Minidump file....

Hi all... having failed to get the DM Log Collector to function (access was denied to the dmp files...), I used BlueScreenView to write the last 9 dmp files to a text file.... hope that's useful!

axe0 · Jun 19, 2016

I'll need more information than that, please follow below instructions for gathering a few logs

Please search for "msinfo32" (without quotes) and open the msinfo32 app,

save it as msinfo32.nfo,
in explorer go to the directory where it is saved,
right click the msinfo32.nfo file,
choose 'send to' or 'copy to',
choose 'compressed (zipped) folder'

View attachment 67992

Please run following commands in an admin command prompt, it creates a file called 'systeminfo.txt', it is created with the DM Log Collector and shows some information about your system too but we'll have to do it manually now.

Code:

systeminfo > "%USERPROFILE%\Desktop\systeminfo.tmp"findstr /v "Owner." "%USERPROFILE%\Desktop\systeminfo.tmp" > "%USERPROFILE%\Desktop\systeminfo.txt"
del "%USERPROFILE%\Desktop\systeminfo.tmp"

Please search "dxdiag" (without quotes), you'll see a pop-up within a few moments.
In this popup you see the DirectX Diagnostic Tool, click on 'Save All Information' and save it as 'dxdiag.txt'
View attachment 67993

Please go in Windows Explorer to following location for the gathering of the minidumps: %systemroot%\minidump
Select all dumps from the last week, right click 1 of them and choose > send to > compressed (zipped) folder naming it as minidumps.

Now that we have a few files, please upload them all, you may put them all together in 1 zip file if you'd like
You can put them in a zip file by moving them in the same place, select the files > right click 1 of them and choose > send to > compressed (zipped) folder.

To sum up there are a few files gathered
1. msinfo file
2. systeminfo.txt file
3. dxdiag file
4. minidumps

Last thing for now, please run in an admin command prompt following command

Code:

slmgr /dlv

a pop-up will show within a few moments, please make a screenshot of it and post it.

Ryder · Jun 20, 2016

Ok, thanks.... the systeminfo commands did not work... it complained about the /v switch. (invalid argument/option)

axe0 · Jun 20, 2016

It actually does work, but it needs a small work-around
Please copy/paste following code in an admin command prompt, note that there is a enter/space at the end of the code. I added this so you would not have to enter the last command separately from the rest, if however this enter/space doesn't come with the rest then just press enter when the other commands are finished

Code:

del %userprofile%\desktop\systeminfo.txt
md "%userprofile%\Desktop\Systeminfo"
systeminfo > "%USERPROFILE%\Desktop\Systeminfo\systeminfo.tmp"
findstr /v "Owner." "%USERPROFILE%\Desktop\Systeminfo\systeminfo.tmp" > "%USERPROFILE%\Desktop\Systeminfo\systeminfo.txt"
del "%USERPROFILE%\Desktop\Systeminfo\systeminfo.tmp"
move %userprofile%\Desktop\Systeminfo\systeminfo.txt %userprofile%\Desktop
rd %userprofile%\desktop\Systeminfo

Ryder · Jun 20, 2016

That did work.... here's the file

axe0 · Jun 20, 2016

Please do NOT forget the slmgr command, last part of post #5

Ryder · Jun 20, 2016

View attachment 68000 Oh darn... I captured, but forgot to include it... apologies, thank you for your kind help.

axe0 · Jun 20, 2016

Thank you,

According to the logs the last crash was a few weeks ago, is that correct?

Ryder · Jun 20, 2016

The last minidump was two days ago.... so no. That is not correct. The crashes are daily (approx.), and often a few times per day, though it has been slightly over a day since my last crash... note: I have restarted the machine numerous times in the last day... which is not something I normally do).

Also, I should mention..... that not all crashes seem to generate a minidump. The system will not always BSOD... it simply goes to instant black... and starts rebooting. I'd say at least 50% are of this nature.

axe0 · Jun 21, 2016

The crashes that go black I cannot help with, all the times I've tried resulted in not much + black screens are not the same as a BSOD.
Only a BSOD crash provides a dump as it is a crash where Windows is capable of preventing (more) corruption, other kinds of crashes do NOT provide dumps because Windows cannot prevent corruption.

Ryder · Jun 21, 2016

Sure, understood, which is why I have only come seeking help with the BSODs... but mentioning the black screens as a clue... if it is one.

But back to the BSODs Why are you saying that the records are showing the last one was weeks ago, when the most recent minidump is from the 18th?

Thanks for your kind help.

axe0 · Jun 21, 2016

Because BSODs are not always recorded in the logs and that can happen for many different reasons.

Hard drive failure,
paging file improper,
Improper recovery settings,
Memory faulty,
System file corruption,
Registry setting corrupted,

Ryder · Jun 21, 2016

[Edit: Found out why you weren't seeing the most recent minidump.... please see next posting]

Ryder · Jun 21, 2016

OK.... I did a little checking... the most recent minidump file (from 6-18) doesn't want to go into the archive for some reason... apparently it was skipped somehow... and I can't seem put it in a zip. This explains why you didn't see the 6-18 file! It ain't there

So, I struggled for a bit to get permission to copy this file... and finally got it. Here is the most recent minidump... though I doubt it differs from the others much.

Thank you!

axe0 · Jun 22, 2016

It looks like I forgot to ask for the event logs

To prevent me from making these mistakes again, for a next time please try to run the .bat version of the DM Log Collector
View attachment 68009

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial to do so

NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums
View attachment 68010

Code:

0: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff801`c9edc000 fffff801`cab20000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR="#FF0000"]Tue Mar 22 02:49:01 2016[/COLOR] (56F0A48D)
    CheckSum:         00BFF073
    ImageSize:        00C44000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please check https://www.asus.com/Motherboards/Z97C/HelpDesk for driver updates for the Intel LAN drivers.

Code:

0: kd> lmvm e1d64x64
Browse full module list
start             end                 module name
fffff801`c9e00000 fffff801`c9e71000   e1d64x64 T (no symbols)           
    Loaded symbol image file: e1d64x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1d64x64.sys
    Image name: e1d64x64.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR="#FF0000"]Tue Feb 04 10:14:25 2014[/COLOR] (52F0AF71)
    CheckSum:         0007209C
    ImageSize:        00071000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Ryder · Jun 22, 2016

Thank you, axe0...
I got as far as the graphics drivers... and that seems to have gone well.

In your last, you included two "Code:" windows... what I am supposed to do with those?

I will work on the LAN drivers tomorrow.

Thank you again!

axe0 · Jun 22, 2016

The code posted is a small part of the output of the dumps, you cannot do anything useful with it.

BSOD daily, KMode Exception, Mem Manage, Crit. structure.

New Member

My Computer

BSOD Analyst & Security Analyst

My Computer

New Member

My Computer

New Member

My Computer

BSOD Analyst & Security Analyst

My Computer

New Member

My Computer

BSOD Analyst & Security Analyst

My Computer

New Member

My Computer

BSOD Analyst & Security Analyst

My Computer

New Member

My Computer

BSOD Analyst & Security Analyst

My Computer

New Member

My Computer

BSOD Analyst & Security Analyst

My Computer

New Member

My Computer

BSOD Analyst & Security Analyst

My Computer

New Member

My Computer

New Member

My Computer

BSOD Analyst & Security Analyst

My Computer

New Member

My Computer

BSOD Analyst & Security Analyst

My Computer