Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Stuck with constant BSoD's while attempting to host a dedicated server.


  • Please log in to reply
6 replies to this topic

#1 Nickoakz

Nickoakz

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 08 January 2018 - 10:14 AM

I've been struggling to find this driver that's causing constant BSoD's and a hanging system that won't automatically restart and continues to run.

I've run the Sysnative program and attached the zip file here.

 

My last BSoD error in Event Logs was '0x000000c4', which is the Driver Verifier that I've forgotten to turn off, tripping on something.

 

I do not overclock my CPU or GPU, and instead, the mass of overclocking tools is just for information about temperature and current clock.

 

I've just uninstalled the Intel Extreme, and the Gigabyte EasyTune/UI programs.


Edited by Nickoakz, 08 January 2018 - 10:15 AM.


BC AdBot (Login to Remove)

 


#2 Nickoakz

Nickoakz
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 08 January 2018 - 10:16 AM

Thought I've attached the file, here it is.

Attached Files



#3 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:05:37 PM

Posted 08 January 2018 - 11:35 AM

The first DV dump flags gwdrv.sys, a GlassWire driver. That driver dates back from 2015, either update GlassWire or uninstall it completely. The two later DV dumps flag gdrv.sys, a GIGABYTE driver you removed. After removing/updating GlassWire, disable DV and reboot and check for BSODs. If no-go, uninstall GlassWire completely.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#4 Nickoakz

Nickoakz
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 08 January 2018 - 08:00 PM

Alright, waiting for any reactions to the up to date GlassWire, and fully removed anything from gigabyte.



#5 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:06:37 PM

Posted 08 January 2018 - 10:40 PM

Hi. . .

Glasswire may be up-to-date -- but it predates your Windows 10 system -
 


gwdrv.sys    Fri May 29 00:15:40 2015 (5567E7EC)
The above driver line came from one of the BSOD dumps you submitted.

The driver is 2.5 years old.

Good luck to you.

Regards. . .

jcgriff2

Edited by jcgriff2, 08 January 2018 - 11:57 PM.

Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#6 Nickoakz

Nickoakz
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 12 January 2018 - 12:13 AM

Glasswire actually had an update that I've checked and did jcgriff2, and I've updated it in the previous post.

 

However, another BSoD just occurred, here's the second dump.

 

 

Attached Files



#7 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:05:37 PM

Posted 12 January 2018 - 12:21 AM

Time to uninstall GlassWire completely... though no memory dump I can see it's blamed in WER.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users