BSOD's on a new machine

So, what are the specs of the new machine (particularly the mobo and the atom processor)?
What version of Win7 are you running?

Note these items:

unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd

Mm is the Windows Memory Manager

Please upload/attach the minidump files so we can work with them

Try running Driver Verifier using these instructions:

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.

So, I'd suggest that you first backup your stuff 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).

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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

It's more than likely that you have a hardware problem. There are 17 memory dumps in the upload, 9 different STOP error codes, and 8 different causes.

Since one of the causes is related to your Norton/Symantec protection (and there are numerous other suggestions that it's at fault), I'd suggest doing this first:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system
- remove any remnants of Norton using this free tool: Download and run the Norton Removal Tool
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

If that doesn't fix things, then I'd suggest these diagnostic tests:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

If the above tests don't reveal anything, then try these:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS

All drivers appear to be 2009 or later (secdrv.sys and speedfan.sys are older, but that's normal)

Summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 17 23:24:24.333 2010 (GMT-5)
System Uptime: 5 days 11:26:53.608
BugCheck 3B, {c0000005, fffff80002ce2416, fffff88009775b50, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireRundownProtectionCacheAwareEx+26 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ccSvcHst.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 21 04:12:32.661 2010 (GMT-5)
System Uptime: 2 days 12:32:52.063
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88004a6cf9e, fffff8800316a508, fffff88003169d60}
Probably caused by : athrx.sys ( athrx+11f9e )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 28 04:16:16.741 2010 (GMT-5)
System Uptime: 6 days 9:28:36.564
BugCheck 4E, {99, 5a6f2, 2, 9038f}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 28 22:31:31.601 2010 (GMT-5)
System Uptime: 0 days 18:14:20.002
BugCheck 50, {fffffd6f80095aab, 0, fffff80002cd9dff, 7}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 12:09:29.278 2010 (GMT-5)
System Uptime: 4 days 7:52:29.304
BugCheck 3B, {c0000005, fffff960000b88ba, fffff8800777d050, 0}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 13:23:56.146 2010 (GMT-5)
System Uptime: 0 days 0:10:56.547
BugCheck 24, {1904fb, fffff88009a73838, fffff88009a73090, fffff880012d3d10}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  ccsvchst.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 17:41:32.463 2010 (GMT-5)
System Uptime: 0 days 0:28:20.849
BugCheck E3, {fffffa8006190820, fffffa80030b8b60, 0, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1a5e8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iTunes.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 22:04:23.960 2010 (GMT-5)
System Uptime: 0 days 1:59:42.972
BugCheck 50, {fffffa802523f2a0, 0, fffff80002cc3518, 2}
Probably caused by : memory_corruption ( nt!MiGetWsAndInsertVad+b8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 22:25:11.392 2010 (GMT-5)
System Uptime: 0 days 0:20:01.778
BugCheck 109, {a3a039d89a447564, b3b7465eecc14792, fffff80002def396, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 22:58:39.617 2010 (GMT-5)
System Uptime: 0 days 0:32:20.019
BugCheck 3B, {c0000005, fffff88002ce644b, fffff88008f60c70, 0}
Probably caused by : SYMTDIV.SYS ( SYMTDIV+1044b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 13:18:57.615 2010 (GMT-5)
System Uptime: 0 days 0:04:58.001
BugCheck 50, {fffffa814401591b, 0, fffff80002c9fdff, 5}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 13:26:36.777 2010 (GMT-5)
System Uptime: 0 days 0:06:57.163
BugCheck 4E, {99, 2ff36, 3, 34d46}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 13:39:52.011 2010 (GMT-5)
System Uptime: 0 days 0:12:33.412
BugCheck 50, {fffff3200e9d97c0, 0, fffff880012d307a, 7}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  wmplayer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 21:50:25.242 2010 (GMT-5)
System Uptime: 0 days 1:47:24.628
BugCheck D1, {40, 7, 0, fffff880045a362d}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Feb  6 11:43:59.263 2010 (GMT-5)
System Uptime: 0 days 13:52:48.665
BugCheck 3B, {c0000005, fffff8800f0fed1a, fffff88009851810, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+36d1a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Feb  6 11:47:00.666 2010 (GMT-5)
System Uptime: 0 days 0:02:19.068
BugCheck 3B, {c000001d, fffff880011cb79c, fffff8800986e030, 0}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Feb  6 11:49:23.696 2010 (GMT-5)
System Uptime: 0 days 0:01:38.098
BugCheck FE, {6, fffffa8006076c00, 43787254, 0}
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_AssertSig+25 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System