troubleshooting Question

Multiple BSOD and Drive Mapping Errors After Upgrading W7 Pro Desktop to W10 Pro

Avatar of Chip Levinson
Chip LevinsonFlag for United States of America asked on
* crashingWindows 10* Video CardsDesktops
36 Comments1 Solution29 ViewsLast Modified:
Hello,

3 days ago I upgraded my custom-built W7 Pro desktop to W10 pro.  The upgrade seemed to go well, but I was unable to use the desktop much due to other commitments.  Now that I have started to use it, I have run into the dreaded Blue Screen of Death three times today!  I have also had problems mapping folders on my Synology NAS.  I would get them mapped then after reboot the desktop can no longer see the network device.  Finally, I lost all audio on the desktop.  I finally got the audio to work when I unplugged my sound card and plugged my speakers into my MOBO.

The first order of business is the BSOD.  I was unable to write down the reason after the first two crashes before the desktop auto rebooted.  I took a picture of the screen at the 3rd crash.  The screen said the "Stop Code: VIDEO SCHEDULER INTERNAL ERROR".  It happened when I was trying to play a small video file on an internal HDD.  All three crashes happened when I was doing something with AVI or mp4 files located on local drives.

My video card is old and somewhat weak. Could this be the cause of the crashes?  I believe I have the latest driver available.  Here is info on my mobo and GPU:
Motherboard: ASUS P8Z77-V LK LGA 1155 Intel Z77, Bios 1402?
Graphics Card: NVidia GeForce GTX 460 EVGA 01G-P3-1361-KR

I am going to try and get info out of events log to add to this post.  I am writing this question from my laptop.

On a related note, is there a software true (preferably free or low cost) that would scan my Windows 10 desktop and tell me which drivers are out of date and help me update the drivers?

In terms of drive mapping, I have three mapped drives on my Server 2012 server (G, L, O) and 4 mapped drives on a Synology NAS (M, P, V, and W).  Once I mapped the Server 2012 drives they have been working fine.  I map the NAS drives and they work until I shut down the desktop and reboot it.  Then I get an error that roughly says "cannot find the network device".  Was thinking of disconnecting all the NAS drives and trying to map one using its 192.168 IP address instead of its alphanumeric address ("MyNAS\P drive") and see what happens after reboot.  Do you think this will solve the problem?  If not, how can I fix it?

Thanks Chip


ASKER CERTIFIED SOLUTION
Join our community to see this answer!
Unlock 1 Answer and 36 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 36 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros