BSOD chrash

Only 1 memory dump in the uploaded files - this may not be enough to solve your problem, but we'll give it a try!

I've noted that there are older BlueSolei Bluetooth drivers on your system. We've had issues with this recently, especially if older versions have been installed on the system.

And, the sole dump file blames the IVT BlueSolei software - so please uninstall it completely.

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:

amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA) - update from Windows Update
SYMDS64.SYS         Tue Dec 07 19:16:58 2010 (4CFECE7A)
vbtenum.sys         Mon Mar 05 07:17:00 2007 (45EC0A3C)
BTHidMgr.sys        Mon Mar 05 07:17:15 2007 (45EC0A4B)
AtiPcie.sys         Mon Aug 24 04:25:26 2009 (4A924E76)
mwlPSDFilter.sys    Tue Jun 02 06:07:30 2009 (4A24F9E2)
Ironx64.SYS         Fri Nov 12 18:06:50 2010 (4CDDC88A)
atikmpag.sys        Mon Mar 29 07:46:26 2010 (4BB09312)
mwlPSDVDisk.sys     Tue Jun 02 06:15:29 2009 (4A24FBC1)
mwlPSDNServ.sys     Tue Jun 02 06:07:39 2009 (4A24F9EB)
k57nd60a.sys        Tue Jun 08 07:40:13 2010 (4C0E2C1D)
btnetdrv.sys        Mon Mar 05 07:18:08 2007 (45EC0A80)
connctfy.sys        Thu May 27 05:19:35 2010 (4BFE3927)
VComm.sys           Mon Mar 05 07:17:28 2007 (45EC0A58)
amdiox64.sys        Thu Feb 18 10:17:53 2010 (4B7D5A21)
atipmdag.sys        Mon Mar 29 08:26:02 2010 (4BB09C5A)
VcommMgr.sys        Mon Mar 05 07:17:48 2007 (45EC0A6C)
blueletaudio.sys    Mon Mar 05 07:16:09 2007 (45EC0A09)
BlueletSCOAudio.sys Mon Mar 05 07:16:23 2007 (45EC0A17)
athrx.sys           Thu Jul 01 16:27:36 2010 (4C2CFA38)
SynTP.sys           Thu Dec 10 21:30:38 2009 (4B21AECE)
RtHDMIVX.sys        Wed Dec 02 01:33:25 2009 (4B160A35)
dc3d.sys            Tue Dec 14 06:09:28 2010 (4D075068)
point64.sys         Tue Dec 14 06:09:25 2010 (4D075065)
psi_mf.sys          Wed Sep 01 03:53:14 2010 (4C7E066A)
btcusb.sys          Mon Mar 05 07:16:40 2007 (45EC0A28)

http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#SYMDS64.SYS
http://www.carrona.org/dvrref.html#vbtenum.sys
http://www.carrona.org/dvrref.html#BTHidMgr.sys
http://www.carrona.org/dvrref.html#AtiPcie.sys
http://www.carrona.org/dvrref.html#mwlPSDFilter.sys
http://www.carrona.org/dvrref.html#Ironx64.SYS
http://www.carrona.org/dvrref.html#atikmpag.sys
http://www.carrona.org/dvrref.html#mwlPSDVDisk.sys
http://www.carrona.org/dvrref.html#mwlPSDNServ.sys
http://www.carrona.org/dvrref.html#k57nd60a.sys
http://www.carrona.org/dvrref.html#btnetdrv.sys
http://www.carrona.org/dvrref.html#connctfy.sys
http://www.carrona.org/dvrref.html#VComm.sys
http://www.carrona.org/dvrref.html#amdiox64.sys
http://www.carrona.org/dvrref.html#atipmdag.sys
http://www.carrona.org/dvrref.html#VcommMgr.sys
http://www.carrona.org/dvrref.html#blueletaudio.sys
http://www.carrona.org/dvrref.html#BlueletSCOAudio.sys
http://www.carrona.org/dvrref.html#athrx.sys
http://www.carrona.org/dvrref.html#SynTP.sys
http://www.carrona.org/dvrref.html#RtHDMIVX.sys
http://www.carrona.org/dvrref.html#dc3d.sys
http://www.carrona.org/dvrref.html#point64.sys
http://www.carrona.org/dvrref.html#psi_mf.sys
http://www.carrona.org/dvrref.html#btcusb.sys

BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-30201-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 24 07:49:39.392 2011 (UTC - 4:00)
System Uptime: 0 days 0:49:50.074
*** WARNING: Unable to verify timestamp for VcommMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for VcommMgr.sys
Probably caused by : VcommMgr.sys ( VcommMgr+6dfe )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  BlueSoleil.exe
FAILURE_BUCKET_ID:  X64_0x3B_VcommMgr+6dfe
Bugcheck code 0000003B
Arguments 00000000`c0000046 fffff800`034c45fc fffff880`0892e9d0 00000000`00000000
BiosVersion = V1.02
BiosReleaseDate = 04/08/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

Don't worry about the language. Your English is much better than my Danish - so I will ask questions if I have trouble translating.

DO NOT update the BlueTooth right now.
First remove it to see if it stops the BSOD's. If it does, then feel free to install the latest version.

Don't worry about the rest of the drivers just yet. We'll see if the BlueSolei is the cause and then we can move on to other things. In many cases I have found that the USB dongle and BlueSolei software does cause a problem - and some users have purchased new equipment to work around these problems. You must use the latest version of the Blue Solei software.

The list of drivers is done automatically by a program that one of the BSOD analysts has written. As such it needs to be interpreted one-by-one in case there are issues.

Don't use the CD, rather use the BlueSolei website to download the latest version.
IVT BlueSoleil

Sometimes software will work for a while until a certain combination of events occurs to cause the problem - then the problem will occur more frequently. You'll often see this when someone blames a Windows Update for causing problems - usually it's not the Windows Update, but rather an outdated program that causes the problem.

Sometimes solving one problem will uncover another problem (such as the freezing that you've described). We handle that by taking the problems one at a time until we've fixed all of them. Hopefully the Blue Solei software replacement will fix both of your problems.

Good Luck!

Sorry for not addressing the heat issue before (I have eye problems).
I'd suggest this free program: Download SpeedFan - Access temperature sensor in your computer

Heat is a hardware error - and we need quite a few memory dumps (at least 4 or 5) to see the lack of a pattern that suggests hardware. Let us know what the temperatures are reading and we'll move on from there.

You can use Prime95 to stress the system and watch for it to overheat:

Prime95 download site: http://www.mersenne.org/freesoft/
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 please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "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).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

It's possible that Windows is damaged - but it is the least likely problem for us to look at. The Windows OS is incredibly robust and very able to repair itself in most situations. FYI, this is the order of things that go wrong IME:
- 3rd party drivers
- incompatible software/malware
- hardware

Wait for another BSOD. While waiting, mark down the approximate time of the freezes. We'll use that to look for errors in the event logs. If it still freezes and doesn't BSOD in 2 days, then make a post stating that and also re-run and upload a new set of reports (like you did in your first post).
- Windows