Another BSOD crash

ZenixNet · 22 Jul 2011

I had alot of issues with BSOD in the past and I though I resolved the issue but apparently not, can someone check out the crash log?
ThanksAttachment 166469

usasma · 25 Jul 2011

This device is disabled:

Pinnacle Marvin Bus 64 ROOT\SYSTEM\0001 This device is disabled.

Please enable the device, uninstall it's software, then remove the device from your system.
This device has had BSOD issues (in the past) with Win7 systems.

MSINFO32 shows a lot of video errors - with some pointing to mctkmd64.sys (most likely belonging to a Magic Control Technology UVTP100 USB to VGA adapter). Please uninstall this device's software, then remove the device from your system. If you're able to find a link for drivers to this device, please post back as we weren't able to locate them here: Driver Reference

If uninstalling and removing the above device doesn't fix things, then we'll have to start testing/updating your video card and it's drivers. Video drivers date from 2009, so it won't hurt to update them now.

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:


nusb3xhc.sys         Thu Jan 21 22:22:21 2010 (4B5919ED)
iaStor.sys           Fri Oct 02 15:58:50 2009 (4AC65B7A)
amdxata.sys          Fri Mar 19 12:18:18 2010 (4BA3A3CA) - update through Windows Update
PxHlpa64.sys         Tue Jun 23 19:16:35 2009 (4A416253)
vpcvmm.sys           Sat Nov 20 06:35:48 2010 (4CE7B294)
rdpdispm.sys         Thu Aug 19 19:20:11 2010 (4C6DBC2B)
vpcnfltr.sys         Sat Nov 20 06:35:20 2010 (4CE7B278)
hcw72DTV.sys         Fri Apr 23 11:54:30 2010 (4BD1C2B6)
LHidEqd.Sys          Tue Aug 24 13:21:26 2010 (4C73FF96)
hcw72ATV.sys         Fri Apr 23 11:50:38 2010 (4BD1C1CE)
MpFilter.sys         Tue Sep 14 20:19:28 2010 (4C901110)
HECIx64.sys          Thu Sep 17 15:54:16 2009 (4AB293E8)
vpcusb.sys           Sat Nov 20 06:35:31 2010 (4CE7B283)
usbrpm.sys           Sat Nov 20 06:37:19 2010 (4CE7B2EF)
k57nd60a.sys         Thu Aug 06 07:44:32 2009 (4A7AC220)
GEARAspiWDM.sys      Mon May 18 08:17:04 2009 (4A1151C0)
wacomvhid.sys        Wed May 20 15:53:55 2009 (4A145FD3)
serscan.sys          Mon Jul 13 20:35:32 2009 (4A5BD2D4)
vpchbus.sys          Sat Nov 20 06:35:38 2010 (4CE7B28A)
nusb3hub.sys         Thu Jan 21 22:22:18 2010 (4B5919EA)
wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)
AtiHdmi.sys          Sun Aug 23 08:35:11 2009 (4A91377F)
dump_iaStor.sys      Fri Oct 02 15:58:50 2009 (4AC65B7A)
LMouFilt.Sys         Tue Aug 24 13:21:43 2010 (4C73FFA7)
IntcDAud.sys         Sat Sep 26 10:42:55 2009 (4ABE286F)
usbcir.sys           Mon Jul 13 20:06:36 2009 (4A5BCC0C)
hcw72ADFilter.sys    Fri Apr 23 11:47:45 2010 (4BD1C121)
LEqdUsb.Sys          Tue Aug 24 13:21:23 2010 (4C73FF93)
LHidFilt.Sys         Tue Aug 24 13:21:36 2010 (4C73FFA0)
adfs.SYS             Thu Jun 26 16:52:37 2008 (48640195)
pcdsrvc_x64.pkms     Sun May 02 23:01:16 2010 (4BDE3C7C)
MpNWMon.sys          Tue Sep 14 20:19:30 2010 (4C901112)
NisDrvWFP.sys        Tue Sep 14 20:20:25 2010 (4C901149)
truecrypt.sys        Sun Sep 05 10:23:16 2010 (4C83A7D4)
rtl819xp.sys         Mon Feb 01 07:30:51 2010 (4B66C97B)
LVPr2M64.sys         Fri May 07 21:38:16 2010 (4BE4C088)
atikmdag.sys         Fri Sep 18 22:44:52 2009 (4AB445A4)

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072211-53055-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul 22 23:09:41.740 2011 (UTC - 4:00)
System Uptime: 0 days 3:03:10.792
Probably caused by : ntkrnlmp.exe ( nt!EtwpFindGuidEntryByGuid+72 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmpnetwk.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!EtwpFindGuidEntryByGuid+72
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`03aceae3 fffff880`0bb040a0 00000000`00000000
BiosVersion = A05
BiosReleaseDate = 07/08/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061111-46004-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 12:51:51.039 2011 (UTC - 4:00)
System Uptime: 0 days 15:26:16.070
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+1269c )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys
Bugcheck code 00000116
Arguments fffffa80`07700150 fffff880`0acb469c 00000000`00000000 00000000`00000002
BiosVersion = A05
BiosReleaseDate = 07/08/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

ZenixNet · 25 Jul 2011

Wow! Thanks for all that information! I going through the list now but I've noticed there are some things in there that I don't even know what the driver is for; such as the ones form VMware. Also the one that says Windows update I don't have an update for. Anyway, I'll keep updating as many drivers as I can and get back to this topic if I have any more issues.

EDIT: I've found even more drivers that I have no idea what they go to, such as "mctkmd64.sys". I'm considering a clean install to start over fresh and only install the newest drivers for what I am using now, though it may take some time to gather up all my devices and find there newest drivers.

ZenixNet · 25 Jul 2011

Got another crash when going into sleep mode...Attachment 167003

ZenixNet · 25 Jul 2011

A year or 2 ago I bought a Dell XPS 8100, I'm a huge fan of Dell and always have good experiences but this is the exception. This computer has given me nothing put problems.
I can't tell you have many days I've spent trying to fix BSOD's. I remember for an entire weekend that's all I did. I have posted countless crash reports, logs, etc. on these forums.
Getting BSOD's when sleeping, randomly, when going to YouTube, etc etc etc.
My ATI card (never again will I but something ATI) also gives me a lot of trouble. I spent an entire day removing ever trace of ATI driver to do a clean install and time and time again it still causes crashes.
This computer also has alot of little stuff that annoys the hell out of me.
I can't stand this machine.

Now that my ranting is done, I need some suggestions on how to take care of this dam computer. In my latest crash ( https://www.sevenforums.com/crashes-d...ml#post1506705 )
USASMA gave me a list of many drivers involved in the crash and when going through them I have no idea what many of them go to. Some are from things I don't use anymore.

My thought on how to fix this is to throw this dam computer out the window and buy/build a new machine, but I don't currently have the money for that. So, my other thought is a clean install. So, should I take the clean install path or is there a better route? If so can anyone give me tips such as the best way to collect the newest drivers for all my equipment.

Thanks everyone for you help trying to fix my previous crashes over the years. I hop I can finally get this dam thing fixed once and for all.
(I know this isn't the BSOD section but here are my two latest crashes if anyone wants to check them out: Attachment 167004 Attachment 167005)

Magron · 25 Jul 2011

I'm a real ATI hater and I'm willing to blame all your problems on it. Their drivers suck, always have sucked and apparently always will suck.

If you can swing it, dump it and put in an nvidia.
A clean load will definitely remove all doubt if it's a hardware problem and it sounds like you're at that point. Go for it.

profdlp · 25 Jul 2011

Can you post a quick list of what you have tried so far?

If it's not on the list as "been there, done that", I'd give Memtest86+ - Advanced Memory Diagnostic Tool a couple go-rounds. :)

Beta · 25 Jul 2011

Try removing the GPU and reseat it also remove all but one stick of ram and then boot. At this point do something such as run a program that would cause the bluescreen. Then if it does it remove the one stick and replace it with another. Then repeat. If it does not bluescreen then its the ram....

Post after that is done and we will see where you are at.

ZenixNet · 25 Jul 2011

Beta said:

Try removing the GPU and reseat it also remove all but one stick of ram and then boot. At this point do something such as run a program that would cause the bluescreen. Then if it does it remove the one stick and replace it with another. Then repeat. If it does not bluescreen then its the ram....

Post after that is done and we will see where you are at.

The thing is, nothing always causes a BSOD for me. It's always random. Not one thing always causes it. Sometimes its going to sleep, sometimes its watching you tube, sometimes its playing games, sometimes I'm not doing anything. Sometimes I get 1 or 2 BSOD and then I don't get another for a few months. Sometimes I get nothing but BSOD for a week and then none for a while.

usasma · 26 Jul 2011

IMO there's no such thing as a random BSOD - it's just a BSOD that we haven't discovered what's causing it. I worked for months on my son's computer with BSOD's only to find that the dialup modem (which we don't use) was causing the problem.

Obviously the purchase of a new machine will get rid of these problems when you toss the old machine in the garbage.
Reinstalling Windows will get rid of any Windows problems that may exist - but getting a clean Windows-only installation is a bit more difficult than just reinstalling.
But, there are numerous other things that can go wrong. In general we look for these types of problems in this order:
- 3rd party drivers
- compatibility/malware issues
- hardware problems
- Windows problems

Don't worry about the drivers for now - they're in generally good shape (with the exception of the wacommousefilter.sys driver from 2007). What we're going to do now is to look for hardware issues - and to see if we can force a Driver Verifier enabled memory dump. I suspect video - but am not entirely sure of where in the video sub-system that the error is coming from (hardware/software/other).

This memory dump was a bit different from the others, as it blames a driver involved in the hibernation process. In the old days (WinXP) an error like this was due to video drivers - but it's not that simple with Vista or Win7 as other drivers get involved (such as storage drivers) And storage drivers are implicated here because the hibernation driver was extracted from your storage driver iaStor.sys

So, try these free diagnostic/stress tests as you have time (the tests after Prime95 are optional):

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:

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: Free Online AntiMalware Resources (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, 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).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
- 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

More Video Stress Tests:
1. Thanks to VirGnarus for finding this test: https://simtk.org/home/memtest
2. 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.
3. Another interesting test that came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!

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

Also try running Driver Verifier according to these instructions. Bring the system in and out of Hibernation/Sleep in order to try and force a BSOD:

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 "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, Win7):
        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__\072511-79451-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jul 25 20:52:13.002 2011 (UTC - 4:00)
System Uptime: 2 days 21:41:19.937
BugCheck D1, {2c0, 2, 0, fffff8800be5da25}
*** WARNING: Unable to verify timestamp for hiber_iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for hiber_iaStor.sys
Probably caused by : hiber_iaStor.sys ( hiber_iaStor+56a25 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_hiber_iaStor+56a25
Bugcheck code 000000D1
Arguments 00000000`000002c0 00000000`00000002 00000000`00000000 fffff880`0be5da25
BiosVersion = A05
BiosReleaseDate = 07/08/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Another BSOD crash

Another BSOD crash

My computer refuses to work.