Associate
- Joined
- 17 Apr 2010
- Posts
- 461
Hi all,
New to the forums and I am looking for a little help. I purchased my kit recently from OCUK and have built it from the ground up, first time...
Spec:
Corsair 850W Power Supply
Zalman case (1 front fan, one exhaust and 2 side)
ASUS M5 A88-V EVO Motherboard
1090T Black Edition CPU
Kingston HyperX Blu 4GB (2x2GB) DDR3 PC3-10666C9 1333MHz Dual Channel Kit (KHX1333C9D3B1K2/4G) RAM
MSI R6850 Cyclone Power Edition GPU
2x WD5000AAKX SATA 3HDD (in RAID 0)
ASUS Xonar DG Sound Card
I have been plauged with problems since day one, following a clean install of Windows 7 x64, the PC would reboot or hard shutdown for no apparent reason, sometimes whilst playing games, other times whilst browsing.
Checking the event viewer gave me very little indication and the issue appeared to be kernel-power related, but not much more information. No Minidump would be produced and the event viewer was no help at all...Anyway to cut a long story shorter I re-seated all components, re-applied Arctic Silver 5 thermal paste and re-installed Windows 7, made sure no OC was present on the CPU, RAM or GPU, and I have made progress...It no longer seems to just reboot, now I get a BSOD error which at least gives me some direction, sometimes this occurs once or twice daily, sometimes 2 days apart.
I am now however getting some error codes which may actually be of use I am also now getting minidump files which should help.
I do not have any knowledge of how to read the files (I can open them ok, but don't really understand what it is telling me and google hasn't been any help unfortunately).
Here is the event viewer error:
And the mini dump is linked below.
http://www.megaupload.com/?d=D6VAWNL6
Finally, when the BSOD error occurs normally it does not reveal much in terms of the component failure, however the last time it went (some 30 minutes ago) it said MEMORY_MANAGEMENT was where the error occurred.
Any help interpreting the dump file / error code would be appreciated so that I can isolate the issue and replace the component / software issue causing it.
Thanks, Chris.
New to the forums and I am looking for a little help. I purchased my kit recently from OCUK and have built it from the ground up, first time...
Spec:
Corsair 850W Power Supply
Zalman case (1 front fan, one exhaust and 2 side)
ASUS M5 A88-V EVO Motherboard
1090T Black Edition CPU
Kingston HyperX Blu 4GB (2x2GB) DDR3 PC3-10666C9 1333MHz Dual Channel Kit (KHX1333C9D3B1K2/4G) RAM
MSI R6850 Cyclone Power Edition GPU
2x WD5000AAKX SATA 3HDD (in RAID 0)
ASUS Xonar DG Sound Card
I have been plauged with problems since day one, following a clean install of Windows 7 x64, the PC would reboot or hard shutdown for no apparent reason, sometimes whilst playing games, other times whilst browsing.
Checking the event viewer gave me very little indication and the issue appeared to be kernel-power related, but not much more information. No Minidump would be produced and the event viewer was no help at all...Anyway to cut a long story shorter I re-seated all components, re-applied Arctic Silver 5 thermal paste and re-installed Windows 7, made sure no OC was present on the CPU, RAM or GPU, and I have made progress...It no longer seems to just reboot, now I get a BSOD error which at least gives me some direction, sometimes this occurs once or twice daily, sometimes 2 days apart.
I am now however getting some error codes which may actually be of use I am also now getting minidump files which should help.
I do not have any knowledge of how to read the files (I can open them ok, but don't really understand what it is telling me and google hasn't been any help unfortunately).
Here is the event viewer error:
And the mini dump is linked below.
http://www.megaupload.com/?d=D6VAWNL6
Finally, when the BSOD error occurs normally it does not reveal much in terms of the component failure, however the last time it went (some 30 minutes ago) it said MEMORY_MANAGEMENT was where the error occurred.
Any help interpreting the dump file / error code would be appreciated so that I can isolate the issue and replace the component / software issue causing it.
Thanks, Chris.
Last edited:
