New
#1
Erratic BSOD. Perhaps related to downloading to external hdd
Hi thread title has half the info, the only other thing would be, sometimes I get a bluescreen with seemingly no dump file.
Thanks
Hi thread title has half the info, the only other thing would be, sometimes I get a bluescreen with seemingly no dump file.
Thanks
Hello, Encephlon. I will see if I can help with this. You only had one dump file, which is what we use to debug. One dump is not a good sample, but this is what the dump says.
That is the Volume Shadow Copy Driver supplied by Windows updateCode:BugCheck 1000007E, {ffffffffc0000005, fffff8800172dd6e, fffff880041247c8, fffff88004124020} Probably caused by : volsnap.sys ( volsnap!VspCollectLazyOffsetsPass+1be ) Followup: MachineOwner
Also shown as causes are
[CODEigdkmd64Code:fffff880`041242c8 fffff880`05ce91a8Unable to load image igdkmd64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys igdkmd64+0xbc1a8
start end module name
fffff880`05c2d000 fffff880`05fec000 igdkmd64 T (no symbols)
Loaded symbol image file: igdkmd64.sys
Image path: igdkmd64.sys
Image name: igdkmd64.sys
Timestamp: Fri Sep 26 08:42:04 2014 (54256D2C)
CheckSum: 003B14CE
ImageSize: 003BF000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4][/CODE]
That is your Intel Graphics driver and can be updated at your manufacturer's web site.
But also listed is
Code:fffff880`04124120 fffff880`0515cea0Unable to load image nvkflt.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvkflt.sys *** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys nvkflt+0x3bea0That is your Nvidia Graphics Filter Driver.Code:nvkflt start end module name fffff880`05121000 fffff880`0516e000 nvkflt T (no symbols) Loaded symbol image file: nvkflt.sys Image path: nvkflt.sys Image name: nvkflt.sys Timestamp: Fri Mar 13 10:31:22 2015 (550302CA) CheckSum: 00052D15 ImageSize: 0004D000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
I also notice that you have an awful lot of errors with Your Secunia Software. Specifically PSIA.EXE. I would uninstall it and install something else to replace it
If you would please fill out your system specs in as much detail as possible. It is difficult for me to recommend things when I have no idea of what hardware w are dealing with. This may help you.
Please fill out your System Specs
InformationYour System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs
I would also run Seatools for DOS SeaTools for DOS and Windows - How to Use on all the drives, especially the external drive.
If you would. please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Hi thanks for looking into my problem!
So far I have uninstalled Secuina, succesfully completed an system file scan and found no errors, fleshed out my system specs, updated my Intel graphics driver from the Intel site but could not update my nVidia driver as it is apparently up to date.
I will run the Seatools thingo and post results later. Note that neither the ssd or the external hdd are Seagate so I will be unable to run the extended test thingos.
Thanks again
I wouldn't run it on the SSD, and you can try Western Digital's Data Lifeguard instead, I believe this link still works
WD Support / Downloads / SATA & SAS / WD Black. A lot of people have trouble with the WD one. With Seatools I believe you can run the long Generic test. But, whichever one you would like to use.
Also, I presume you have switchable graphics in your Laptop.
I'm running the WD Data lifeguard Windows short test on the external as we speak, is it necessary to run the Seatools one in DOS for the external? It's more convenient in Windows as I happen to have no USB sticks or blank discs with me.
Edit: The quick test passed. Yes, graphics switch dependent on the rules set in the nVida control panel app.
Further edit: One of the times it BSOD'd but didn't leave me a minidump my computer kept trying to restart except it kept not finding a boot device until I powered off with the button and then powered on again with the button at which point it booted normally.
Western Digital has a DOS version also. We prefer the DOS version because it gives a better test when the drive you are scanning is not in use at the time. But, if for whatever reason you can't do the DOS test, the installable one will do.
Well the quick Windows test has passed, and now I'm running the extended Windows one. I can go and get a usb though if necessary.
No, I doubt if it is that important. I am concerned about you not being able to locate a bootable device. That would mean the hard drive is disappearing. Please make sure your SSD is up to date with the Firmware. I believe you can get the updated firmware here support-ssd-firmware | United States (USD)
I have updated the SSD firmware to the latest revision, and have not yet BSOD'd since the minidump that you found in the zip in the OP. In doing so I had to abort the extended WD test, however the quick test did pass so unless you think otherwise I assume that is fine? Should I do anything else or should I assume this is solved until another BSOD?
If so do I mark this thread as solved now?
Thanks for your help
I would wait a while before marking it solved. Whenever you think it is solved, mark it that way,