I have seen many times people asking about windows crashes and others shooting in the dark about hardware problems, heat problems, cleaning ram, cleaning dust etc... etc... etc...:rofl:
Lets analyze and find out whats exactly wrong. and try to fix it instead of replacing the ram.
step 1: setup the mini dumps.
Step 2: Analyze the dump.
Install the "debugging tools for windows" from msdn and open windbg.
From here:
Install Debugging Tools for Windows 32-bit Version
Install Debugging Tools for Windows 64-bit Version
now, in the command window, type "!analyze -v"
Now you have found which driver is rogue.
now, uninstall the bugger and get a stable new version. or remove the service from registry. (brute way of cleaning)
And please don't blame windows for rogue third party drivers.
Disclaimer: Although 90% the crashes are similar, some times windows crashes due to some faulty windows drivers and some strange cases the minidumps dont provide enough info. but at least you wont have to panic that your ram modules are burnt.
Lets analyze and find out whats exactly wrong. and try to fix it instead of replacing the ram.
step 1: setup the mini dumps.
Step 2: Analyze the dump.
Install the "debugging tools for windows" from msdn and open windbg.
From here:
Install Debugging Tools for Windows 32-bit Version
Install Debugging Tools for Windows 64-bit Version
now, in the command window, type "!analyze -v"
Now you have found which driver is rogue.
now, uninstall the bugger and get a stable new version. or remove the service from registry. (brute way of cleaning)
And please don't blame windows for rogue third party drivers.
Disclaimer: Although 90% the crashes are similar, some times windows crashes due to some faulty windows drivers and some strange cases the minidumps dont provide enough info. but at least you wont have to panic that your ram modules are burnt.