BSOD while gaming

I went into BIOS last night and saw that my CPU core temp was 83 degrees celsiu (I know, not good) so upon further investigation I noticed that my CPU cooler wasn't fully connected to the mobo, so it wasn't completely touching the CPU, causing it to overheat.

I fixed that and I played around on my computer for a few hours last night and I have yet to get a problem, so I will keep you all informed if that simple, stupid mistake of mine was the culprit.



Oh and my PSU: ESP ULTRA 750 Watt ATX Power Supply. I believe it had a fairly good rating when I bought it.

taekwonjoe01 said:

I went into BIOS last night and saw that my CPU core temp was 83 degrees celsius.

Geezus. Well, I'm glad you found it that issue. HWMonitor is what I use to keep an eye on all my temp sensors. Hope things are smooth sailing from here!

Well I just got another Memory Dumb/ BSOD and I wasn't playing any games at all. My system was idling (running utorrent downloading music) and it happened.

taekwonjoe01 said:

well i thought i uploaded them

Hi

I have gone thru all the dumps and just copied the tag line to save space. they are all similar as you can see.

newest dump memory corruption bug check 50
next page fault iin non page area=memory nviddmkm,sys
critical object terminated=ntoskrnl bugcheck f4
Memory corruption bug check 50
memory corruption bugcheck 50

The thing is only one of the dmps showed any video involvement. I just have to think there is a memory problem.

What did you use to test the memory? You should use memtestx86 and let it run for hours (preferably overnight)
I would also run a system file check to verify and fix system files
You type cmd in search>right click and run as admin> SFC /SCANNOW
Let us know the results

You may also be having a heat issue so I would get an app to mionitor the temps
If you are overclocking STOP
If you have a raid update the driver
If you get more BSOD's upload the dmp for us

Hope this helps

Ken J

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


Loading Dump File [C:\Users\K\Desktop\111409-205437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c4ee50
Debug session time: Sat Nov 14 15:00:56.562 2009 (GMT-5)
System Uptime: 0 days 0:17:20.200
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa803109633b, 0, fffff80002a96d3b, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+41b )

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

Download and install these two: Realtemp techPowerUp! :: Download Real Temp 3.40
and Memtest86+ V4.00 Memtest86+ - Advanced Memory Diagnostic Tool
Run Memtest86+ V4.00 on each stick of memory separately.

Alright so my temperatures have been under control since fully reattached my CPU heatsink.

I have a monitor running for my GPU and CPU, and Mobo, and they're all fine running under 50C consistently.

I also did run the memtest program again this past weekend and it returned that there ARE errors with my memory. So I took out one stick, and no blue screens since.

Now I am working with Manufacturer of ram to send me new RAM. Annoying because this is brand spanking new RAM to begin with. Just pulled out of package.

Thanks for the help everyone.