Solved Crashes during various PC actions.

[Tekno Venus]

Great. We can rule out RAM now as a cause as after 11 passes I'm sure something would have been picked up if there were issues.

Lets see if we can find out if there is a driver issue:

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:
  

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    
    
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

Then upload the dumps following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html.

If you have any questions, feel free to ask
Stephen

 

[Salamandrex]

I set up Driver Verifier and so far no crashes for the past 4 hrs trying everything that crashed before. Either that fix you posted earlier with the usb worked or my computer isn't co-opperating. I'll run it some more and try to see if we get a crash.

 

[Dave76]

Was that using the same ISO and CD or USB stick?

Are you using a CD or USB stick?

If you are using the same ISO and same CD/USB stick, then I would call the first two tests a failure. If the tests passes the third time it still means you have RAM issues.

If you get any more crashes, run memtest86+ again on each RAM card.
Due to the previous errors, I would recommend running memtest86+ on the individual RAM cards as suggested in the tutorial:
RAM - Test with Memtest86+

The sad truth is RAM testing is not an exact procedure, there are several factors that are involved, I have seen many cases of memtest86+ passing several times and then having errors on a subsequent test. Then replacing the RAM, or adjusting settings, solved the problem.

From my experience and many other 'RAM testing' sites, the Windows Memory Diagnostic Tool does not show many errors. There have been numerous times that the Windows test showed no errors and memtest86+ (or other third party tests) will show errors when ran.
If you want to run a RAM test from windows, run Memtest for Windows by HCI.

 

[Tekno Venus]

Ok then. Dave knows more about RAM than I do so here is my suggested plan of action.

Continue running driver verifier for up to 12 hours. If no crashes happen during the 12 hours, disable verifier and report back.

Once that is complete, run memtest again. As Dave pointed out, the first two tests sort-of failed so we cannot be sure the RAM is stable. Download a fresh ISO file and burn it on to a fresh CD. Run memtest for each stick of RAM, i.e, remove all but one stick for each test. Once all the ram modules are tested separately report back.

Stephen

 

[Salamandrex]

Got a bsod with driver verifier on going to try to get a few more then if thats inconclusive run memtest again individually.

 

[karlsnooks]

with bsods, then you can submit the .DMP files here along with other needed info for analysis.
Blue Screen of Death (BSOD) Posting Instructions

 

[Tekno Venus]

Once you've got 2-4 crashes with verifier, upload the dumps here before doing anything else. I'll see what driver is causing the crashes, if any.

Stephen

 

[karlsnooks]

I use a binary method of locating offending dirver(s).
Cut the number of drivers checked off in half.
Keep the half that causes the problem and just keep halving to you locate an offending driver.
After updating that driver, then I repeat the process is case there is more than one offending driver.
Slow method and not as quick as analysis of a dmp file, but the procedure works for me.

I also recommend using NirSoft's DriverView: Loaded Windows Drivers List

The output is very thorough and allows sorting on various fields. My top choice is to sort with the oldest files listed first. Quite often you will find that a fundamental chip driver for the motherboard is out-of-date.

 

[Salamandrex]

The program still isnt grabbing the .dmp files so I'll upload C:\Windows\MEMORY.DMP to filesonic and hopefully that'll work.

 

[Tekno Venus]

I use a binary method of locating offending dirver(s).
Cut the number of drivers checked off in half.
Keep the half that causes the problem and just keep halving to you locate an offending driver.
After updating that driver, then I repeat the process is case there is more than one offending driver.
Slow method and not as quick as analysis of a dmp file, but the procedure works for me.

I also recommend using NirSoft's DriverView: Loaded Windows Drivers List

The output is very thorough and allows sorting on various fields. My top choice is to sort with the oldest files listed first. Quite often you will find that a fundamental chip driver for the motherboard is out-of-date.

That's a good method to follow when the BSOD's aren't creating minidumps. However, if they are, just upload the dumps following the posting instructions. Then I can debug them.

Regarding Driver View, it's a useful program but thanks to the fantastic worn of Writhziden, I now have a custom made tool for doing that and more. It's stills useful program however.

So, Salamandrex, what I want you to do us wait until you get a few more crashes with Driver Verifier enabled. Then disable verifier and follow the posting instructions to upload the dumps. I'll then analyse them and post back. Then you can either update the offending driver or run some more hardware checks.

Stephen

 

[Tekno Venus]

The program still isnt grabbing the .dmp files so I'll upload C:\Windows\MEMORY.DMP to filesonic and hopefully that'll work.

Ok, missed that when typing my previous post. If you can do that, I'll look at them tomorrow.

 

[karlsnooks]

Salamandrex,
Please read this very carefully. This will guarantee that all requirements for creating minidumps have been fulfilled.

Just today, I added a little more to this write-up.

After carrying out the steps in the write-up, then and only then:
go to an command prompt, enter following, and attach the resulting dmpinfo.txt file to your next post. DmpInfo.txt will be on your desktop.

wmic recoveros get /all /format:list > %userprofile%\desktop\dmpinfo.txt

[FONT=&quot]MEMORY DUMPS - REQUIREMENTS[/FONT]


Enable automatic management of the Paging file
WIN + PAUSE/BREAK key combo |
Advanced system settings (left-hand side) |
Advanced tab, Performance section, Settings |
Advanced tab, Virtual Memory section, Change |
checkmark Automatically manage paging file size for all drives |
OK | OK | OK



STARTUP AND RECOVERY SETTINGS
WIN + PAUSE/BREAK key combo |
Advanced system settings (left-hand side) |
Advanced tab, Startup and Recovery section, Settings |
System Failure section | checkmark Write an Event to the system log
| uncheck Automatically restart |


Under Write debugging information, select Small memory dump |
in the Small dump directory: box, enter %SystemRoot%\Minidump | OK

If Overwrite any existing file is checked, then:
Ø Under Write debugging information, select Kernel memory dump
Ø Uncheck Overwrite any existing file
Ø Under Write debugging information, select Small memory dump
Ø OK button
If you get a crazy message from Win 7 about your paging file being too small, then just ignore the message since we have already made sure that the paging file is set to be managed by Win 7.

ENABLE THE WINDOWS ERROR REPORTING SERVICE
WIN key | type SERVICES.MSC | ENTER |
Scroll down to Windows Error Reporting Service |
Rt-clk on Windows Error Reporting Service | Properties |
General tab | for Startup type, choose Automatic |
In Service status, Start button (unless grayed out) | OK


ASSURE THAT CCLEANER IS NOT DELETING DUMPS
CCLEANER | Cleaner icon | Windows tab | System category |
Uncheck Memory Dumps
· WINDOWS ERROR REPORTING SERVICE must NOT be disabled!
· WIN | Services.msc | Enter
· Under Name, locate Windows Error Reporting Service
· If Status is not Started, then
Right-click on Windows Error Reporting Service |choose START
· If Startup Type is not Automatic, then
Right-click on Windows Error Reporting Service |
choose Properties | General tab |
set Startup type to Automatic
· Close Services.msc (I like to use ALT + F4)

After a crash, the minidump file will be in %SystemRoot%\Minidump
%SystemRoot% is generally C:\Windows

==============================================================
==============================================================

Incidentally, a minidump is considerably smaller than a kernel dump and still contains all of the info needed.

 

[Salamandrex]

MEMORY.zip Memory.dmp file, as well as the .txt file attached. I got one bsod with driver verifier the rest have been the standard freezes I've gotten. Not sure if they create dmp files or not. If theres anything else I need to provide please let me know. Thanks for the help

 

[karlsnooks]

Salamandrex,

The other info that is helpful to the bsod analyzers can be supplied by:
Blue Screen of Death (BSOD) Posting Instructions

 

[karlsnooks]

The dmpinfo.txt file is in order. Now the new dumps won't be overwriting the previous dump and your .DMP files are in c:\windows\minidump folder.

 

[Salamandrex]

Will upload ASAP. While doing a system health scan my computer turned off on its own. This type of crash is new to me and seemed noteworthy. Is this indicitive of anything?

 

[karlsnooks]

The dump analysis experts such as Tekno Venus are best qualified to help you here.

Quite often strange problems, after drivers are eliminated, come from memory failures, disk failures, over-clocking, and over-heating.

You've tested the memory.

Did you run CHKDSK on each of your drives?

Did you Microsoft's Defragmenter (do not use a 3rd party product) to defragment your drive?

Are using Speccy or CoreTemp to keep an eye on your disk and/or processor temps?

Post up a fresh copy of the three files mentioned in this write-up and I'll see if maybe there are programs which should/could be uninstalled, programs running at startup time that do not to run at that time, scheduled tasks which do not need to be scheduled.

Install CCleaner:
CCleaner - PC Optimization and Cleaning - Free Download

list of STARTUP PROGRAMS

CCleaner | Tools icon | Startup button | Windows tab |
click on Save to text file button (bottom right side) |
accept Startup.txt as file name | SAVE button

list of SCHEDULED TASKS

CCleaner | Tools icon | Startup button | Scheduled Tasks tab |
click on Save to text file button (bottom right side) |
enter Scheduled Tasks as File name | Save button

List of INSTALLED PROGRAMS

CCleaner | Tools icon | Uninstall button |
click on Save to text file button (bottom right side) |
accept install.txt as File name | Save button


UPLOAD, as an attachment, the startup.txt file
UPLOAD, as an attachment, the Scheduled Tasks.txt file
UPLOAD, as an attachment, the install.txt file.

HOW TO UPLOAD
Post a File or Screenshot in Seven Forums

 

[Salamandrex]

On reboot i recieved a BSOD of BAD_SYSTEM_CONFIG_INFO STOP:0x00000074 before windows fully loaded.

 

[karlsnooks]

I'm not qualified to answer such a question. Tekno is your man!

Furthermore, isolated stop codes do not tell enough of the story, which is why the dmp files and their analysis is so vital.

 

[writhziden]

Are you still receiving the 0x74 BugCheck during restart? That BugCheck code means your registry is corrupted and you should choose Last Known Good Configuration (advanced) if given the option. Otherwise, you may want to try a http://www.sevenforums.com/tutorials/700-system-restore.html to recover the registry from a backup within a recent restore point.

Your Memory.DMP file was corrupted and pretty useless other than the BugCheck 0x50 code is most often faulty memory related.