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

"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

Click to expand...

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/Win7 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.

Click to expand...

d137z said:

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

Click to expand...

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.

Click to expand...

d137z said:

There is ALOT of errors in there , mustly its seems when something stopped working .
I only have USB keyboard and mouse installed
my computer is built by my self and its completely new , never had it to run as it should .
so the waranty is on the single parts alone . Thats why I need to tack down the problem so I can send the defect part back or ofc. fix it in another way.

here is a post of an arror in the viewer from internet expolerer crashing , witch is one of the newest errors.
Faulting application name: iexplore.exe, version: 9.0.8112.16421, time stamp: 0x4d76255d
Faulting module name: kernel32.dll, version: 6.1.7601.17651, time stamp: 0x4e211318
Exception code: 0xc000001d
Fault offset: 0x0002d292
Faulting process id: 0xd84
Faulting application start time: 0x01ccda17706c3e06
Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe
Faulting module path: C:\Windows\syswow64\kernel32.dll
Report Id: 48a13a9a-460c-11e1-a3a6-5404a61f3260

yesteday I ran Prime95 with bluetooh disable`s and only 1 ram block in the computer ,
ended up with a BSOD and a dump file is attach`ed.
"whocrashed" found 2 problem`s :
ntoskrnl.exe
ntkrnlmp.exe

The hidclass.sys BSOD is gone after I disable`d bluetooh and have`nt seen it since .
though my computer seems to get worse since I have`nt experinced internet explorer crash`s before untill now

HERE IS A SUM`UP WHAT i HAVE DONE SO FAR.
Format c: after first problem`s
Used 2 different SDD`s with 2 different win 7x64 install`s to see if it was the SDD
MEMTEST86 with all 4 ram blocks = 1 error
MEMTEST86 with 1 ram block = 0 error (on all 4 block`s)
INTELburntest for CPU stress test = stable on "standard" and "high" settings, unstable at "very high"
Furmark for GPU stress test on standard settings= stable FPS no crash . On extreme burn setting`s = Stable FPS no crash.
Prime95 with different RAM block`s = Allways getting the same error`s
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.

Click to expand...

d137z said:

Okay i Will . a Quick quastion you Want me to run memtest86 ? Or dó you mean another program. Coz i cant take screenshots in memtest86 ?

Click to expand...

d137z said:

hello again.
And thank you for all the help , I found out for about 30 min ago that there was a swich on the MB that whould automaticlig OC the ram . and for some reason it was on "enable" I turned it off and didnt get any error`s in prime95 for the first time .

SO SO SO I really hope that this was my problem witch it seems to be , I had allmost sent the MB back to the seller

im sorry I kinda wasted you guys time , my thank you anyway !
I will keep looking at the site since it started to interrest me with all the dmp file`s and stuff like that
so maybe we will talk later

for now bye

Click to expand...