getting more and more BSOD's.... getting sick of it, finally going to ask for help.
the last two BSOD's never made a .dmp file for some reason.... even though the settings are set to make a .dmp file in %systemroot%/minidump i have a couple older ones though. Any help would be greatly appreciated!
Just got another BSOD. No .dmp file this time eitherThis time I was in Netflix (in Chrome) and it was paused. An error message popped up saying silverlight had crashed, and moments later, a BSOD.
Is there anything else I can do for info?
Make sure your dump logging is enabled.
MSINFO32:
- Click Start, point to Settings, and then click Control Panel.
- Double-click System.
- Click the Advanced tab, and then click Settings under Startup and Recovery.
- Check Write an even to the system log, and Automatically restart.
- In the Write debugging information list, click Small memory dump (256k).
Location of Dumps:
C:\Windows\minidump
- Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter.
- Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
- Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).
here they are... and dump logging is enabled.
Had another BSOD. I was gone when it happened. No .dmp file.... i checked with the SF_Diagnostic_Tool and manually. Nothing. Heres a snip of when I double checked my settings....
Perform a Clean boot:
Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
- Click on the
- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow
Full tutorial here:
Run Disk Check on your Hard Drive for file system errors and bad sectors on it:
Upload a screenshot of your hard disk using Crystal Disk Info:
- CrystalDiskInfo - Software - Crystal Dew World
- Screenshots and Files - Upload and Post in Seven Forums
Make a hard drive test from the hard drive manufacturers website:
Test your Hard Drive with SeaTools:
Back again... it was my old hard drive causing the BSOD's, i think anyway... it was definitely faulty. I didn't use my comp for a long time due to the BSOD's but then i got a new hard drive, a SSD :) and the thing is awesome. I am using the SSD for my OS but I still have my old faulty HD hooked up with all its info (if this is causing the BSOD's please let me know!) Anyway I got a BSOD two days ago and another just a little bit ago today. Any help would be greatly appreciated! You guys are awesome!
Hi, sorry for not following the rules. So simple, yet you probably have so many people not follow them. Well here is the proper zip (with a new BSOD), and thanks again for any help.
1)Things to know (that you will probably know as soon as you review that folder):
2)My slave drive is a new with a fresh SSD (my old HDD was faulty)
3)I still have the old faulty drive with all the info hooked up (it has windows still installed but I dont run windows off it)
4)Once so far since I got the new SSD the message has appeared on boot up: "A disk Error occured: ctrl alt del to restart." This used to happen often before the new drive. (I have heard it can be fixed by reflashing BIOS or something, I have NOT done that)
5)BSOD's happen even when I'm running stuff that isn't related to the old drive
The crash dumps are all pointing to Netgear Neutral Wireless Solution.
The driver is extremely old, and cannot be compatible with windows7.Code:BugCheck A, {0, 2, 1, fffff80002ee38ac} *** WARNING: Unable to verify timestamp for scmndisp.sys *** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys Probably caused by : scmndisp.sys ( scmndisp+16d1 ) Followup: MachineOwner ---------
Search for a possible update to it from NETGEAR Support | Welcome .... if there is no feasible update, stop using it.Code:Image name: scmndisp.sys Timestamp: Wed Jan 17 13:18:03 2007 (45ADD4B3)
Let us know for any further BSOD after dealing with it.
Quote