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: BSOD on first Win 7 RTM now on Win 7 Ultimate


02 Dec 2009   #1

Microsoft Windows 7 Ultimate 64bit
 
 
BSOD on first Win 7 RTM now on Win 7 Ultimate

Hi! guys, I first had Win Xp installed and didn't have any hitches. When I installed Win 7 RTM the BSODs started happening. Thinking it must be a fault with the installation I installed the Win 7 Ultimate hoping that might solve the problem. But the BSODs kept coming.

I attached my minidump folder. Hope it isn't too big. I think it includes every dump file created since I installed the Win 7 Ultimate.

Please help me. This OS looks awesome compared to its predecessors and it is eating me up inside that something this perfect keeps crashing.

My System SpecsSystem Spec
.

02 Dec 2009   #2
Microsoft MVP

 
 

Running the 18 dump files. Will be back with the results shortly....
My System SpecsSystem Spec
02 Dec 2009   #3
Microsoft MVP

 
 

A wide range of BSOD's pointing to:
- video
- storage
- Daemon Tools CD program
- luafv.sys (has something to do with virtualization, but I'm not real sure about this).

I'd start by getting rid of Daemon Tools - it causes many issues with systems. Leave it off while we're troubleshooting the issues. If you want to put it back on afterwards, that's up to you.

I'd also update your video drivers to latest available version available from the nVidia website.

For the storage drivers, I'd update those drivers from the website of the system manufacturer. If Windows 7 drivers aren't available, please post back for further suggestions.

Here's the memory dump summaries:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov 19 08:21:05.830 2009 (GMT-5)
System Uptime: 0 days 0:07:32.532
BugCheck A, {fffffc000273f7b0, 2, 8, fffff8000273f7b0}
Probably caused by : ntkrnlmp.exe ( nt!PpmPerfQueueAction+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wuauclt.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov 19 08:41:52.434 2009 (GMT-5)
System Uptime: 0 days 0:03:23.135
BugCheck D1, {fffffc8004a69820, a, 8, fffff88004a69820}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1ae820 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov 21 12:22:16.087 2009 (GMT-5)
System Uptime: 0 days 4:45:51.788
BugCheck 50, {fffffc8003f5f7f8, 8, fffff88003f5f7f8, 7}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 22 07:47:57.218 2009 (GMT-5)
System Uptime: 0 days 0:28:52.920
BugCheck D1, {fffffc8004c27820, a, 8, fffff88004c27820}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1ae820 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 22 05:44:13.475 2009 (GMT-5)
System Uptime: 0 days 0:06:39.052
BugCheck D1, {fffffc8000e0c318, 2, 8, fffff88000e0c318}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeProcessCompletedRequests+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 22 11:23:41.092 2009 (GMT-5)
System Uptime: 0 days 3:35:05.793
BugCheck 50, {fffffc8001434290, 8, fffff88001434290, 7}
Probably caused by : Ntfs.sys ( Ntfs!memmove+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  skypePM.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Nov 24 21:05:33.071 2009 (GMT-5)
System Uptime: 0 days 1:02:20.631
BugCheck D1, {fffffc8000fcc318, 2, 8, fffff88000fcc318}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeProcessCompletedRequests+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Nov 24 21:13:36.401 2009 (GMT-5)
System Uptime: 0 days 0:07:20.102
BugCheck D1, {fffffc8000e0c318, 2, 8, fffff88000e0c318}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeProcessCompletedRequests+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov 25 01:32:38.051 2009 (GMT-5)
System Uptime: 0 days 4:18:23.627
BugCheck 50, {fffffc0002ae5d04, 8, fffff80002ae5d04, 7}
*** WARNING: Unable to verify timestamp for aswFsBlk.sys
*** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.sys
Probably caused by : luafv.sys ( luafv!LuafvNormalizeNameComponentEx+145 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Nov 24 20:02:31.989 2009 (GMT-5)
System Uptime: 0 days 10:35:31.566
BugCheck 50, {fffffc0002a97d04, 8, fffff80002a97d04, 7}
Probably caused by : ntkrnlmp.exe ( nt!KeEnterGuardedRegion+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov 25 19:57:15.284 2009 (GMT-5)
System Uptime: 0 days 0:29:03.985
BugCheck D1, {fffffc8003e80128, 2, 8, fffff88003e80128}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : sptd.sys ( sptd+4398a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov 26 09:34:48.202 2009 (GMT-5)
System Uptime: 0 days 8:26:51.904
BugCheck D1, {fffffc80049f9820, a, 8, fffff880049f9820}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1ae820 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov 26 01:07:00.684 2009 (GMT-5)
System Uptime: 0 days 5:09:06.385
BugCheck 50, {fffffc0002a90d04, 8, fffff80002a90d04, 7}
Probably caused by : ntkrnlmp.exe ( nt!KeEnterGuardedRegion+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 27 22:32:46.511 2009 (GMT-5)
System Uptime: 0 days 2:03:51.212
BugCheck 50, {fffffc0002aa1d04, 8, fffff80002aa1d04, 7}
Probably caused by : ntkrnlmp.exe ( nt!KeEnterGuardedRegion+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  1 07:32:24.908 2009 (GMT-5)
System Uptime: 0 days 7:04:47.609
BugCheck 50, {fffffc8003f2f7f8, 8, fffff88003f2f7f8, 7}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  1 00:26:55.131 2009 (GMT-5)
System Uptime: 0 days 1:49:55.832
BugCheck 50, {fffffc0002ce3f60, 8, fffff80002ce3f60, 7}
Probably caused by : ntkrnlmp.exe ( nt!IopAllocateIrpPrivate+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  1 20:05:53.122 2009 (GMT-5)
System Uptime: 0 days 0:11:24.823
BugCheck D1, {fffffc80049cb820, a, 8, fffff880049cb820}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1ae820 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  1 22:10:37.556 2009 (GMT-5)
System Uptime: 0 days 2:03:37.257
BugCheck 50, {fffffc0002cd4d04, 8, fffff80002cd4d04, 7}
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : luafv.sys ( luafv!LuafvNormalizeNameComponentEx+145 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
My System SpecsSystem Spec
.


03 Dec 2009   #4

Microsoft Windows 7 Ultimate 64bit
 
 

Thanks for the reply and sorry for the delay in replying.

Okay this is what I did.
  1. Uninstalled Daemon Tools straight away
  2. Updated the video drivers from Nvidia to the latest for Win 7
  3. By storage did you mean the drivers for the hard disks? I updated the entire set of drivers available for Win 7 for this motherboard from the Gigabyte site. There was one set of drivers for SATA and raid controllers. I installed that. Are those the ones you meant?
  4. The errors caused by the luafv.sys seems to be affecting files connected to the Avast Antivirus program that I am using. Does this mean that Avast is responsible for the crashes as well?
There were 2 BSODs between the Daemon tools uninstall and the video drivers update. One happened just instantly after the uninstall finished and another about 10 mins after. Have attached the 2 dump files of those here as well as the sysdata.xml file that gets mentioned in each post crash bootup message.

So far its just been about an hour after the updates and there haven't been any other crashes.
My System SpecsSystem Spec
03 Dec 2009   #5

7600.20510 x86
 
 

If you do have further crashes, I'd suggest uninstalling any antivirus you have, based on the fact that one of these is a 0x50 stop.
My System SpecsSystem Spec
03 Dec 2009   #6
Microsoft MVP

 
 

Quote:
The errors caused by the luafv.sys seems to be affecting files connected to the Avast Antivirus program that I am using. Does this mean that Avast is responsible for the crashes as well?
Not necessarily, although the likelyhood is pretty good. It depends on what's causing it to do this.

Both of the latest BSOD's have components of the storage sub-system involved, so that's the most likely thing to concentrate on now. The most recent also has the driver from Daemon Tools in the stack text. With that being the case, I'd have to suggest that you wait for further BSOD's (as it could have been the SPTD.SYS file causing the problems, and that could have involved the storage sub-system and caused issues when it was being removed).

If it BSOD's again, post back with the dump files and we'll see if further tests are called for.
My System SpecsSystem Spec
03 Dec 2009   #7

Microsoft Windows 7 Ultimate 64bit
 
 

Ok Guys! Thanks for the help. Much appreciated. There haven't been any more crashes yet (Hope it stays that way)
Will post again with the dump files if there is one.
My System SpecsSystem Spec
03 Dec 2009   #8

7600.20510 x86
 
 

Very cool. You're welcome and enjoy.
My System SpecsSystem Spec
04 Dec 2009   #9

Microsoft Windows 7 Ultimate 64bit
 
 

Hey guys, there were 2 more crashes. Have uploaded the dump files. Hopefully we'll be able to narrow down the culprit this time.
My System SpecsSystem Spec
04 Dec 2009   #10

7600.20510 x86
 
 

Still 0x50 errors. So uninstall the Avast if you haven't already. Let's also see what Usasma might have to say about things if that doesn't help.
My System SpecsSystem Spec
Reply

 BSOD on first Win 7 RTM now on Win 7 Ultimate




Thread Tools



Similar help and support threads for2: BSOD on first Win 7 RTM now on Win 7 Ultimate
Thread Forum
Win 7 Ultimate x64 BSOD BSOD Help and Support
BSOD - Windows 7 Ultimate 64bits TO MANY Different BSOD BSOD Help and Support
bsod w7 ultimate 64 bit BSOD Help and Support
Win 7 Ultimate x64 BSOD BSOD Help and Support
BSOD on Win 7 Ultimate...please help BSOD Help and Support
BSOD During upgrade from Vista Ultimate to 7 Ultimate Installation & Setup

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 09:07 PM.
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