Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: jocrp6 on August 09, 2010, 09:47:15 PM
-
Description
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80002da9700, 0xfffff88005fe9e60, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080710-7956-01.
Description
Faulting application name: aceshigh.exe, version: 0.0.0.0, time stamp: 0x4c5078b8
Faulting module name: d3d9.dll, version: 6.1.7600.16385, time stamp: 0x4a5bd9a9
Exception code: 0xc0000005
Fault offset: 0x0001dbe8
Faulting process id: 0xef8
Faulting application start time: 0x01cb36a77093adf6
Faulting application path: C:\Hitech Creations\Aces High\aceshigh.exe
Faulting module path: C:\Windows\system32\d3d9.dll
Report Id: ca94e531-a29a-11df-a155-6cf049087007
Description
Faulting application name: aceshigh.exe, version: 0.0.0.0, time stamp: 0x4c5078b8
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29c
Exception code: 0xc0000005
Fault offset: 0x0005053b
Faulting process id: 0xca0
Faulting application start time: 0x01cb362ddd39fda5
Faulting application path: C:\Hitech Creations\Aces High\aceshigh.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 72a1f9fd-a221-11df-9514-6cf049087007
-
Note the faulting module as being d3d9.dll. That is the DirectX module. Basically, this could be memory related, or video card (driver or hardware) related.
-
Skuzzy I had the same prpoblem with my other comp and come to find out it was the MB getting ready to STB.
-
seems like it all hit the fan after the new patch! so I removed Aces high reinstalled with high resolution package!
It got so bad, my comp would not even boot! reset defaults in bios, still no boot, let windows do a restore from the repair screen! seems all is fine now, I guess a bad OC caused it? but I had been running it for month's that way!
any Ideas on what might have corrupted OS? I am on 2 Intel SSD's on a RAID-0
-
any Ideas on what might have corrupted OS?
Sure, bad sector on a drive, bad memory chip on a ram module, virus, file compression algorithm, erroneous registry entry, extraction/installation of corrupted files into system files, corrupted software installer, improper shutdown routine, power surge, Symantec products, McAfee products, and the list goes on...
-
You have the operating system on an SSD? That will do it right there. Give it enough time, and those SSD's will fail. Put the OS on it and they will fail that much faster.
-
Skuzzy you alamist you. SSD's are a beautiful thing. Any drive can be corrupted over time unless you are diligent. SSD and OS are meant for each other. Unless you don't do your homework and set them up right, they will last years. Maybe not as long as spin drives, but long bleeping enough.
-
Depends on the SSD and the operating system. If the SSD does not support leveling, it will slow to a crawl over a short period of time. If the OS is not Windows 7, leveling is not supported.
Placing the OS and page file on an SSD is not a good idea. Never has been.
By the way, I am not an alarmist. I am an electrical engineer. I am methodical. I am not a bleeding edge enthusiast, yet my home computer is overclocked. It has never had an error in the 2+ years it has been running. It still boots in 4 seconds flat, and does not need an SSD to do so.
-
Well I've had way more luck out of the SSd's in a RAID-0 than spin drives! and if this is my first glitch in 4 months i'll take It! and with a simple restore fixed it.
Windows7 64,
Q9550 OC 3.4Ghz
4Gig OCZ DDR3@1600 FSB
-
If you have problems with hard drives, after only a few months, then you are either getting some really junky drives, or you have a system problem that extends beyond the surface issues you are having.
I assume you are not using an onboard RAID chip, as those are really just there for marketing purposes only. They do not handle errors correctly. None of them do. What add-on RAID board are you using?
I would be rather disturbed if my system got the error yours got to begin with. I would be even more disturbed if a "restore" seemed to fix it. As a "restore" has a tendency to make a bigger mess of many things than it usually fixes. The Windows "restore" only undoes changes to the Windows binaries. All the data files and other applications can get screwed up by a restore.
The biggest issue is, you have no idea what really caused the problem, which usually means it will happen again and continue to keep on happening until you do figure out why it happened. Maybe you are okay with that. It would drive me nuts though.
-
Aw,Man! here we go again! no it's not a adon RAID, It's built into motherboard (Gigabyte P-45 chipset) and no! didn't fix it! threw windows7 back in and did an upgrade as not to loose anything (Files)! Now it's fixed! for now! and lightning fast! another question? what makes the lights stay on on my CH stick after comp powered down? wondering if that might be causing something,
after powering down now, I'm actually turning off powersupply switch!
-
USB stays powered on when "shut down" so the you can turn the PC back "on" by double-clicking a mouse or typing in a password. Check you bios for options to do so.