7

I've been prompted with BSoD, at seemingly random times, with the above error. This is off a fresh install of Windows 10 (2 times in fact) on a new hard drive. This is my model: https://docs.sony.com/release/specs/SVF15A18CXB_mksp.pdf

Here are the recent .dmp files for your analysis: http://bit.ly/1d2w4gZ

All my drivers are up to date. Thank you for your time and consideration.

8
  • Bit information (32Bit or 64Bit) of Windows would also be required to debug the crashdump. Refer to resources like this
    – clhy
    Jun 18 '15 at 3:41
  • 1
    Microsoft didn't release debug symbols for Build 10130, so we can't debug it. disable the power saving for some devices in device manager Jun 18 '15 at 4:27
  • In Device Manager, I disabled power saving for: Generic USB Hubs, USB Root Hubs, Broadcom Wireless (disabled since I use ethernet with Realtek PCIe) and Bluetooth (which is turned off anyways); in fact none of these are important since I'm always plugged in. Nevertheless, we'll see whether I get any more issues today. Jun 18 '15 at 11:14
  • Regarding debugging, was there anything I needed to do? Or can we not do anything since it's the Windows 10 TP (x64). Jun 18 '15 at 11:15
  • 1
    So apparently the BSoDs still ensue. Anyway to look at those .dmps? Jun 18 '15 at 16:46
4

Update: So it's a known driver issue with Nvidia on a pre-release OS. Welcome to beta testing. Some people are lowering the frequency of these errors by using an older Nvidia driver (350.12) or the new beta notebook driver 353.17 or reverting to their onboard video driver while waiting for updated drivers. There's not much else you can do.

Initial suggestion

  • Check Sony's site to see if you have the latest BIOS installed

    • Check for corrupt system files by executing the following from a Command Prompt (Admin) and typing in sfc /scannow

    • Use MemTest86 to check for faulty RAM

7
  • I've verified the integrity of my system files, my RAM, and have the latest version of the BIOS already installed. Therefore, there is likely another cause for the BSoD. Jun 18 '15 at 11:02
  • Did you check Device Manager to see if you have all the drivers installed? Sometimes just installing an OS from a generic source (generic being plain vanilla Microsoft in this case and not a Sony specific source) leaves many manufacturer's drivers uninstalled. Sony should have a support site with additional drivers required by your computer. Try using the Sony Windows 8 drivers as I assume they haven't published Windows 10 drivers yet. Chipset, bluetooth, video card and other drivers often must be installed from the manufacturer's site after a clean OS install. Jun 18 '15 at 15:47
  • It seems like I have all my drivers installed. I was missing one a few days ago, and found it online at the Sony site and that was fixed. Windows 10 Sony Drivers are not out, but Windows 8 drivers seem to work perfectly fine (Nvidia is already supporting W10). I'll be trying @magicandre1981 method and seeing if it works, for now. Thanks Jun 18 '15 at 16:01
  • So it's a known driver issue with nVidia on a pre-release OS. Welcome to beta testing. Some people are lowering the frequency of these errors by using an older nVidia driver (350.12) or the new beta notebook driver 353.17 or reverting to their onboard video driver while waiting for updated drivers. Not much else you can do... Jun 20 '15 at 18:03
  • @GamersRule: uhm ... what? The bugcheck code is crystal clear. WinDbg proves that nt tears down the system, so all points to a misbehaving driver. Nothing even pointed to RAM or hardware in the first place, although BIOS (also for the VGA) is always a possibility. HighTechGeek is spot on, though, lm shows nVidia drivers loaded and you would be well advised to check the driver timestamps for those nVidia drivers against the driver bundle (unless you know already). I think that HighTechGeek is spot on. And it's on nVidia to fix the issues (i.e. not MS, none of us certainly). +1 to HTG! Jun 20 '15 at 19:37
1

My Microsoft contact looked at the dump and told me, that the nVIDIA GPU driver caused it. So update the nVIDIA driver and try the Windows 10 driver, which nVIDIA offers.

On 2015/06/22, nVIDIA relased a new WHQL driver 353.30. Try this updated driver.

9
  • Thanks for looking into this! A little bit strange since I'm quite certain I downloaded the latest, proper version for Windows 10 (I have the 735m) from that site. Will give it a shot though. Jun 19 '15 at 10:30
  • In fact, I took a look at what I have right now and it seems correct: bit.ly/1MRz2RF - I will try uninstalling/reinstalling it however Jun 19 '15 at 10:33
  • Looking at this, it seems to be an issue with the specific driver: bit.ly/1Sv0WXn and bit.ly/1JZkXUD Jun 19 '15 at 10:43
  • What would be the best course of action? Jun 19 '15 at 12:05
  • also reply to the topic and wait for a reply of nVIDIA and try newer drivers, if they produce one. Jun 19 '15 at 17:19
0

you can also try GeForce Hotfix driver 353.38

0
0

I have had this error message on 4 different occasions this past week while working on a system that ultimately got updated to Windows 10 Pro.

i7-3770/16GB with 1TB Crucial SSD and finally a 256GB SSD with an NVIDIA GT630

Each time I got that screen (some are calling a BSOD), is when was forced to do the hard reset on the computer and then the rather quick restart. I attributed it to the SSD not being able to fully recover/prepare for a restart.
I validated this, albeit maybe not the reason, by the next time I need to do a forced restart using the switch on the power supply and letting the system rest for a few seconds. I haven't seen the problem since.

btw. . .system is finally up and running by replacing the 1TB SSD with the 256GB.

Not the answer you're looking for? Browse other questions tagged or ask your own question.