Jump to content
Posted 24 April 2015 - 04:18 PM
Posted 24 April 2015 - 04:45 PM
Boot into safe mode...then do the following.
Please download MiniToolBox , save it to your desktop and run it.
Checkmark the following checkboxes:
List last 10 Event Viewer log
List Installed Programs
List Users, Partitions and Memory size.
Click Go and paste the content into your next post.
Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link of the snapshot in your next post.
Posted 24 April 2015 - 04:48 PM
Thanks so much for replying, but I can only use the laptop in safe mode, and I'm pretty sure you can't install programs in safe mode, or am I wrong?
Posted 24 April 2015 - 04:51 PM
I keep getting a network error when I download minitoolbox. Oh and by the way I'm doing all this from another, older laptop that I have.
Posted 24 April 2015 - 05:04 PM
Alright never mind, I had to switch off avast for a moment to complete the download. However, will I be able to run this program in safe mode? Does it actually need to install, or is it just a kind of process?
Posted 24 April 2015 - 05:30 PM
Okay here are the minitoolbox results:
Edited by hamluis, 24 April 2015 - 06:02 PM.
Posted 24 April 2015 - 05:49 PM
I don't know what all that "a system shutdown is in progress" stuff is about by the way.
Anyway, I ran speccy, but I don't think it's working properly because I'm in safe mode. It "cannot initialize SCP dll" for CPU, RAM, Motherboard or Graphics (it says that the "CPU dll init failed (error 2)" and that "some information will not be displayed), but I can provide you with that information myself.
CPU: Intel Core i7-4960X CPU @ 3.60GHz
RAM: 32GB Kingston Hyper-X Impact 1600MHz SODIMM DDR3 (4 x 8GB)
Motherboard: Manufacturer = Notebook, Model = P570WM, unsure of temperature or socket number.
Graphics: 2X Nvidia GeForce GTX 880M - 8.0GB DDR5 Video Ram - Direct X 11
And here's the snapshot link: http://speccy.piriform.com/results/pYTy1Kly2axNCrzdFtHHSl1
Edited by clubshrimp91, 24 April 2015 - 05:55 PM.
Posted 24 April 2015 - 06:34 PM
i would run the chkdsk /r command (it seems that you may have file corruption) and then I would follow that with the sfc /scannow command.
I would then go to Windows Update and install all critical updates (no optional updates).
Then...I would try the Speccy drill again.
Posted 24 April 2015 - 06:47 PM
I actually ran chkdsk already (unchecking both options of course), and for both my drives, and no errors came up. I'll try sfc /scannow.
Isn't it kind of risky to use chkdsk to fix things if there are serious hardware issues? I only use it as a diagnostic kind of thing.
Posted 24 April 2015 - 07:09 PM
You linked me to steps on how to run sfc / scannow from a command prompt at boot, but can I not just do it from within Windows 7 in safe mode using an elevated command prompt? Reason being I don't have the OS disc to hand at the moment, and I'm sort of eager to fix this problem or figure out what's wrong. Will sfc /scannow from an elevated command prompt in safe mode suffice?
EDIT: I should probably just mention that I used chkdsk to repair bad sectors on a dodgy external drive I had a few years ago, and it totally ruined it. So I'm just wary of running it on this expensive laptop. Could I also just use sfc /verifyonly in an elevated command prompt? I'd rather diagnose things first before jumping in.
Edited by clubshrimp91, 24 April 2015 - 07:13 PM.
Posted 24 April 2015 - 07:35 PM
Okay so I booted in Safe Mode with Command Prompt, used sfc /verifyonly, and the result is that "Windows Resourse Protection found integrity violations." Details are in the CBS log, but it's a bit big to copy and paste here. Would you like me to post a dropbox link to it? Or would you advise that I just go ahead and use sfc /scannow? Again, I don't want to mess everything up like what happened to my old external drive when I used stuff like this on it.
I might regret going ahead with it if there's something in the CBS log that indicates the laptop will get screwed by sfc /scannow. Maybe you'd like to take a look at the log first?
UPDATE:Okay I threw caution to the wind and ran sfc /scannow. The message at the end read "Windows resourse protection found corrupt files but was unable to fix some of them," followed by the usual CBS log stuff. I used this: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" to narrow down what was wrong, but I don't know what I'm looking for. I can't really find any particularly negative looking stuff in that text file. Maybe you'd like to look at it?
Also, Safe Mode disables the Windows Update service, so I can't run it unless I log in through standard startup. I haven't actually tried logging in (via standard startup) after having run sfc /scannow yet, but I don't want to provoke that bsod too much in case it damages something. I'd rather you or someone maybe have a look at these text files (sfcdetails and the CBS log) to see if they reveal anything. I figure they might be able to give you some idea if I'm still liable to bsod if I try to log in normally.
UPDATE 2: Just thought I'd mention that I ran a diagnostic (not for repairing) chkdsk on both my harddrives via safe mode with elevated command prompt, and no problems were found. I'm pretty sure the problem must be detailed in either sfcdetails.txt or the CBS log, or of course in those minidumps I posted.
Sorry if I'm going a bit manic in this thread, I'm just super worried about ma dang laptop.
Edited by clubshrimp91, 24 April 2015 - 09:26 PM.
Posted 25 April 2015 - 10:37 AM
Sorry...I don't analyze sfc /scannow logs, I simply run the command multiple times, if necessary...just as I run chkdsk /r multiple times, if necessary.
Neither of these tools should be expected to overcome every situation in just one attempt, IME.
For my approach...running a new MTB and posting a new Speccy link is the method I use to attempt to see if problems still remain.
Posted 25 April 2015 - 11:40 AM
Okay, I'd really appreciate if someone could look at this latest minidump: https://www.dropbox.com/s/1b73v5c098...52-01.dmp?dl=0
Here's why: After running sfc /scannow, the NovaShield driver for the Bullguard Scanner, which was identified as problematic here:http://www.tomshardware.co.uk/answer....html#15745133 no longer has an exclamation mark beside it in Device Manager, nor is it listed as a "problem" under components in System Information. Previously, it's status read "This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)" but this is no longer the case. I don't know if sfc /scannow rectified this, but whatever the case, it doesn't seem to have anything wrong with it anymore.
The Tom's Hardware poster I was talking with studied the dmp files and told me this: "a device driver freed the same memory twice and caused this bugcheck. The driver was \SystemRoot\system32\DRIVERS\NSKernel.sys Wed Mar 18 01:13:08 2015. NovaShield Kernel Module driver Believed to be a part of BullGuard Internet Security. The process accessing the driver was BullGuardBhvSc most likely bullguardbhvscanner.exe." The person I was talking to here also suspected Bullguard: http://forums.techguy.org/windows-7/1147193-plagued-bad_pool_caller-bsod-freaking-out.html#post9073768 . However, despite the fact that there are no longer any problems with NovaShield, the bsod problem persists. This of course created a new minidump, which is the one I've posted, and I'd be very interested to find out what it says went wrong.
The problem with the Security Processor Loader Driver (that I mentioned in the above threads) has been a constant throughout all of this, so I suspect that it might have something to do with why I keep crashing. Perhaps the dmp file will detail what's happening?
One last thing: The Bullguard Scanner process that accessed the NovaShield driver was of course among the services I disabled when I tried the clean boot, and like I said the bluescreen problem persisted despite this. However, one thing I noticed when I booted via Safe Mode afterwards was that the scanner process was still running somehow. Or at least, when I looked at the services tab in msconfig, all those services I'd unchecked and disabled were still unchecked and disabled, but the status of "Bullguard scanning service", despite being disabled, was "Running," whilst pretty much everything else was "Stopped." So, this suggests that perhaps Bullguard is still the culprit despite the fact that the problem with the NovaShield driver seems to have been rectified. Again, I'm hoping this new minidump might enlighten us as to whether or not this is the case.
Thanks for reading. I feel like I might be closer to the solution now. I just want to make sure I don't do anything rash. If uninstalling Bullguard is all that needs to be done, I'd like to know that rather than repairing the OS and all that stuff. Also, those links I posted above describing problems with the Security Processor Loader Driver suggest a similarly simple solution that doesn't require anything too extreme. If that's also all that needs to be done to solve this, I'd love to know. I might seem like I'm being hyper-fastidious, but remember this is a super expensive machine, and ideally I'd like to solve this problem with the exact solution, rather than going too far or not doing enough.
Posted 25 April 2015 - 11:49 AM
Sorry hamluis, I didn't see your new post. I suppose you don't analyze minidumps either?
Well I can tell you that Speccy is still producing the same errors, and honestly I'd rather not run chkdsk and sfc /scannow too much in case it messes anything up. I'm aware that sfc /scannow can require multiple tries to fix everything, but before I do that I'd just like to be sure the problem can't be solved another way.
As for MiniToolBox, I noticed that some of the boxes you can check include List Devices (with problems or with no drivers, or both), List Minidump files, and list restore points. Do you think checking these could provide any useful information in light of what I described in my latest post? (the faulty drivers and such). Also, I presume MiniToolBox is safe to use as much as you want? Unlike chkdsk and sfc which can be harmful?
Posted 25 April 2015 - 03:08 PM
No problem...it's your system and the members here only suggest .
I've never heard anyone document either chkdsk /r or sfc /scannow...as potentially or actually harmful. Harmful to what and how? I suppose that if I have a failing hard drive and I try to run Windows commands to ameliorate such....that could be less than useful...since neither is designed or capable of curing a failing hard drive. In fact, the process of "repairing" a failing hard drive is only done by professionals employed in the business of such.
0 members, 0 guests, 0 anonymous users