your the 2nd person who told me that cooler master doesn't make good PSUs. I have checked several calculators and I'm above the recommended min. and thats with everything that runs off my PS. Before I start buying stuff, I need to know whats causing the problem.
ok , so it might be my memory?
heres a BSOD I got today. I had problems uploading the file so I just copied and pasted it.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\071911-23166-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c50e50
Debug session time: Tue Jul 19 21:46:44.292 2011 (UTC - 5:00)
System Uptime: 0 days 7:49:00.978
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa7fffffffb0, 2, 1, fffff80002aa902e}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+9602e )
Followup: MachineOwner
---------
I also got a BSOD that said something about memory management, it wasnt able to save the dump, cause the computer froze up. and I only get BSODs when I play games
Without symbols configured, that output is not helpful. Also, the file is binary, meaning it is searchable (which is what we do with it), which is where it's useful. So if it's too big to zip up and post somewhere, it's not going to be much help to any of us unfortunately.
ok, zipped the file and uploaded it.
071911-23166-01.dmp.zip
The memory dumps do actually point to memory corruption, although it's not 100% clear if it's a driver issue or if it really is a RAM issue. You mentioned earlier that you had tested the memory earlier, so that would leave potentially a software issue. The PSU could still be an issue if the power is not sufficient or clean, but I leave that to the hardware folks. However, the error really is happening when reading memory due to an invalid memory address (passed in via an invalid PTE), but it's just not easy to say whether it's a software or hardware issue.
When you said you tested your ram did you use memtest86 and did you run it for at least 8 passes? If not, I would suggest you download free memtest86 and run it at least 8 passes (which will take several hours. 7 on my machine). Download the ISO file and byrn it to disk and boot from the disk. They also have a version that will install to a USB drive.
i tried the ram in another system and it was fine, and I ran memtest86 for 4 hrs, I'll run it again overnight.
More at Johnny Guru.Coolermaster has a decent 600 watt unit here. The unit does pretty well for stability and efficiency, doesn't get very loud, and... what? It's a 750 watt unit?
This is a link to the last review page. Fortunately it has a 5 yr warranty. While the PSU may not be the root cause of your issue, I think you should look into it. If it is bad you could end up with more problem, such as a motherboard fried.
Also test your RAM modules individually. Then with all installed.
ok, I did 10 passes with no errors, with both sticks of RAM. Over the next few days, I'll test the individual sticks. I think I'm going to get a new PSU, because I'm begining to worry that this coolermaster wont last long, and like you said, could end up frying my computer. do you have any suggestions for PSUs. I'm looking for the best so price isnt really a concern, with around 800-900w.
In my opinion the best PSU's are Corsair, Antec and Seasonic. There are some other good ones, but I think those 3 are the best. Best suggestion is go to Newegg, pick some out and spend some time reading customer feedback on them. Reading the reviews from those that use them will give you a better idea of which ones are best.
Quote