BSOD from ntoskrnl.exe

[space55]

Hello there!

I am having a bit of an issue. As of today, I can boot up my pc, log in to it, and for about 5 minutes, use it. After that, it BSODs, or as of late, just plain freezes. All of my temps were fine, and everything is the same as it was yesterday. I've uploaded my minidump files to Mediafire and linked them below.

Specs of my PC (Custom build):
CPU: i7 4770K @ 4.4GHz (Reduced to 4.0)
Mobo: ASUS Sabertooth Z87
GPU: EVGA GeForce GTX 780 @ Max 1280MHz
RAM: Corsair Vengeance DDR3 1600MHz
Case: Corsair Obsidian 750D
PSU: Corsair RM850
Boot Drive: Samsung 840 PRO 256GB SSD
Storage Drive: Seagate Barracuda 2TB HDD
Scratch Drive: WesternDigital 1TB HDD
Render Drive: 240GB HDD
Video Drive: Hitachi 2TB HDD
Keyboard: Razer Blackwidow Ultimate 2014
Mouse: Razer Deathadder Chroma
Headset: Logitech G930
Super important LED kit for cool lighting

Minidump folder: https://www.mediafire.com/?fb6c2km6hwj3e24

I don't get a kernel panic in a distro of Linux I have installed, so I am wondering if it's software.

 

[redgarl]

My SSD was the culpritt... and I have the same one as you.

Could also be related to your gpu, however SSD are dying the worst way possible... like you are experiencing.

Try cloning your drive on your HDD and use it as your boot disk. If everything is fine, then you know what is the problem.

 

[space55]

Does the fact that I have 25TB+ writes to the SSD count? I think I may have to agree. I'm going to go ahead and do a memory test, as I suspect slightly, because one of the two sticks has been causing problems for a while. After, I'm going to go and try to do what you said.

 

[johnbl]

32168938.sys
3930587drv.sys
really don't have an idea what these drivers are but they do show up in various bugchecks you provided.

remove the drivers you can (listed below), change your memory dump type to kernel:
https://www.sophos.com/en-us/support/knowledgebase/111474.aspx

then run cmd.exe as an admin then run
verifier.exe /standard /all
reboot your machine and see if it bugchecks, if so put the larger kernel memory dump file (c:\windows\memory.dmp) on a server and post a link.







---------
i would remove a bunch of the old ASUS utilities:
starting with IOMap64.sys Thu Feb 04 17:55:34 2010
I would also remove:
AsIO.sys Wed Aug 22 02:54:47 2012
AsUpIO.sys Mon Aug 02 19:47:59 2010
ASUSFILTER.sys Tue Sep 20 08:46:33 2011

you also have a few suspect driver:
32168938.sys Fri Mar 04 01:20:03 2011
3930587drv.sys Sat Nov 13 05:38:07 2010

(or it could be memory corruption of the memory dump, I will check another memory dump)

The actual bugcheck was bugcheck 0x101 CLOCK_WATCHDOG_TIMEOUT
in this case the system thinks what ever is running on processor 8 is hung.

(you can not debug this with a mini memory dump, you have to provide a kernel memory dump)

 

[space55]

---------
i would remove a bunch of the old ASUS utilities:
starting with IOMap64.sys Thu Feb 04 17:55:34 2010
I would also remove:
AsIO.sys Wed Aug 22 02:54:47 2012
AsUpIO.sys Mon Aug 02 19:47:59 2010
ASUSFILTER.sys Tue Sep 20 08:46:33 2011

you also have a few suspect driver:
32168938.sys Fri Mar 04 01:20:03 2011
3930587drv.sys Sat Nov 13 05:38:07 2010

(or it could be memory corruption of the memory dump, I will check another memory dump)

The actual bugcheck was bugcheck 0x101 CLOCK_WATCHDOG_TIMEOUT
in this case the system thinks what ever is running on processor 8 is hung.

(you can not debug this with a mini memory dump, you have to provide a kernel memory dump)

Where could I find a kernel dump file? In the BSOD window, it also says that there isn't enough memory for a dump. What could that mean?

Also, how are you finding all this out from a dump file? Teach me your ways...

--
Space

 

[johnbl]

The minidump file is a binary that contains info on the drivers and what was running at the time of the crash. You can use the windows debugger to read the info. The windows debugger can be downloaded from microsoft website.
it is called windbg.exe

the mini dump only contains the names of the drivers that are loaded and the current stack back trace.
The kernel memory dump contains the internal error logs, the stacks of all of the device drivers and all of the code for all of the device drivers. If you run verifier, even more info and checking is done to make debugging easy.

best to google for a tutorial on how to setup windbg.exe. basically, you install it, set up a symbol path pointing to the microsoft symbol server, then load a crash dump. Have the debugger do an automatic analysis to start with then refine it with a few commands.
I check for corrupted binaries in memory, dump the list of drivers in alphabetical order, then check a few other things depending on what I see.

---------
i would remove a bunch of the old ASUS utilities:
starting with IOMap64.sys Thu Feb 04 17:55:34 2010
I would also remove:
AsIO.sys Wed Aug 22 02:54:47 2012
AsUpIO.sys Mon Aug 02 19:47:59 2010
ASUSFILTER.sys Tue Sep 20 08:46:33 2011

you also have a few suspect driver:
32168938.sys Fri Mar 04 01:20:03 2011
3930587drv.sys Sat Nov 13 05:38:07 2010

(or it could be memory corruption of the memory dump, I will check another memory dump)

The actual bugcheck was bugcheck 0x101 CLOCK_WATCHDOG_TIMEOUT
in this case the system thinks what ever is running on processor 8 is hung.

(you can not debug this with a mini memory dump, you have to provide a kernel memory dump)

Where could I find a kernel dump file? In the BSOD window, it also says that there isn't enough memory for a dump. What could that mean?

Also, how are you finding all this out from a dump file? Teach me your ways...

--
Space

 

[Paul NZ]

Your video drivers maybe crashing too., And your razer drivers rzpnk.sys are crashing

USBD.SYS maybe crashing too. And wmiacpi.sys

I would uninstall AVG, it's useless. Then use their removal tool

It looks like you're using AVG and NOD32?? If you are, you should only have 1 firewall. Two will conflict with each other

gpt_loader.sys maybe causing something. It looks like it can conflict with HFS. Which (I think) is also made by Paragon

I dont think theyre from the same program. But they are from the same company

 

[space55]

Your video drivers maybe crashing too., And your razer drivers rzpnk.sys are crashing

USBD.SYS maybe crashing too. And wmiacpi.sys

I would uninstall AVG, it's useless. Then use their removal tool

It looks like you're using AVG and NOD32?? If you are, you should only have 1 firewall. Two will conflict with each other

gpt_loader.sys maybe causing something. It looks like it can conflict with HFS. Which (I think) is also made by Paragon

I dont think theyre from the same program. But they are from the same company

Last I checked, I don't have any of those programs except for Paragon HFS. I could've sworn that I deleted NOD32, among others. I'll go clean all of those out in a second here, provided they can be done within my five-minute time limit. Very interesting, and thanks.

 

[space55]

Oh and to add, I also have ESET Smart security as a firewall. So that's three?

 

[Paul NZ]

NOD32 = Eset software. So it may still be 2. Eset / NOD and AVG. If AVG has been uninstalled use its removal tool. To remove the rest of it

If you removed NOD32 before did you uninstall it? You didnt delete it folders without uninstalling it first?? If you did, this wont remove it

AVG]http://www.avg.com/ww-en/utilities]AVG removal tool is here[/url]

 

[space55]

I'm sorry. I thought NOD32 was Norton for some reason...

I'll go remove AVG right now, among other useless software.

 

[space55]

New minidump folder. Let me know if this doesn't have the kernel dumps, and if not, please do tell me where to find them.

https://www.mediafire.com/?dcfgepazq6h51p3

 

[Paul NZ]

I would run tddskiller on this. Those strange files may belong to rootkits or something

http://support.kaspersky.com/viruses/utility#TDSSKiller

3930587drv.sys, 32168938.sys

 

[space55]

I will gladly run that. I kinda need this PC by tomorrow, so I have a resolve - if it's not done by midnight, I'm doing a fresh install and rebuilding my data

EDIT:
Ran it, but it only scanned my C:\ drive. Any way to make it scan all my drives?

 

[johnbl]

did not see a kernel memory dump file memory.dmp in the dumps you provided.
I assume you wiped your OS and reinstalled by now.
looks like the suspect drivers were still installed in the last memory dump shown.

I will gladly run that. I kinda need this PC by tomorrow, so I have a resolve - if it's not done by midnight, I'm doing a fresh install and rebuilding my data

EDIT:
Ran it, but it only scanned my C:\ drive. Any way to make it scan all my drives?

 

[space55]

Yep. I wiped my OS, since I really needed it today. However, I probably still have some files left over.

I'll try to be a bit more careful as to which drivers I install in the future. Thanks a lot for you help!

--
Space