BSOD Caused By ntoskrnl.exe, Please See Attached Dump File

[Comicsnut]

Hi all!

I'm hoping for a little help in troubleshooting this particular BSOD.

I've attached BlueScreenView's HTML report, the Minidump file created and a Speccy snapshot of the machine on which this happening.

If there is any other information you need, please let me know!

 

[matts6887]

Have you added any new hardware or ram as of late? Because some of what i have researched on this points to possible bad hardware and or faulty ram. I would run memtest86+ from the following link and let it do a thorough scan:

Memtest86+ - Advanced Memory Diagnostic Tool

 

[Comicsnut]

That's usually what I've noticed when ntoskrnl.exe is the "cause", however, the client has not added any new hardware or RAM.

I ran memtest the moment I saw ntoskrnl in the report.

 

[matts6887]

Well; I would still try and do a thorough memory scan again and let it run over night. Also; you might want to try and do a sfc /scannow. Click start, programs, accessories, and then right click on command prompt and select run as administrator. Once thats done; type sfc /scannow and let it scan for any integrity violations within windows. One other thing: take a look at the following link and see if it doesnt help ya any:

Error Message:

 

[Comicsnut]

I did all the basic, standard things you're suggesting. I started memtest last night before leaving and stopped it when I arrived this morning.

I also ran a system file check.

I also googled the error, as read that technet article that suggests a disk check. This was done as well.

So, I have arrived here...posting the report, minidump and specs of the machine for someone that can open them and take a look better than I can.

 

[Comicsnut]

Anyone else have any ideas as they pertain to the actual data from the mindump?

 

[Comicsnut]

Anyone?