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.
Gamers Rule
Posted 2015-06-18T02:20:25.690
Reputation: 73
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.
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
HighTechGeek
Posted 2015-06-18T02:20:25.690
Reputation: 1 467
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. – Gamers Rule – 2015-06-18T11:02:59.393
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. – HighTechGeek – 2015-06-18T15:47:52.090
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 – Gamers Rule – 2015-06-18T16:01:37.777
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... – HighTechGeek – 2015-06-20T18:03:01.843
@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! – 0xC0000022L – 2015-06-20T19:37:34.600
@0xC0000022L Not sure why there was some confusion. After being told it was caused by a Nvidia Driver, and doing some research, it was about as clear as you make it out to be. This was established a while back. I also know that the two drivers HTG mentioned are lowering the frequency of the issue but not solving it all together. As of right now, I have my nVidia driver uninstalled and am using the integrated graphics with no issues (no intensive games, after all) until a fix rolls out. – Gamers Rule – 2015-06-21T16:31:51.417
@GamersRule: actually, you won't believe it, I looked at the dump files to establish which drivers are loaded (no symbols needed for that; none needed to see which module was the culprit either). Hadn't even scrolled down to the other question before that point. – 0xC0000022L – 2015-06-22T07:59:12.310
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.
magicandre1981
Posted 2015-06-18T02:20:25.690
Reputation: 86 560
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. – Gamers Rule – 2015-06-19T10:30:29.423
In fact, I took a look at what I have right now and it seems correct: http://bit.ly/1MRz2RF - I will try uninstalling/reinstalling it however
– Gamers Rule – 2015-06-19T10:33:24.410Looking at this, it seems to be an issue with the specific driver: http://bit.ly/1Sv0WXn and http://bit.ly/1JZkXUD
– Gamers Rule – 2015-06-19T10:43:28.963What would be the best course of action? – Gamers Rule – 2015-06-19T12:05:59.920
also reply to the topic and wait for a reply of nVIDIA and try newer drivers, if they produce one. – magicandre1981 – 2015-06-19T17:19:32.720
@GamersRule I added a link to a new nVIDIA driver. Please try this one. – magicandre1981 – 2015-06-23T04:21:55.007
Thanks, I will try installing it now. Though, feedback for this driver doesn't seem to good. – Gamers Rule – 2015-06-23T04:41:55.303
@GamersRule there is a new hotfix: http://nvidia.custhelp.com/app/answers/detail/a_id/3694 try this version.
– magicandre1981 – 2015-06-27T18:02:37.273Thanks for the update. So far 353.30 has been working surprisingly well (no BSoD yet), but I will definitely try the hotfix. – Gamers Rule – 2015-06-28T21:37:18.843
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.
Myster Mrine
Posted 2015-06-18T02:20:25.690
Reputation: 1
0
you can also try GeForce Hotfix driver 353.38
MrX1980
Posted 2015-06-18T02:20:25.690
Reputation: 11
Bit information (32Bit or 64Bit) of Windows would also be required to debug the crashdump. Refer to resources like this
– pun – 2015-06-18T03:41:56.3731Microsoft didn't release debug symbols for Build 10130, so we can't debug it. disable the power saving for some devices in device manager – magicandre1981 – 2015-06-18T04:27:00.113
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. – Gamers Rule – 2015-06-18T11:14:03.757
Regarding debugging, was there anything I needed to do? Or can we not do anything since it's the Windows 10 TP (x64). – Gamers Rule – 2015-06-18T11:15:03.817
1So apparently the BSoDs still ensue. Anyway to look at those .dmps? – Gamers Rule – 2015-06-18T16:46:38.633
I've asked a contact from Microsoft for help. I'll post again if I hear something. – magicandre1981 – 2015-06-18T17:35:40.967
It's greatly appreciated; please let me know if you find anything out. – Gamers Rule – 2015-06-19T01:34:21.540
I performed an Nvidia update today and after about an hour my computer crashed and I got this error. Now, every time I log onto my computer it crashes after about a minute with the same error. I can't even get into the Windows 8 advanced options during boot up before the computer crashes. This is unbelievable, I don't even think I will be able to reset my PC back to factory settings. – Kyle Bridenstine – 2015-11-22T05:01:32.840