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

BSOD after January Win10 updates


  • Please log in to reply
33 replies to this topic

#1 perrybucsdad

perrybucsdad

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 19 February 2017 - 10:20 AM

My workstation has been running great for over a year.  Sometime in January it seems it started to BSOD on my and I can't figure out what the issue is.  I started all over again and reinstalled W10 x64 Pro on a fresh drive.  Attached is the one file that I generated as you requested.  The Perfmon file would never generate.
 
I see there is a MSInfo32.nfo file in the ZIP file, so I don't think you need me to type out all of my system information.  Let me know if that is not correct.  I have posted the summary from Speccy below... if that does not give everything you need, please let me know what other information you need.
 
The OS was installed about a week ago on a desktop computer.
 
Let me know if more information is needed.  Thank you.
 
Summary
        Operating System
            Windows 10 Pro 64-bit
        CPU
            AMD Athlon 64 X2 6000+    57 °C
            Windsor 90nm Technology
        RAM
            8.00GB Dual-Channel DDR2 @ 334MHz (5-5-5-15)
        Motherboard
            ASUSTeK Computer INC. M2N-E (Socket AM2 )    40 °C
        Graphics
            Acer S231HL (1920x1080@59Hz)
            1024MB ATI AMD Radeon R7 200 Series (Sapphire/PCPartner)    30 °C
        Storage
            111GB KINGSTON SH100S3120G ATA Device (SSD)    27 °C
            2794GB Western Digital WDC WD30EZRX-00D8PB0 ATA Device (SATA)    29 °C
            232GB Samsung SSD 850 EVO 250GB ATA Device (SSD)    29 °C
            3GB Kingston DataTraveler 2.0 USB Device (USB)
        Optical Drives
            HL-DT-ST BD-RE WH16NS40 ATA Device
            HL-DT-ST DVDRAM GH22LS40 ATA Device
        Audio
            AMD High Definition Audio Device

Attached Files



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:12 PM

Posted 22 February 2017 - 11:44 AM

Hi there!

Several of your dumps blamed the following drivers:

fffff801`5be6f788  fffff80d`d21d5a31Unable to load image \SystemRoot\System32\DriverStore\FileRepository\c0309377.inf_amd64_7ab08912e1e1da0a\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x45a31
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+7468 )
The first one is your AMD graphics driver, and the latter one is some NVIDIA driver. Can you try reinstalling them?

Thank you!

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


#3 perrybucsdad

perrybucsdad
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 24 February 2017 - 08:55 AM

NVIDIA driver... strange as the only NVIDIA drivers that I recall seeing were for a IDE/SATA driver.  I switched those over to the default Microsoft ones since there were lots of reports of issues with the NVIDIA drivers.

 

As of last night, this went from being a once in a while BSOD, to shortly after reboot BSOD.  I'll have to try and bring this up in Safe Mode.  I wonder is some new patch was applied to the system yesterday with the auto updates. I know after some other past updates, it reset these drivers back to the NVIDIA ones.  Not sure if there is a way to block that or not. 



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:12 PM

Posted 24 February 2017 - 03:47 PM

Can you run the Sysnative Reporting Tool for us again?


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


#5 perrybucsdad

perrybucsdad
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 24 February 2017 - 10:30 PM

Here you go...

Attached Files



#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:12 PM

Posted 24 February 2017 - 10:52 PM

atikmpag.sys, your AMD graphics driver, is still listed in the "raw stack". Did your PC come with a driver CD? If so, try reinstalling your graphics driver from there. Otherwise, try downloading it from AMD's/ASUSTeK's website.


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


#7 perrybucsdad

perrybucsdad
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 25 February 2017 - 10:17 AM

That's odd as I just downloaded the most recent driver from AMD.  Initially, MS had installed the wrong driver for the wrong card, which makes sense why it was causing errors.  I took a look at the actual card, and noted that it was the AMD Radeon HD 7700 Series.  I then got the most current driver (17.2.1) and it stabilized the PC.

 

The other day though, while Win Defender was running it's scan, all kinds of issues started popping up and it would blue screen shortly after reboot.

 

I guess I'm not sure what to do then if I have the most current video driver.  



#8 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:12 PM

Posted 25 February 2017 - 11:15 PM

Try rolling-back graphics drivers. :)


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


#9 perrybucsdad

perrybucsdad
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 09 March 2017 - 01:00 PM

Okay, so I rolled back the graphics driver and I am still seeing the same issue. 

 

Other ideas?

 

Also, I have been seeing random lockup's without the BSOD too.  This was going on when this all started, but has started to get worse.



#10 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:12 PM

Posted 09 March 2017 - 01:06 PM

Sorry to hear that. Please run the Sysnative File Collection App again, so I can review the latest dump files.


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


#11 perrybucsdad

perrybucsdad
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 09 March 2017 - 08:57 PM

Here is the file you requested.

Attached Files



#12 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:12 PM

Posted 09 March 2017 - 10:54 PM

0: kd> .bugcheck
Bugcheck code 000000F7
Arguments 0200076e`fdd81957 0000076e`fdd81957 fffff891`0227e6a8 00000000`00000000
fffff803`8fc736a8  fffff807`e9e57f5dUnable to load image \SystemRoot\System32\drivers\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
 nvmf6264+0x17f5d
0: kd> lmvm nvmf6264
start             end                 module name
fffff807`e9e40000 fffff807`e9e94080   nvmf6264   (deferred)             
    Image path: \SystemRoot\System32\drivers\nvmf6264.sys
    Image name: nvmf6264.sys
    Timestamp:        Wed Apr 20 18:49:36 2011 (4DAF6300)
    CheckSum:         00057D34
    ImageSize:        00054080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Latest dumps all have STOP 0x000000F7: DRIVER_OVERRAN_STACK_BUFFER bugchecks with an ancient NVIDIA nForce network driver listed in the raw stack. Please reinstall that driver and continue to monitor for further BSODs.

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


#13 perrybucsdad

perrybucsdad
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 10 March 2017 - 07:42 AM

0: kd> .bugcheck
Bugcheck code 000000F7
Arguments 0200076e`fdd81957 0000076e`fdd81957 fffff891`0227e6a8 00000000`00000000
fffff803`8fc736a8  fffff807`e9e57f5dUnable to load image \SystemRoot\System32\drivers\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
 nvmf6264+0x17f5d
0: kd> lmvm nvmf6264
start             end                 module name
fffff807`e9e40000 fffff807`e9e94080   nvmf6264   (deferred)             
    Image path: \SystemRoot\System32\drivers\nvmf6264.sys
    Image name: nvmf6264.sys
    Timestamp:        Wed Apr 20 18:49:36 2011 (4DAF6300)
    CheckSum:         00057D34
    ImageSize:        00054080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Latest dumps all have STOP 0x000000F7: DRIVER_OVERRAN_STACK_BUFFER bugchecks with an ancient NVIDIA nForce network driver listed in the raw stack. Please reinstall that driver and continue to monitor for further BSODs.

 

I'm not even sure where to find that driver.  Last I checked, the MB support page didn't have anything listed for it.



#14 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:12 PM

Posted 11 March 2017 - 06:29 PM

You can find the driver from NVIDIA's download page, under the "Legacy" section. :)

 

Hope that helps!!! :)


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


#15 perrybucsdad

perrybucsdad
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 11 March 2017 - 09:38 PM

Well, I decided to get a new NIC.  I went with an Intel Pro 1000 GT... no drivers for Win 10 though on their site.  Does anyone make a NIC for W10 x64?

 

Anyhow, loaded it up, disabled the old one in the BIOS, and seemed to be running okay, and then bingo... BSOD.  I ran the Sysnative File Collection App and attached it.  This is driving me nuts.

 

If anyone can recommend a NIC that you can actually get Win 10 drivers for the x64 box, please let me know.  I figured Intel should be the best.

Attached Files






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users