Repetitive BSoD

[Mooostache]

So my system started crashing about 3 times a week starting last month and at first I didn't think much of it since there wasn't much I was able to do about it, but lately it's becoming a problem because I keep crashing at the worst times. I'll post up my latest crash dump for you guys to see.

My Specs:

Windows 7 64 bit Preinstalled
4gb Ram
AMD Phenom II X4 925
Nvidia Geforce GTX 460
Gigabyte GA-770T-USB3

.Zip:

 

[zigzag3143]

So my system started crashing about 3 times a week starting last month and at first I didn't think much of it since there wasn't much I was able to do about it, but lately it's becoming a problem because I keep crashing at the worst times. I'll post up my latest crash dump for you guys to see.

My Specs:

Windows 7 64 bit Preinstalled
4gb Ram
AMD Phenom II X4 925
Nvidia Geforce GTX 460
Gigabyte GA-770T-USB3

.Zip:

Memory corruption probably caused by a driver. Please run these 2 tests


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.



Driver verifier

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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).

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.

 

[Mooostache]

I ran Memtest86, but it started reporting thousands of errors on test 9 after the first pass, I wasn't able to continue with the test because it got stuck there.

 

[FredeGail]

I ran Memtest86, but it started reporting thousands of errors on test 9 after the first pass, I wasn't able to continue with the test because it got stuck there.

Can you remove one stick and check for errors, and remove it again and so on. Try also if you could rent some other sticks and check those in MemTest also. This will confirm if it's the sticks, or the slots.

By the way, for your information, if you see the red text I selected, it says it's a corruption.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI00.596\070811-12714-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`030a5650
Debug session time: Sat Jul  9 05:40:51.403 2011 (UTC + 2:00)
System Uptime: 0 days 12:02:17.042
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa9005ed89c8, 2, 0, fffff80002f87fef}

[B][COLOR="red"]Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )[/COLOR][/B]

Followup: MachineOwner
---------

Best Regards,
FredeGail

 

[Mooostache]

Sorry for the bump, but I just came back to this thread after all this time to keep you guys up to date on what's happening with my BSoDs.

I moved my ram sticks to my other slots like I was told and that didn't fix the problem. I ran Memtest on both my sticks and it said that both of them were corrupted .

I'm still getting BSoDs, but I'm glad to know the source of my problem, planning on buying new RAM soon.

Thanks for the help.