BSOD's at idle and running

[Darxtar12]

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!

 

[Darxtar12]

Just got another BSOD. No .dmp file this time either This 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?

 

[koolkat77]

Make sure your dump logging is enabled.

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. Check Write an even to the system log, and Automatically restart.
5. In the Write debugging information list, click Small memory dump (256k).

Location of Dumps:
C:\Windows\minidump

MSINFO32:

• 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).

 

[Darxtar12]

here they are... and dump logging is enabled.

 

[Darxtar12]

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....

 

[koolkat77]

Perform a Clean boot:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

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 rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

Upload a screenshot of your hard disk using Crystal Disk Info:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Test your Hard Drive with SeaTools:

• How to Use SeaTools for DOS and Windows Disk Check Utility

 

[Darxtar12]

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!

 

[Arc]

Hi.

Please post it following the Blue Screen of Death (BSOD) Posting Instructions?

 

[Darxtar12]

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

 

[Arc]

The crash dumps are all pointing to Netgear Neutral Wireless Solution.

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
[COLOR=Red]Probably caused by : scmndisp.sys[/COLOR] ( scmndisp+16d1 )

Followup: MachineOwner
---------

The driver is extremely old, and cannot be compatible with windows7.

    Image name: scmndisp.sys
[COLOR=Red]    Timestamp:        Wed Jan 17 13:18:03 2007[/COLOR] (45ADD4B3)

Search for a possible update to it from NETGEAR Support | Welcome .... if there is no feasible update, stop using it.

Let us know for any further BSOD after dealing with it.

 

[Darxtar12]

I had updated the files for the netgear wireless internet thing and everything worked awesome. Then after a week of vacation I came home and turned my computer on and installed like 7 updates and installed Microsoft Security Essentials. Then after class, boom, BSOD. I never saw it, it just showed the "unexpected shutdown" error, and I have a new minidump. Smh. I would be screwed if it werent for you guys.

 

[Darxtar12]

also I updated my video card (through Nvidia) also here are those that I installed

 

[Arc]

I had updated the files for the netgear wireless internet thing and everything worked awesome. Then after a week of vacation I came home and turned my computer on and installed like 7 updates and installed Microsoft Security Essentials. Then after class, boom, BSOD. I never saw it, it just showed the "unexpected shutdown" error, and I have a new minidump. Smh. I would be screwed if it werent for you guys.

Is it? You really updated the netgear driver???

The BSOD of 24th shows the same driver that was pointed out two weeks ago, in post #10.

BugCheck A, {0, 2, 1, fffff80002ee08ac}

*** WARNING: Unable to verify timestamp for scmndisp.sys
*** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
[COLOR=Red]Probably caused by : scmndisp.sys ( scmndisp+16d1 )[/COLOR]

Followup: MachineOwner
---------

    Image name: scmndisp.sys
[COLOR=Red]    Timestamp:        Wed Jan 17 13:18:03 2007 [/COLOR](45ADD4B3)

Not updated at all. May be it does not have any further update ... you know more, I dont know, I dont use it.

But as long as the driver will be present in your system, the BSODs will continue to occur.

It is the network driver that needs to be updated. Updating the display driver will not add anything towards the solution of the issue.

If there is no further driver update after that of January 2007 for the device, dump it.

Report us for any further BSOD after doing it.