Constant BSOD (WIndows 7 32-bit)

Are you connected to the internet?
Debuggee not connected is normal (for a short while), while the debugger connects to the symbol server at Microsoft.
Since this is the first time you're doing it, I'd leave it for 15 to 20 minutes to see if it connects.

Also, uploading the .zip file will let me run the memory dumps - and that way you'll have something to compare your output to.

Starting 21 memory dumps right now (20:07 my time)

Finished all 21 at 20:27 my time.
Going back and am going to run the last 5 separately (since we ran the first 16 previously).

5 memory dump file over 3 days
4 different BSOD error codes (STOP 0x19 (2), 0xFC, 0x24, 0xA)
at least 2 different causes.
This is (IMO) most likely a hardware problem.

So, let's start with this:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:

Code:

AtiHdmi.sys     Thu May 06 05:19:48 2010 (4BE289B4)
http://www.carrona.org/dvrref.html#AtiHdmi.sys 
dsfksvcs.sys    Mon Feb 08 22:35:54 2010 (4B70D81A)
http://www.carrona.org/dvrref.html#dsfksvcs.sys 
DSFOleaut32.sys Mon Feb 08 22:35:53 2010 (4B70D819)
http://www.carrona.org/dvrref.html#DSFOleaut32.sys 
amdxata.sys     Tue May 19 13:57:35 2009 (4A12F30F)
http://www.carrona.org/dvrref.html#amdxata.sys 
dsfroot.sys     Mon Feb 08 22:35:56 2010 (4B70D81C)
http://www.carrona.org/dvrref.html#dsfroot.sys 
atikmpag.sys    Tue Jul 06 21:15:23 2010 (4C33D52B)
http://www.carrona.org/dvrref.html#atikmpag.sys 
atikmdag.sys    Tue Jul 06 21:34:15 2010 (4C33D997)
http://www.carrona.org/dvrref.html#atikmdag.sys 
HECI.sys        Thu Sep 17 15:54:12 2009 (4AB293E4)
http://www.carrona.org/dvrref.html#HECI.sys 
RTKVHDA.sys     Thu Dec 03 08:33:36 2009 (4B17BE30)
http://www.carrona.org/dvrref.html#RTKVHDA.sys 

Then try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in 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

Prime95 download site: 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 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

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Debug session time: Sat Feb 19 11:10:51.612 2011 (UTC - 5:00)
System Uptime: 0 days 5:49:57.720
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x19_3_nt!ExDeferredFreePool+336
Bugcheck code 00000019
Arguments 00000003 aa94a9f0 aa94a9f0 aa94abf0
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 10:33:13.723 2011 (UTC - 5:00)
System Uptime: 0 days 1:03:25.832
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME:  explorer.exe
Bugcheck code 000000FC
Arguments 98279c10 448f9963 98279b68 00000002
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 07:03:16.444 2011 (UTC - 5:00)
System Uptime: 0 days 0:55:02.942
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  0x24_Ntfs!NtfsReleaseFcb+29
Bugcheck code 00000024
Arguments 001904fb 8a2f9714 8a2f92f0 8888d6cd
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 11:31:13.170 2011 (UTC - 5:00)
System Uptime: 0 days 2:23:02.278
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wlschost.ex
FAILURE_BUCKET_ID:  0x19_3_nt!ExDeferredFreePool+336
Bugcheck code 00000019
Arguments 00000003 9e91eb68 9e91eb68 9e91e968
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 09:05:32.631 2011 (UTC - 5:00)
System Uptime: 0 days 0:43:07.114
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  VSSVC.exe
FAILURE_BUCKET_ID:  0xA_nt!KiTrap0E+2cf
Bugcheck code 0000000A
Arguments 00000234 00000002 00000001 82c15829
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

Don't worry about amdxata.sys for now - it's probably updated via Windows Update (if available).
This is most likely a hardware problem - but we keep working on the drivers while trying out the different hardware tests.

Try Prime95 with the Small FFT test and then with the Large FFT test. Here's a DRAFT of my suggestions about Prime95:

DRAFT Prime95 testing procedure
This is in case you are getting errors in Prime95 and want to nail down the cause

Run HDD diag and MemTest prior to Prime95

Run Blend test
Run Inplace Large FFT's test
Run Small FFT's test

Run CPU Stress Tests
- http://downloadcenter.intel.com/Deta...19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld - PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface - XtremeSystems Forums

Run Video Stress Tests
- FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
- МИРNVIDIA / Утилиты / VMT
- МИРNVIDIA / Утилиты / Artifact Locator

Swap RAM sticks around per Steps 7 through 10 of this link and run Prime95 (in Blend mode) on each stick/slot: Memory Diagnostics
This is because of issues found in this topic: https://www.sevenforums.com/crashes-d...ml#post1076674
************************
DISCUSSION:
Small FFT's test CPU cache and very little memory.
Large FFT's access' a lot of memory - but in-place option keeps it limited
Blend is not run in-place, so it cycles the tests through a lot of RAM

All tests stress the CPU
In-place large FFT's and Blend also test CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- This would then be testing the memory controller onboard the CPU in the Athlon64 and i-series processors
In-place large FFT's stress CPU more than Blend
MemTest is better at testing RAM

Prime 95 tests 3 things:
- Memory
- CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- CPU

FWIW - the distinction between RAM and different types of memory in the system is one that I've made. The documentation that I've read speaks of RAM issues and CPU cache - and doesn't mention the other aspects. BUT, this is just speculation on my part, so we'll have to see how it works for us.
Link to explanation about i-series CPU/RAM interface: Intel Core - Wikipedia, the free encyclopedia

Common features of all Nehalem based processors include an integrated DDR3 memory controller as well as QuickPath Interconnect or PCI Express and Direct Media Interface on the processor replacing the aging quad-pumped Front Side Bus used in all earlier Core processors.

3 memory dumps over 2 days
3 different BSOD error codes
At least 2 different causes are blamed.
I'm nearly certain that this is a hardware problem. Let's see the results of the Prime95 tests and move on from there.

OLDER DRIVERS PRESENT IN THE DUMP FILES

- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system (you don't have to redo the one's that you've already updated).
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:

Code:

dsfksvcs.sys       Mon Feb 08 22:35:54 2010 (4B70D81A)
DSFOleaut32.sys    Mon Feb 08 22:35:53 2010 (4B70D819)
amdxata.sys        Tue May 19 13:57:35 2009 (4A12F30F)
dsfroot.sys        Mon Feb 08 22:35:56 2010 (4B70D81C)
HECI.sys           Thu Sep 17 15:54:12 2009 (4AB293E4)
Rt86win7.sys       Thu Aug 20 12:04:54 2009 (4A8D7426)
AtihdW73.sys       Wed Nov 17 07:00:47 2010 (4CE3C3EF)
FoxAwdWINFLASH.SYS Wed May 30 05:43:02 2007 (465D4726)
pcwiz_x32.sys      Fri Jul 09 07:18:04 2010 (4C37056C)

http://www.carrona.org/dvrref.html#dsfksvcs.sys
http://www.carrona.org/dvrref.html#DSFOleaut32.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#dsfroot.sys
http://www.carrona.org/dvrref.html#HECI.sys
http://www.carrona.org/dvrref.html#Rt86win7.sys

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 10:46:30.829 2011 (UTC - 5:00)
System Uptime: 0 days 0:35:53.327
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  0x50_nt!KiTrap0E+dc
Bugcheck code 00000050
Arguments 9e078000 00000001 82c4b7f3 00000000
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Debug session time: Sun Feb 20 15:11:55.146 2011 (UTC - 5:00)
System Uptime: 0 days 1:08:46.645
BUGCHECK_STR:  0xc000021a_csrss.exe_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  0xc000021a_csrss.exe_c0000005_nt!KiFastCallEntry+12a
Bugcheck code C000021A
Arguments a61682f8 c0000005 7604c461 00c3ef1c
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Debug session time: Sun Feb 20 14:02:09.624 2011 (UTC - 5:00)
System Uptime: 0 days 6:04:27.742
Probably caused by : memory_corruption ( nt!MiUpdateWsle+1ab )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0xA_nt!MiUpdateWsle+1ab
Bugcheck code 0000000A
Arguments c08120a4 00000000 00000000 82caf51d
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``