Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD or "a problem caused the program to close" in games win7x64


22 Jan 2012   #1

Windows 7 ultimate x64
 
 
BSOD or "a problem caused the program to close" in games win7x64

Hello everybody , I really hope someone can help me couse this new pc is helll expensive.

ok first a bit about my problem.

When I play games , my game will crash after a while from 5min to 2hours.
in Battlefied 3 I get BSOD screen but in league of legends and Starcraft 2 the game will close and say "a problem caused the program to close" etc.

I have format c: my computer two times now , on two different SDD`s both are doing it.
This night I ran a MEMTEST86 on all four block it found 1 error .
After that I took each block for a test 1 by 1 zero error`s

Im pretty sure im uptodate with every single driver in my computer since I have bin using maybe 40 hours allready to make the computer run as it should.

I have allso tryed to disable my onboard soundcard (realtek) and played Battlefied3 for 2 hours after a crash.

HERE IS MY SYSTEM INFOMATION:
CPU: Intel core i7-2700 3.50 ghz
MB: P8z68-vPRO/GEN3
SSD: Samsung 830 series 256gb
RAM: 12 gb ddr3 crosair CL8 4x4gb
GFC: ASUS GTX590 (useing new nvidia driver)
OS: WIN 7x64 (full updated service pack 1 etc)

I get different set up dumps.
I uploaded the dmp files.
Cheers out there.
Martin Dietz.

My System SpecsSystem Spec
.

22 Jan 2012   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Hello there,
Quote:
"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
My System SpecsSystem Spec
22 Jan 2012   #3

Windows 7 ultimate x64
 
 

thank you for the reply , I tryed furmark for grafic card stress test , no problems where shown. It ran though the test.

allso ran intelburntest without any problems

So my problem is still there
My System SpecsSystem Spec
.


22 Jan 2012   #4
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

We now wait to examine the next DMP to see if anything further is revealed...
My System SpecsSystem Spec
22 Jan 2012   #5

Windows 7 ultimate x64
 
 

okay , I ran prime95 with 8 threads , and I ended up with a BSOD

the dump file attach`ed

results of the test from prime95:

[Sun Jan 22 22:24:07 2012]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4995517731, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4921875, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Resulting sum was -3.169466379769477e+016, expected: 3681151461364212
Hardware failure detected, consult stress.txt file.

allso did the last step`s
the system file checker sfc.exe/scannow
and a picture is attach`ed aswell
My System SpecsSystem Spec
22 Jan 2012   #6
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Your crash was caused by a misbehaving driver.
Please run Driver Verifier...

Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
23 Jan 2012   #7

Windows 7 ultimate x64
 
 

OKAY so I used the verifier , booted up as normaly and entered Battlefied 3 with a BSOD stright away .
I didnt get any infomation about the driver tho windows or "who cashed" but I have a dump file for you

I can see a driver in Verifier that never bin loaded called nvbrigde.kmd
all other`s says "loaded"

and so fare so good im really glad for your help.
My System SpecsSystem Spec
23 Jan 2012   #8

Windows 7 ultimate x64
 
 

I found out that there was a problem with the driver "hidclass.sys"
I tryed different things disabling USB3.0 etc.
but then I tryed disable the bluethood and my BSOD at battlefied 3 start up while verifier was running stopped
but im still getting a "a problem caused the program to close"
I still have verifier on .
no dump file`s are made from that
and im still getting errors in prime95
My System SpecsSystem Spec
23 Jan 2012   #9
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Your DMPs didn't provide us with much information.

Are you overclocking?
Is your computer under Warranty?
Are you still having the same problem with Prime 95?
My System SpecsSystem Spec
23 Jan 2012   #10

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by d137z View Post
I found out that there was a problem with the driver "hidclass.sys"
I tryed different things disabling USB3.0 etc.
but then I tryed disable the bluethood and my BSOD at battlefied 3 start up while verifier was running stopped
but im still getting a "a problem caused the program to close"
I still have verifier on .
no dump file`s are made from that
and im still getting errors in prime95
What external devices do you have attached? HID (human Interface Device) are external devices (usually) like game controllers, etc.

What is logged in event viewer?


To check for freezing/crashing you need to check several things.

Event viewer.

Quote:
Type eventvwr in search and go to the windows log>application tab & system tabs.
Look for errors. Errors have red in the left hand column.

Look for errors that say app hang, or app crash, or anything related to the problem.
When you find them either take a screenshot of them and upload them to us, or note the event ID and source codes and look them up in google. If you cant find them in google tell us what they are.

You might want to turn verifier off as it in itself can trigger BSOD's. You do that by typing verifier /reset.
My System SpecsSystem Spec
Reply

 BSOD or "a problem caused the program to close" in games win7x64




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:47 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33