Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
http://www.cpuid.com/softwares/cpu-z.html
cpuz -> validate button -> submit button
it will open a browser, copy the url (address) and paste it here
is anything overclocked?
if so, what cpu cooler and how are the load temps?
I know for a fact my graphics card is factory overclocked however it is an asus and i am able to tweak it very easily. the processor i am unsure of. i originally got this from cyber power pc. they kept having problems and i didnt feel like sending it to them every time when it is 100 bucks to ship it. nothing but headaches. also the occt and my gpu tweak asus state when it is going full bore my load temps have never been about 67c. I have 4 120mm fans and an asetek 550lc 120mm self contained watercooler
Have u tried disable this as a test yet?
What about running other games or stress tests?
AMD CPUs should not run above 65*C or u may have issues; course those temps might not be accurate either unless u are viewing with AMD OverDrive; or applying the correct AMD Temp Offset to your 3rd party Temp Monitoring App.
If MemTests are freezing; please ensure the correct DRAM is setup in the BIOS; such as XMP Profile#1
ok Bad-Motha i quickly got cought up on the dram setup. when i went into my bios to change the xmp profile it seems that i do not have any xmp profiles. I also think my bios is out of date but i dont think that is what is causing the issue. when i was in my bios it said my cpu temp was at 58! and i wasnt even doing anything!
so in short i believe 1. it is overheating. 2. my 750watt power supply may not be enough at the current clock it is at right now. 4700mhz and according to my amd overdrive i just downloaded it is actually clocked at 4700 but it is drawing in 5000. with 1.5 cpu vid voltage and 1.1250nb vid. so what i can tell if i turn down my mhz to like 4000 maybe it would run a little cooler to not freaking melt my motherboard? if so what voltage should those two be at? sorry if i am kind of answering some of my own questions i am just kinda throwing some ideas out there after you two asked me some quick questions. also with my current configuration what enclosed water cooling system should i get if that does not over shoot my wattage? keep in mind i am also running at gtx 980 strix which is still far less voltage that a amd r9 290x that i used to have had in there. voltage and wattage and overclocking are not my strong suits as of yet.
0x4 - Just claiming it's Windows Vista and later
0x12C = 300 - Time-out value, in seconds
0xFFFFE001847D4880 - The thread currently holding onto the Plug-and-Play (PnP) lock.
0xFFFFF80332179900 - Reserved
The power state transition timed out waiting to synchronize with the PnP subsystem.
---
Translated in English: A plug and play driver hanged and the system shutdown on purpose to prevent any data lost. Please run a "Driver Verifier", fix corrupted drivers or remove incompatible ones not supported by this Operating System, which is Windows Vista or later.
---
Start > Run > Type "cmd.exe" (without the quotes) and right-click it from the list, select "Run As Administrator".
Under that Admin Command Prompt, type "SFC /scannow" and press enter.
(this will verify your critical Windows files)
After that, type "chkdsk /f /r c:" and press enter, select it to scan upon next boot, then reboot and let it do it's thing.
(this will check your hard drive for errors and attempt to repair them)
When back in Windows: Use Spybot or similar anti-malware / rootkit scanner to check for viruses that might of hi-jacked your drivers. Just to be 100% safe. Rare case that a virus is posing or replaced a system drivers. As it claims "executing a routine that transitions from non-privileged code to privileged code", meaning the system blocked it from trying to access an area it wasn't allowed.
Uninstall any new drivers, if installed recently. If not, did Windows itself do some updates? Windows 8 seems to be extremely good at messing up third party drivers, when attempting to update itself.
Check under Control Panel > Device Manager, for any question marks or red errors on devices.
Go to your offical motherboard website and download the latest drivers for your Operating System (making sure it's 64 bit if your OS is 64 bit). Repeat for the graphic card drivers and others you might use.
If none of that worked, worst case: That could also be a sign of physical hardware failure.
what cooler do you have?
either, get a h105 or better cooler for it, or underclock it to 3.5ghz or lower to keep it cool
lower it to 1.2v and underclock, then start overclocking again
in small steps testing each time for 15+min and watch the temps
temps low, unstable = raise core voltage (+.05v)
temps low, stable = raise cpu multi (+1)
temps high, stable = lower core voltage (-.05v)
temps high, unstable, = go back to last stable and stop overclocking
take notes on your voltage, multi and max temps
max temp on fx is 62-72c, keep it under 60c if possible
max core voltage on air is around 1.55v
On Mon 9/14/2015 11:55:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091415-4734-01.dmp
This was probably caused by the following module: iomap64.sys (IOMap64+0x1708)
Bugcheck code: 0xC9 (0x226, 0xFFFFF800631B7708, 0xFFFFCF8082AACEA0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\IOMap64.sys
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iomap64.sys .
Google query: iomap64.sys DRIVER_VERIFIER_IOMANAGER_VIOLATION
On Mon 9/14/2015 11:55:08 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iomap64.sys (0xFFFFF800631B7708)
Bugcheck code: 0xC9 (0x226, 0xFFFFF800631B7708, 0xFFFFCF8082AACEA0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\IOMap64.sys
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iomap64.sys .
Google query: iomap64.sys DRIVER_VERIFIER_IOMANAGER_VIOLATION
On Mon 9/14/2015 11:52:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091415-26953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0xF7 (0x26FBBF80F8A0, 0xF88453AA801, 0xFFFFF077BAC557FE, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 9/14/2015 11:50:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091415-27046-01.dmp
This was probably caused by the following module: iomap64.sys (IOMap64+0x1708)
Bugcheck code: 0xC9 (0x226, 0xFFFFF800F70CD708, 0xFFFFCF819018AEA0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\IOMap64.sys
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iomap64.sys .
Google query: iomap64.sys DRIVER_VERIFIER_IOMANAGER_VIOLATION
also i got my temps below 60.
Your current OS installation is stuffed due to overclocking, just lowering the clocks will not uncorrupt the files affected.
Reinstall Windows.
Do not overclock it again as it cannot handle it.
Easy. :-)
underclock the cpu to 3ghz in bios then install windows