Continuous BSOD after login

Hello,

I'm having a little problem with the bsod.
Everytime I start the computer in the normal way I get a bsod about 1-2 seconds after the desktop appears (after I log in) and the system crashes. When I then start the computer in the safe mode it does not instantly give me another bsod, but even in the safe mode I have gotten a bsod. I actually downloaded the exe file from the posting guide and while running that for the first time it actually crashed in safe mode again.

Because I'm really not into the really deep tech stuff, I can't make much sense of anything, so I'm just gonna follow the guide to posting step by step :)

I'm running Windows 7 Home Premium 64bit.
Its the original OS.
It is not an OEM version I think.. I did not order this computer, it was done for me. I'm pretty sure its retail, but at the moment I can not ask this to the person who ordered the computer for me.
The computer is tomorrow 1 week old. (yes I managed to crash it in a week)
The OS was installed 7-8 days ago, I'm not sure of that but its more then 7 days and less then 14 days for sure. Can ask if its important, but again not at this moment :/

When trying to do the system health report as stated in the guide (perfmon /report), it gives me a viewer stating that the system cannot find the path.

Please help me if possible, if not with a solution, maybe with clarifying some things for me.

Thanks in advance

Literally all of these are related to memory corruption



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

* If you have raid update its Driver.



Memtest.

*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

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

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.

First tried the memtest and I got over a million errors (litteraly) in a couple minutes. 17% on pass 1 at this point. I'm a bit worried I might ruin something so I'm a bit reluctant to try and actually remove things from the motherboard.. If this really is what's causing the problem (which sounds kind of weird because the computer has worked fine for a while) I'd rather have someone test the memory sticks who actually knows what they're doing :P

The zip file attached contains 2 dump files, 1 which I got when trying to go login the normal way (7410) and the other was when I tried to login through safe mode (6848).
Both happened while having the verifier on.

Thank you for helping

EDIT: I have no idea what raid is btw, I found something through google related to the BIOS, but I have never seen a thing on this computer which seems to have anything to do with it.

Thoxik said:

First tried the memtest and I got over a million errors (litteraly) in a couple minutes. 17% on pass 1 at this point. I'm a bit worried I might ruin something so I'm a bit reluctant to try and actually remove things from the motherboard.. If this really is what's causing the problem (which sounds kind of weird because the computer has worked fine for a while) I'd rather have someone test the memory sticks who actually knows what they're doing :P

The zip file attached contains 2 dump files, 1 which I got when trying to go login the normal way (7410) and the other was when I tried to login through safe mode (6848).
Both happened while having the verifier on.

EDIT: I have no idea what raid is btw, I found something through google related to the BIOS, but I have never seen a thing on this computer which seems to have anything to do with it.

Both related to memory management.

If you had that many errors you can be pretty certain it is either the ram, or a bad mobo slot.

Dont bother with verifier until you remedy the ram



RAM, like anything else can wear out, break, or simply stop working. Just because it worked yesterday doesnt mean it will tomorrow.

Its just so weird because I received the machine less then a week ago and it was put together less then a month ago..
But thanks for the help, I'm gonna let someone see about the ram sticks :)

Thoxik said:

Its just so weird because I received the machine less then a week ago and it was put together less then a month ago..
But thanks for the help, I'm gonna let someone see about the ram sticks :)

Some times ram will fry it self in the first 48 hours. Defective manufacturing.

let us know if we can help