Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSODs on new system


01 Aug 2011   #1

Windows 7 Professional x64
 
 
BSODs on new system

Hi there!

I've built a new system a week ago with the following (all new) components:
- board: MSI P67A GD65 (B3) LGA1155
- CPU: Intel i7 2600K Sandy Bridge Quadcore 3.4GHz
- RAM: Corsair XMS 2x4GB SDRAM-DDR3 1600
- HDD: Western Digital Caviar Black 1TB 7200rpm
- GPU: Nvidia GT560 (on EVGA card)
- PSU: Antec 750W
Windows 7 Professional x64, all drivers updated, Windows Security Essentials.

Since then I'm having several blue screens a day, apparently completely at random.
I've also had a few funny things, like Document Manager has ceased functionning.

Running Driver Verifier twice for about 12hrs with settings as recommended here:
Driver Verifier - Windows 7 & Vista (BSOD-related) - Tech Support Forum
didn't trigger anything.
Also memtest86+ on each RAM stick didn't find anything wrong.

Below is attached the zip with dump files/perfmon report.
Any help you can provide is greatly appreciated.
Thanks.

My System SpecsSystem Spec
.

01 Aug 2011   #2
Microsoft MVP

 
 

23 memory dumps over 6 days - WOW!!!
MSINFO32 relates a variety of memory dump errors, which make me suspect a hardware cause (but could be a low-level driver/malware/or compatibility issue).
Waiting on the memory dumps to finish running.

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
http://www.carrona.org/memdiag.html (read the details at the link)
http://www.carrona.org/hddiag.html (read the details at the link) - Test ALL of the hard drives.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: http://www.carrona.org/malware.html (read the details at the link)
My System SpecsSystem Spec
01 Aug 2011   #3
Microsoft MVP

 
 

There's one Verifier Enabled Memory Dump that indirectly blames your Wacom tablet drivers. Please update them.
The Wacom drivers seem to date from 2007, so updating them is strongly suggested.

I'd start with these free diagnostics:
Quote:
I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Quote:
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) - Test ALL of the hard drives.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)
There are also bootable antivirus disks at this link: Free Online AntiMalware Resources
If these don't turn up anything, then I'd have to suggest running Driver Verifier again with these instructions:
Quote:
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/Windows 7 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 "Special Pool" and "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:
Code:
Delete these registry keys (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
BSOD BUGCHECK SUMMARY
Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080111-15615-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 20:29:05.333 2011 (UTC - 4:00)
System Uptime: 0 days 0:50:16.208
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36103 )
BUGCHECK_STR:  0x1a_3452
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  nvvsvc.exe
FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+36103
Bugcheck code 0000001A
Arguments 00000000`00003452 000007fe`fef67000 fffff700`010822a8 30100001`d841f404
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080111-16972-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 19:36:55.491 2011 (UTC - 4:00)
System Uptime: 0 days 0:23:24.366
Probably caused by : Ntfs.sys ( Ntfs!NtfsCheckExistingFile+5d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!NtfsCheckExistingFile+5d
Bugcheck code 00000050
Arguments fffff280`07b02184 00000000`00000000 fffff880`012f1c5d 00000000`00000007
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-15147-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 13:37:39.269 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:35.144
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindBlockRun+83 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_LINEAR_POOL::FindBlockRun+83
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0554d58b fffff880`02d0c2b8 fffff880`02d0bb10
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-17222-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 13:02:33.635 2011 (UTC - 4:00)
System Uptime: 0 days 1:34:37.400
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
Bugcheck code 00000050
Arguments fffff6f8`50013398 00000000`00000000 fffff800`02e6c31b 00000000`00000005
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-16894-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 11:26:57.895 2011 (UTC - 4:00)
System Uptime: 0 days 3:07:39.769
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 )
BUGCHECK_STR:  0x4E_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x4E_2_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229
Bugcheck code 0000004E
Arguments 00000000`00000002 00000000`001b163e 00000000`0023f7ff 00000000`00000002
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-14913-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 30 22:09:47.551 2011 (UTC - 4:00)
System Uptime: 0 days 2:12:09.315
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+10c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ObReferenceObjectByHandleWithTag+10c
Bugcheck code 00000050
Arguments fffff280`0a8fadc8 00000000`00000000 fffff800`0317d77c 00000000`00000007
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073011-15007-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 30 16:03:03.535 2011 (UTC - 4:00)
System Uptime: 0 days 0:37:16.409
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
Bugcheck code 00000050
Arguments fffff6f8`500142d0 00000000`00000000 fffff800`02e8531b 00000000`00000005
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073011-20311-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 30 15:14:05.536 2011 (UTC - 4:00)
System Uptime: 0 days 0:21:27.410
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
Bugcheck code 00000050
Arguments fffff6f8`806192a0 00000000`00000000 fffff800`02e8631b 00000000`00000005
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073011-16161-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 30 14:27:48.574 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:35.620
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+22d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!CmpKcbCacheLookup+22d
Bugcheck code 00000050
Arguments fffff0a0`00b6eef0 00000000`00000000 fffff800`031665ad 00000000`00000007
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073011-17066-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 30 06:25:31.558 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:07.604
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  nusb3mon.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
Bugcheck code 00000050
Arguments fffff684`003ad170 00000000`00000000 fffff800`02ec031b 00000000`00000005
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072911-21606-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul 29 07:47:12.698 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:17.603
Probably caused by : win32k.sys ( win32k!GetKeyboardLayout+58 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!GetKeyboardLayout+58
Bugcheck code 00000050
Arguments fffff280`0da8b418 00000000`00000000 fffff800`02e511c0 00000000`00000007
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072911-15927-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul 29 07:44:49.737 2011 (UTC - 4:00)
System Uptime: 0 days 0:15:00.643
Probably caused by : win32k.sys ( win32k!UserFindAtom+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!UserFindAtom+22
Bugcheck code 00000050
Arguments fffff0a0`0427546f 00000000`00000000 fffff800`031c099d 00000000`00000007
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072911-20482-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul 29 07:28:34.096 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:07.001
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+d9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!MiCaptureAndResetWorkingSetAccessBits+d9
Bugcheck code 00000050
Arguments fffffa98`0837d458 00000000`00000000 fffff800`02f942a9 00000000`00000005
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072911-20592-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul 29 07:25:34.363 2011 (UTC - 4:00)
System Uptime: 0 days 0:16:21.269
Probably caused by : win32k.sys ( win32k!GetKeyboardLayout+58 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!GetKeyboardLayout+58
Bugcheck code 00000050
Arguments fffff280`0d2e8a18 00000000`00000000 fffff800`02e571c0 00000000`00000007
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072911-20514-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul 28 18:05:57.459 2011 (UTC - 4:00)
System Uptime: 0 days 0:48:35.365
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+469e5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  wisptis.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+469e5
Bugcheck code 00000050
Arguments 000007fe`fbaa219c 00000000`00000008 000007fe`fbaa219c 00000000`00000008
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072811-19344-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu Jul 28 11:50:58.060 2011 (UTC - 4:00)
System Uptime: 0 days 0:17:11.028
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339a3 )
BUGCHECK_STR:  0x1a_3452
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wuauclt.exe
FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+339a3
Bugcheck code 0000001A
Arguments 00000000`00003452 000007fe`fd3d8000 fffff700`010819e8 00000000`00000000
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072811-17487-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu Jul 28 11:27:59.104 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:24.072
Probably caused by : hardware ( dxgmms1!VidSchGetNewSubmissionFenceId+2a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`04239eea fffff880`05bc3298 fffff880`05bc2b00
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072711-15147-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Wed Jul 27 17:31:47.638 2011 (UTC - 4:00)
System Uptime: 0 days 1:33:51.606
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ExAcquireResourceSharedLite+4e
Bugcheck code 00000050
Arguments fffff280`0a140ff8 00000000`00000001 fffff800`02eb6e2e 00000000`00000007
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072711-23992-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Wed Jul 27 14:34:49.559 2011 (UTC - 4:00)
System Uptime: 0 days 0:15:11.527
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`002bb033 00000000`00000002 00000000`002baffe
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072711-16972-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Wed Jul 27 03:15:57.131 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:13.988
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ExDeferredFreePool+100
Bugcheck code 00000050
Arguments fffff0a0`039fbcf0 00000000`00000000 fffff800`02fadf8c 00000000`00000007
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072611-25038-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jul 26 08:13:03.203 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:10.171
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`082bff90 00000000`0000ffff 00000000`00000000
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072611-24336-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jul 26 08:07:55.541 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:14.509
*** WARNING: Unable to verify timestamp for wacomvhid.sys
*** ERROR: Module load completed but symbols could not be loaded for wacomvhid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_22e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_22e_VRF_HIDCLASS!HidpMajorHandler+0
Bugcheck code 000000C9
Arguments 00000000`0000022e fffff880`05b04818 fffff980`06e60dc0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072611-26520-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jul 26 07:08:38.814 2011 (UTC - 4:00)
System Uptime: 0 days 0:12:51.782
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`002dddb4 00000000`00000000 00000000`002bccb4
BiosVersion = V1.9
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
.


02 Aug 2011   #4

Windows 7 Professional x64
 
 

Ok, first my apologies for not reporting back earlier, I've had two hectic days.

I've been through your website and read everything carefully. The tests and actions you recommend (or very similar) are what I've been doing for the past eight days, plus some minor tweaking in the BIOS.
I don't know, maybe it was the end of the day and I was tired, but I felt that this was either leading me nowhere or going to take a decade. So I went back to the BIOS, reset all the parameters to their original values (mostly [Auto]), enabled the XMP feature, picked up the first profile, saved and rebooted.

The computer has been on heavy duty for the past 48 hours (working all day long, rendering at night) and it's a breeze! Before that, I've never had more than two or three hours in the same session without a crash.

I'm not discarding any of your advices and I've bookmarked your site, hoping I'll never have to visit again
Thanks a lot for your time. I'm glad the nightmare is over.
(or is it?)
My System SpecsSystem Spec
02 Aug 2011   #5
Microsoft MVP

 
 

FWIW - the BIOS would be the last thing that we check (unless you'd mentioned changing settings there). So'd we'd have been at this for a long time!

Thanks for letting us know!
My System SpecsSystem Spec
Reply

 BSODs on new system




Thread Tools



Similar help and support threads for2: BSODs on new system
Thread Forum
Regular BSODs on new system BSOD Help and Support
Solved Random BSODs on new system BSOD Help and Support
BSODS on new system BSOD Help and Support
New system, BSODs around BSOD Help and Support
BSODs on new Win 7 x64 system BSOD Help and Support
Many bsods on a new system lately... BSOD Help and Support
BSODs ever since system was started BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 08:44 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33