Windows 7 x64 BSOD Assistance Requested

[boneddoctor]

My windows 7 Enterprise 64 bit installation is crashing and I haven't been able to get help from our University IT tech dept. . . . they suggest offloading files and rebuilding the system in 32 bit mode. After googled the minidump error codes and came across the Windows 7 Forum web site, I have followed the instructions detailed from "Windows 7- BSOD Posting Instructions" and have attached the perfmon file and the BSOD Dump and System file collection output files.

Any help would be greatly appreciated . . . . I will forward this info to our IT dept for educational purposes.

System Info:
Windows 7 Enterprise x64
Original OS: XP Pro OEM
Age of system: ~4 y
Age of OS installation(W7): 2 months

 

[usasma]

7 different BSOD errors (out of 12 memory dumps) and over 5 different causes blamed
This is most likely a hardware problem (although compatibility issues can play a part here also).

You can check compatibility here: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

Please try these free hardware diagnostics:

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)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability 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 you may want to 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.

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.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: [url=http://www.carrona.org/dvrref.html]Driver Reference[/url] ).
Please pay particular attention to any dated 2008 or earlier:

ctac32k.sys  Wed Jul 02 04:38:22 2008 - Creative Audio Driver - http://www.carrona.org/dvrref.html#ctac32k.sys
nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia Ethernet Networking Driver (nForce chipset driver) - http://www.carrona.org/dvrref.html#nvm62x64.sys
VMNetSrv.sys Wed Jan 16 06:52:01 2008 - Microsoft Virtual Machine Network  Services Driver - http://www.carrona.org/dvrref.html#VMNetSrv.sys

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  1 10:49:09.171 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:07.343
BugCheck 1000007E, {ffffffffc000001d, fffff80002aa83d0, fffff88002fe6d68, fffff88002fe65d0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 30 15:37:00.000 2010 (UTC - 4:00)
System Uptime: 0 days 4:47:02.958
BugCheck 3B, {c0000005, fffff96000116569, fffff88006cb2e60, 0}
Probably caused by : win32k.sys ( win32k!xxxInternalDoPaint+19 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  sidebar.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Aug 26 09:18:42.301 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:12.473
BugCheck 24, {1904fb, fffff88002fbe738, fffff88002fbdfa0, fffff880012336b8}
Probably caused by : Ntfs.sys ( Ntfs!NtfsUninitializeNtfsMcb+98 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 25 12:40:50.895 2010 (UTC - 4:00)
System Uptime: 0 days 22:30:08.067
BugCheck 24, {1904fb, fffff880085efad8, fffff880085ef340, fffff80002aab000}
Probably caused by : memory_corruption
PROCESS_NAME:  iexplore.exe
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 23 16:17:50.109 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:14.281
BugCheck A, {10bb, 2, 0, fffff80002aa8a3e}
Probably caused by : memory_corruption
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 23 12:02:23.886 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:06.058
BugCheck 4E, {7, 1619ac, 163877, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+16dc6 )
BUGCHECK_STR:  0x4E_7
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 23 11:52:01.378 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:41.566
BugCheck 50, {fffff800026670f0, 8, fffff800026670f0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42837 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  SearchIndexer.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 23 10:23:31.451 2010 (UTC - 4:00)
System Uptime: 2 days 21:23:32.623
BugCheck 3B, {c000001d, fffff80002aa97f0, fffff880089476c0, 0}
*** 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
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Aug 20 12:47:10.829 2010 (UTC - 4:00)
System Uptime: 1 days 0:34:55.000
BugCheck 3B, {c0000005, fffff80002bbaa00, fffff88002541cb0, 0}
*** 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
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Aug 19 11:54:16.565 2010 (UTC - 4:00)
System Uptime: 1 days 2:27:41.248
BugCheck 50, {ffffffffffffffb8, 1, fffff80002ab4eb4, 0}
Probably caused by : hardware ( nt!MiCheckProtoPtePageState+c4 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 18 09:24:01.153 2010 (UTC - 4:00)
System Uptime: 8 days 23:11:49.076
BugCheck A, {28, 2, 0, fffff80002b09410}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchProtocol
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 10:11:28.506 2010 (UTC - 4:00)
System Uptime: 4 days 23:25:21.413
BugCheck 19, {20, fffff8a011d1c250, fffff8a011d1c280, 5030104}
Probably caused by : Ntfs.sys ( Ntfs!NtfsRemoveHashEntry+e2 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]