Windows 7: BSOD on fresh morning startup.

theArtizan,

You MUST uninstall Comodo and install MSE, Microsoft Security Essentials.

Link to MSE in my signature.

Comodo,for all of its good points, has been known to stop more than one computer.

I need you to help us to help you:

1. Fully and completely fill out your system specs and here is how:
Update your SevenForums System Specs
User CP (located on the top menu bar) |
Your Profile | Edit System Spec (left-hand column)

To gather info, use Speccy (my favorite) or SIW or System Info

In the System Manufacturer Block, enter:
Ø Manufacturer and Model OR Custom build.
Ø ADD the word laptop, desktop, netbook or tablet.
For example:
Toshiba Satellite L305D notebook.

Provide full windows version info, for example:
MS Windows 7 Ultimate SP1 64-bit

Use the “Other Info” block for Optical Reader,
Mouse, touchpad, wifi adapter, speakers, monitor, etc

Scroll down and click on SAVE CHANGES.

With Speccy, you can select with your mouse/touchpad info from the display
and paste that info into your specs.

SIW is a marvelous program, but the free version does not offer
this capability.
========================================
========================================

Carry out the following:
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
========================================
thanks,
karl

Hi,

Finished with the CPU stress test.

Keyboard:
A month ago the NumLock led died, the keyboard still works. Untill aprox. 7-10 days ago the keyboard worked in the DOS screen (Safe mode, Start windows normally selection). Now it doesnt. It works only in BIOS and in the first DOS screen where you select to go to BIOS. It's a USB keyboard.
I have an old PS2 connection keyboard laying around and will switch with that one.


RAM:
Is it possible that Memtest has given me a false positive result, even with all the passes overnight?
Like written before, when I booted after the BSOD in the Recovery windows screen Win7 recognizes all 12Gb but uses only 10Mb now. I haven't rebooted since morning.
This gives me thinking that it's a hardware problem and not software. Don't want to be disrespectful towards you guys, since you know more that I about these things and all you want is to help me solve this problem.

@karlsnooks: OK, I'll update the specs.

carry out all parts of post #21.

Try the other keyboard and a different mouse also.

Did you change the BIOS settings:
QPI/Vtt Voltage change to 'Manual' and set to 1.200v?
DRAM Voltage still at 1.540v?

RAM can throw thousands of errors or just one every once in a while, either way will crash your computer.
Tests like memtest86+ sometimes have to be run several times in order to catch an error.
Make the above BIOS setting changes and run memtest86+ tonight, for seven full passes, best to run overnight.
If you get any errors you can stop the test.

The OCCT test looks ok except for the CPU temps, they are pretty close to max.
Are you using the stock Intel CPU cooler?
Have you cleaned inside the case recently?
Give it a good cleaning with a can of compressed (Dry) air, make sure the fan blades are clean.

Agree with Karl, you should uninstall Comodo and don't install the Comodo firewall.
Use Microsoft Security Essentials and the Windows firewall, for testing purposes.
Some AVs (including Comodo) are known to cause problems with Win7.

If you get anymore crashes post the full crash report.

Yes,
I have changed the BIOS settings as suggested and I'll use another keyboard and mouse. Will run another memtest86+ tonight.

Thanks for the update.

Let us know how memtest86+ turns out.

Hi,

I haven't done the memtest86+ tonight, but changed the keyboard and mouse with older ones after I've turning off the computer.
(I'll do the memtest86+ tonight. First I wanted to see if the old 'broken' keyboard was the problem.)
Freezes, BSODs ahead.

1 boot. I get into WIn7 normally, th in recognizes I have new hardware (mouse, keyboard) and installs them.

A small window appears telling me WIndows has found new hardware and I should restart it. I hit later as I wanted to see if it freezes. LOL, seconds later I get 2 BSODs before the PC reboots itself. I could barely make out HARDWARE from one of the BSODs.

In the DOS selection Window (Safe mode, start windows normally,...) I could move with the arrows a couple of times,
untill it froze again on that window, without any 30 second countdown (since I moved the selection it disappeared).
I hard boot again and on the Repair Windows / Start windows normally I could chose the Start windows normally (keyboard working) and it booted in Windows.

I get BSOD (Memory Management) and reboot.

I start windows normally and I get into windows, well... normally.

Windows froze after 3 minutes, as usual. I hard boot again.

In the DOS slction screen (Safe mode, Start windows normally) I select Start windows normally and the PC turns OFF automatically and seconds later it turns ON on it own. It recognized only 8GB of ram and went into Win normally after that.


1st. It looks like the other keyboard is really broken, since this one is working in the DOS menus. (except for the first time when it froze.)
2nd. It still have to boot it several times to settle the PC down. IT's as if it has problems waking up.

Since it was in Windows 7 when the BSODs happened I have the dump files. I attahed the SF Diagnostics files. I hope it grabbed OK.


Yeah, I have cleaned the inside, but not the RAM slots. I have to remove the FAN of the CPU cooler to get to all the RAM sticks. Will try and do it today. I'll remove the RAM, clean them with canned air and reposition everything.

The CPU cooler is Scythe Mugen 2, not the standard Intel one that comes with the CPU.

I will do the memtest86+ tonight and let it run overnight.
If cleaning the case won't solve the problem, I will probably format the System disc and reinstall Windows without COMODO.

Have a nice day.


P.S. Getting pissed at the PC and a little discouraged.

When Windows asks you to re-boot, especially with new hardware or drivers, then re-boot. Not re-booting is why you had the crash.

Re-seating the RAM is a good idea, it might help.

Your CPU core temps are too high for the Scythe Mugen 2.
When you remove the cooler, clean the old thermal paste with Isopropyl alcohol, apply new thermal paste before re-installing the CPU cooler.
This is a must do.

Is there any reason you don't want to uninstall Comodo AV?
It is your system and your choice but, it has been mentioned a couple times for a reason, we have seen AVs be the source of crashes many times. It's not that time consuming to uninstall Comodo and install MSE for testing.

Let us know if you want to continue.

It's just that I gotten used to COMODO. Nothing against MSE. It's just that Comodo's firewall is so handy. I don't like things to connect from internet and to internet If I don't want.

YES, I definitely want to continue and try to solve this. Thank you.

So, back to business.
I opened the case, took out the CPU cooler's fan and all 6 RAM sticks.
I just read you comment, Dave, so I didn't remove the cooler, either way I don't have any thermal paste at home. I'll buy some next week and clean/re-apply the paste.
Anyways, I sprayed the RAM slots on the motherboard and sprayed/cleaned each ram stick before putting them randomly back in the slots.

Something caught my attention.
In Speccy I've noticed that under RAM is written the amount and what kind of RAM and (8-8-8-20). I don't know what are the amounts in the brackets, but on the label on the RAM sticks is written 1.5V - 1.6V (which I've set in the BIOS to 1.540V, per your suggestion, Dave) and 9-9-9-27.
Might this be the problem? Should I hunt in BIOS where these amounts are set/written and change them to the amount written on the RAM labels?
Just an Idea.

I will run memtest86+ tonight, will report what are the results.
Monday morning I'll see what is the situation when I'll start the computer.
I will uninstall COMODO from my computer.

I appreciate all your help, guys. I don't mean to make you loose your time. Thank you for continuing with me and helping me out.

Have a nice day.

Are you willing to keep Comodo even if it is crashing your system?
The only way to be sure is to remove it and install MSE, for testing. I have seen several different AVs cause crashes and I recommend you to uninstall it.
You can re-install it later if it proves to not be the cause.
Boot into safe mode, go to Control Panel > Programs and Features, uninstall all Comodo listings.
Re-boot.

The RAM information is why I asked you to post the CPUZ snips.
The CPUZ Memory tab shows your current settings.
The CPUZ SPD tab shows the manufacturers recommended/tested settings for different RAM frequencies.
The only way to get the RAM and IMC voltages is from the BIOS.
Look at the CPUZ snips you posted to see what your settings are, Do Not change any of the BIOS settings unless I tell you to.

The 9-9-9-27 numbers are the first four RAM timings, these will depend on the frequency that is set on the motherboard.
Your CPUZ Memory tab tells the RAM frequency is 540MHz, your RAM timings are 8-8-8-20, when you look at the SPD tab under JEDEC#2 your setting are slightly different but is correct for the frequency.

Changing the RAM frequency, besides the XPM and SPD options, requires many setting changes and overclocking the CPU to get the bus speed set correctly.