Windows 7 - BSOD 5+ times a day

About a week back, I started blue screening with 'irql_not_less_or_equal' and some pagefile bsod (i forget the text). I formatted since I hadn't done it in awhile, hoping that maybe I installed something funky and it would get rid of the issue.

It's almost been a week since my reformat and I am still getting these errors, and a few new ones! I have 2 x 2gb of ddr3 ram in my computer (that were shipped with the comp from the factory). Since the last two days, my computer sometimes only recognizes 1 of the sticks after startup. I figure since ram is cheap, and an upgrade would be nice, I go out and buy 2 x 4gb of ddr3 ram (what I bought is compatible with my comp). I still get these errors and have the problem of the computer sometimes only recognizing half of the ram. Right now, I have the 2 x 2gb sticks of ram in since I don't want to damage the ones I just bought if I do end up returning them. In the Perfmon .html file that was included in the zip file below, the computer is only recognizing 2gb of the 4gb currently installed.

Before the format, I was getting blue screen 4-5 times a day, usually when playing games or watching videos. After format, up until today, it would bluescreen like once a day. Today, it's bluescreened more times than I can count. I've been trying to run these tests to make this topic, and it would bluescreen in the middle. I don't have too much installed since the format. Google Chrome, a few IDE's for school, iTunes, and a couple games.

Since purchase, the computer has had compatibility issues with the graphics drivers for the card installed, but it would only crash once a week max. This isn't my main issue right now, and I'm not sure this issue has happened since the format, so I doubt there are any logs about this. These blue screens would actually list the .sys file that caused it (usually dxblahblah.sys or nvblahblah.sys), recent BSOD have not listed any file.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64 bit
- the original installed OS on the system? Windows 7 Home Premium 64bit
- an OEM or full retail version? OEM
- What is the age of system (hardware)? About 2 years
- What is the age of OS installation (have you re-installed the OS?) About a week.

Here are my logs, let me know if you need any further information. The Perfmon log was generated right after startup. Computer has been crashing not too long after start up, so I did it as soon as the computer rebooted.

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.


If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


Memtest.

Quote:

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Quote:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Thanks for the reply. I ran memtest, tested each stick for 5 passes, no errors. Then I tested 1 of the sticks in each slot (separate test for each slot) for a couple passes. Nothing.

I will have to wait until Monday to run Driver Verifier. I don't have my external with me at the moment to back up my files.

I sort of have an idea on what's happening, but I'm not sure I understand it fully. This is a laptop with 2 slots for ram. It supports ddr3 1066/1333. One of the slots (the back slot) doesn't always recognize the chip that is occupying that slot. Sometimes in the setup menu (F2 at boot), it will show 4gb when I am using 2x4gb modules. Other times when I boot up, it will show the full 8gb. When it shows 8gb, sometimes the laptop will freeze on the black Windows loading screen (the one with the 16bit colors and little animation) or even the screen before. If it makes it to login without freezing, it will blue screen within 5 minutes, guaranteed. Upon booting after one of these crashes, it will only recognize one of the 4gb chips, and it will not crash as soon (if at all, haven't had the laptop running enough time since to tell). This same problem occurs with the old 2x2gb ram modules, just not as often, and doesn't always result in a crash within 5 mins of start up. Another thing I found interesting, was that using one of the old 2gb modules in combination with 1 of the 4gb ones, the laptop boots fine and runs fine as far as I can tell. After 5 or so minutes, the computer was still running error free. However, this isn't practical in the long run because the 2gb stick runs at 1066 mhz and the 4gb stick at 1333.

What does this mean? Is there anything that I can do to fix it? Even if it's a little "hackish" so to speak...

Sounds like either a mobo slot or a voltage problem what psu do you have and in BIOS what ram voltage? Specs of both sets of ram would also help (things like latency,etc)

I has the same power supply that came with the laptop. I'm not sure the wattage, but I know that during certain games the output gets up to 130w, usually the computer runes at 90-100w when no games are being ran but other programs are being used. My bios (Phoenix SecureCore) doesn't really give any detailed info. It just displays the processor types and speed, ram amount, options for boot order, things like super password, and how the fb key functions.

I instead ran a program called Speccy, it says that both sets of ram are running at 1.5 volts.

Each 2gb ram stick runs at 1066 MHz with a timing of 7-7-7-20.
Each 4gb ram stick runs at 1333 MHz with a timing of 9-9-9-24.