Games Freeze + Sound Static + BOD

[S.S.Swedish]

Ok So the good news is I stopped getting IRQs.. But now I still have the same freezing problem-- with a different freeze sound. Its really high pitched.. and I got one error so far.. A Kernel_data_inpage_error.. Any thoughts?

[Fum]

What was going on when this happened? You know we like details here.

[S.S.Swedish]

I resintalled everything. Xp- XP Pro.. All great versions.> Windows completely updated. I stil have the other hardware disconnected.. and while I played fear everything ran fine for a couple hours. The error happend during the game Oblivion. It is a system hog and I"m just worried i set my ram timings wrong but I really doubt it. I was in a graphics intense area when it crashed... So i uninstalled it.. reinstalled it and then a bit later i got the second error.. Missing dvr--.dll etc.

[Fum]

Check the Stock Speed Database and try and find your ram. See what timings other guys are using and see how they compare to yours. Perhaps you need to spend some time tweaking timings and memtesting.

 

Since the error doesn't show up for an hour of intense gaming, perhaps heat is also an issue? When the error occurs, what are your temps... vid card, case, mobo, cpu?

 

Also, if Oblivion is as intense as you say (never heard of it, i guess i live under a rock?) then perhaps what's happening is you're beginning to access your swap file, combined with un-optimized ram, that could potentially lead to problems. Next time Oblivion crashes, open up the task manager and have a look at the performance tab. On the bottom left there a menu called "Commit Charge", what does is say your Peak is? That should provide more clues.

[S.S.Swedish]

I would try to give you the peak but it crashes the whole computer and reboots it. I'm wondering if this is a memory/mobo problem. At least i know it's not the hardrive or vid card... I think. My peak right now is 443604.. but thats not with oblivion on.. i'll see what the score is while playing it. So far this is the only game that has crashed me, but its only 1 out of many that i have yet to install.

 

Correction. I just tried it again and it didnt run the game it just errored out with the peak at 612308.

 

And again at 615604

 

**The mem sticks feel cool to the touch and my processor is stayinb right at and below 50.

[Kakarot]

Ok So the good news is I stopped getting IRQs.. But now I still have the same freezing problem-- with a different freeze sound. Its really high pitched.. and I got one error so far.. A Kernel_data_inpage_error.. Any thoughts?

 

I got this static sound once or twice when it did not like my overclock....

weird I know

 

Also, when I push my proc a lil further, my games/benches also lock

 

lowering the oc fixed that for me.

 

gl

[Fum]

Did you find your memory in the stock speed database? Get that stable first. Enable memtest and start with some settings other use. Don't boot into the OS until you've run memtest at least 2 hours with zero errors.

[S.S.Swedish]

I can't seem to find the stock speeds here but I found at least two sources that said they were 3-3-3-8. And before i wiped they passed 12 hours of mem testing without error. But I will try it again with these timings and then if that doesnt work go ahead and use the default ones.. I can't seem to pinpoint this problem other than its either hardware/driver. but i havent installed two of any driver and have the most up to date as far as i know?.

 

Perhaps its just bad memory but i would think memtest would catch it.

 

 

GRRRRR.. i just want a stable system though it has only generally crashed during games so far. heh.

 

nothing seems to be overheating above normal but again i cant seem to run my system in games long enough to get it warm

[S.S.Swedish]

It could be either my timings, drivers or hardware.. Is it possible that this is a damaged motherboard? Or possibly just connected wrongly somewhere?

[watsonte]

I dont know if it would be a damaged motherboard as much of a case in which memory just doesnt seem to like the motherboard for some unknown reason, I have seen it myself with an ASUS and Corsair even after going through the compatibility list and finding memory that worked and so on there are all kinds of things that factor into these errors....It took me 4 months to get my first DFI build completely rock solid and now I dont even touch the Bios...

 

Some things just dont want to work as they should....

 

I guess what I am saying is good luck in finding a solution youre okay with if you think it might be the board RMA it and see if things change if not well pick another solution that best suits you.

[stealthgeek]

more details about he error you posted:

 

Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR

The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.

 

Interpreting the Message

This Stop message has four parameters:

 

Lock type value (0x00000001, 0x00000002, 0x00000003, or page table entry (PTE) address).

I/O status code.

If the lock type is 0x00000001, this parameter represents the current process. If the lock type is 0x00000003, this parameter represents the virtual address.

The virtual address that could not be read into memory.

Frequently, the cause of this error can be determined from the second parameter, the I/O status code. Some common status codes are:

 

0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.

0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks (sectors) on the hard disk.

0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.

0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.

0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination, defective storage controller hardware, or defective disk cabling, or two devices attempting to use the same resources.

For information about other possible status codes that might be returned, see the file Ntstatus.h of the Windows XP Professional Driver Development Kit (DDK). For more information about the DDK, see the Driver Development Kits link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources.

 

Resolving the Problem

The following suggestions are specific to Stop 0x7A errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

 

Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix. For more information about Autochk and Chkdsk, see "Troubleshooting Disks and File Systems" in this book.

Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.

Check the hardware manufacturer's Web site for updates to disk adapter firmware or drivers that improve compatibility. Verify that your disks and controller support the same set of advanced features, such as higher transfer rates. If necessary, select a slower transfer rate if an update is not yet available. Consult your hardware or device documentation for more information.

Important

 

You can install disk controller drivers not present on the Windows XP Professional operating system CD by responding to the following prompt shortly after starting Setup:

Press F6 if you need to install a third party SCSI or RAID driver.

Press F6, and when prompted, provide the appropriate storage controller driver (ATA or SCSI) supplied by the manufacturer.

The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.

Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. For more information about Stop 0x77 messages, see "Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR" earlier in this appendix.

For more information about Stop 0x7A messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x0000007A, and 0x7A.

 

It sounds like a problem with RAM, but I would also give your drives the once over with scandisk. Pay special attention to the drive you use for the page file (usually C if you havent changed it). Also, what hard disk configuration do you have? SCSI/SATA/PATA? RAID? Do you use the onbaord RAID controllers? If so, which ones?

[Guest zoo]

I did have same problem and was solve now. Just i' setup vcore to v1.35 to my X2 4800+ and my system has been stable

 

Tray it, may be you could found the solution.

 

Sorry 4 my bad english, Just i hoppe that anybody understand ths text.

 

Saludos