Computer crashing seemingly randomly and consistently

[CraftyWeasel]

Running Windows 7 home premium 64 bit
Clean install built computer myself from scratch and fresh disk from Microsoft
First install never re-installed or installed any other OS
Computer is only 3-4 months old as well as OS

The problem I have been having is that my computer will just crash completely with no explanation. I can be doing absolutely anything or nothing at all, and my computer screen will either sometimes BSOD and give me a 1033 code or it will just go black and take like 4-5 restarts before it will even give me video to my monitor.

lemme know anything else you need me to tell you about, or any other files i need to attach and how to get them.

 

[FredeGail]

Hello CraftyWeasel & Welcome to SevenForums! Oh and, thanks for following the instructions with the .zip file.

That's a bunch of crashes you got there. Let's take a look at it-

:ar: BSOD Summary

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+156354 )

As you can see, one of your crashes was a cause by nvlddmkm.sys, which is a Nvidia driver. Do you have any chance to uninstall this Graphic Driver, and install the newest one?

Best Regards,
FredeGail

 

[CraftyWeasel]

Thanks for helping me out with this. I uninstalled and and installed the latest driver from the nvidia webpage now.

 

[FredeGail]

Upload any upcoming .dmp and we'll continue the adventure.

By the way, I also saw in your third .dmp that you had a memory corruption. If you get another BSOD, try doing a MemTest86+ as we call it. Do it under these instructions:

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

However, we probably fixed your Nvidia driver, that's good news ain't it?

Best Regards,
FredeGail

 

[CraftyWeasel]

so far it has not crashed again so thats good. and to get new .dmp would i just run the program from the instructions for posting here again after another crash? windows nt 6 bsod etc?

 

[FredeGail]

so far it has not crashed again so thats good. and to get new .dmp would i just run the program from the instructions for posting here again after another crash? windows nt 6 bsod etc?

I don't really have any experience with that, but I think you should just leave the set-up as it is, and go to the path where they're located.

Looks good so far.
FredeGail

 

[CraftyWeasel]

I just received another bluescreen after a long time not having any =[ here is the dump and the message I received.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: FFFFF68000001588
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: FFFFF800030BAC5B
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\072611-23368-01.dmp
C:\Users\Timothy\AppData\Local\Temp\WER-44803-0.sysdata.xml

 

[CraftyWeasel]

i ran a memtest on it and it got over 100 thousand errors so i just exited i figured if i got over 100 thousand errors that means it wasnt working obviously lol.

my motherboard is: ASRock 890GX PRO3

my ram is : G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)

as far as i can see they should work fine together... any help?

 

[FredeGail]

Hello again CraftyWeasel, sorry I haven't made replies as I was in Thailand.

Your latest .dmp was also a memory corruption.

:ar: BSOD Summary

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff68000001588, 0, 0, fffff800030bac5b}

Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )

Followup: MachineOwner

Try removing one of the sticks, any see if there will appear an BSOD, then with the other, and so on.
Do you have any chance to rent some memory sticks from your friends or something? It's very likely that we found a solution on this.

Best Regards,
FredeGail