Very Short HD videos causes Win7 to crash

[kostarae]

Event ID 41 - System Crashes while watching HD video

I just completed my build and I am running Windows 7 Pro 64bit.

If playing a short (1-2 second HD video) that was created by mistake or if I close a video immediately after opening, my computer crashes. There is no BSOD.....screens just go black and system crashes. I have to hard reset.

I am currently running everything stock and don't have any other problems.

My system
i5 750
XFX 4770 512mb vid card
Corsair 650w supply
Intel 40gb SSD
2 X WD Blue 640gb for videos

Is this a known bug? What could be the issue here?

I have uploaded a video of mine which causes my computer to crash if you would like to try on your system. It is a m2ts file (playable in Win7 media player) -- file is less than 3mb

Disc3.m2ts

I just tested on my friends Dell and it runs fine without crashing....maybe something with my Video card?

Event Viewer shows (Event ID 41 - Kernel Power)

 

[valtonray]

hmmm your specs are fine. anyone else have any ideas?

 

[abp1873]

sorry can't help i'm having similar problem when trying to convert xvid to dvd windows 7 shuts down

 

[usasma]

Works fine on my system. If it crashes with no BSOD, it's usually a hardware problem that causes a crash before the memory dump can be captured.

Try these free stress tests:

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.