BleepingComputer.com: freezing/lockups/usb dropouts during games

CORSAIR Builder Series CX430 V2 430W - $45

Great input guys, here's something strange..

I was playing portal 2 today for like 2 hours straight. Didnt crash, the kyeboard/mouse didnt drop out at all. Just thought ide share that.

Hey guys, i just purchased this : http://www.mittoni.com.au/thermaltake-600w-litepower-psu-p-3346.html

I installed it, played Portal for about an hour, and it crashed again, Bluescreen of Death. The error thats always popping up is 0x0000007f

This also happened with the old PSU, and it corresponds with the USB drop outs.

I guess its not the PSU after all...this is driving me insane.

Ive attached the report, it seems as tho driver named "ntkrnlpa.exe" is the culprit. Ive googled around but haven't come up with anything significant!

This post has been edited by ziadramman: 30 July 2011 - 09:53 AM

Any help at all........ happened 3 times in an hour yesterday while playing wow.

how can no one know what this is caused by?!

Just bought a new Graphics card. installed it, did the Futuremark test, 3 minutes into the test, my USB's dropped out, ALL OF THEM.

Nothing has changed, its not the PSU, its not the Graphics Card....HELP plox

I can't guarantee it but it possibly could be the motherboard.

Hello lets see if we can get this problem resolved.

STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)

This error message can occur if either of the following conditions exists:
Your computer has hardware or software problems (hardware failure is the most common cause).
You try to over clock the speed of your computer's processor (for example, you set a 150 MhZ processor to run at 187 MhZ).
The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal. The most common causes of a STOP 0x7F are:
Low-level hardware corruption, such as corrupt memory (RAM)
Mismatched memory modules
A malfunctioning motherboard
To determine an approximate cause, examine the parameters at the top of the STOP screen:
**STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000, 0x00000000)
UNEXPECTED_KERNEL_MODE_TRAP

The most important parameter is the first one (0x0000000X) which may have several different values. The cause of this trap can vary, depending on the value of this parameter. All traps that cause a STOP 0x7F can be found in any Intel x86 microprocessor reference manual as they are specific to the x86 platform. Here are some of the most common ones:

Values Meaning
---------- --------------------
0x00000000 Divide by Zero Error
0x00000004 Overflow
0x00000005 Bounds Check Fault
0x00000006 Invalid Opcode
0x00000008 Double Fault

Divide by zero error
A divide by zero is caused when a DIV instruction is executed and the divisor is 0. Memory corruption (or other hardware problems) or software failures can cause this.

Overflow
The overflow instruction occurs when the processor executes a call to an interrupt handler when the overflow (OF) flag is set.

Bounds check fault
This fault is generated when the processor, while executing a BOUND instruction, finds the operand exceeds the specified limits. A BOUND instruction is used to ensure that a signed array index is within a certain range.

Invalid opcode
This fault is generated when the processor attempts to execute an invalid instruction. This is generally caused when the instruction pointer has become corrupted and is pointing to the wrong location. The most common cause of this is hardware memory corruption.

Double fault
A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers.

To resolve this issue, use the appropriate method:
If either software or hardware can cause a particular trap, a debug is required to determine which is the cause. If you suspect a hardware problem, try the following hardware troubleshooting steps:
Test the RAM in the computer by running the diagnostic software that is provided by the computer manufacturer. Replace any RAM that is reported as bad. Also, make sure that all the RAM in the computer is the same speed.
Try removing or swapping out controllers, cards, or other peripherals.
Try a different motherboard on the computer.
If you are over clocking the speed of your processor, set it back to the speed at which it is designed to run.
Check with the hardware vendor for any updated hardware drivers or BIOS updates, or both.
For more information on processor faults, consult an Intel processor reference manual.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice.
NOTICE: content above republished with prior written permission

I suggest you try a memory error program such as memtest.

***** A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A
B. If you have only one RAM stick installed......run memtest...1. Download - Pre-Compiled Bootable ISO (.zip)2. Unzip downloaded memtest86+-....iso.zip file.3. Inside, you'll find memtest86+-....iso file.4. Download, and install ImgBurn: http://www.imgburn.com/5. Insert blank CD into your CD drive. 6. Open ImgBurn, and click on Write image file to disc7. Click on Browse for a file... icon:8. Locate memtest86+-....iso file, and click Open button.9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:10. Once the CD is created, boot from it, and memtest will automatically start to run. The running program will look something like this depending on the size and number of ram modules installed:It's recommended to run 5-6 passes. Each pass contains very same 8 tests.This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.The following image is the test results area:The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

Thanks to KeyboardNinja for the content published above.

If you have any further questions, please do not hesitate to ask or contact me via PM.

Bruce.

This post has been edited by MrBruce1959: 11 August 2011 - 05:09 PM