BSOD in DAO/Rift after Win7 32 - 64 upgrade

Apryldaun · 28 Apr 2011

Hiyas all

GAH!!

Tried every single thing I know how, ran Memtest86, ck'd for the newest drivers I could find... uninstalled Nvidia drivers ran Driver Sweeper and reinstalled... First few weeks it was 'Rift' that caused the crashes. After I got the Beta *now released* Nvidia drivers the problem went away. Life was good. :)

BUT NO, Then I decided I wanted to install Dragon Age Origins and copy my character over for the new xpac and BAM. BSOD's are back, but worse than ever before... No consistency that I can see in exactly wth is causing it *sigh* I'll love you forever and be your 'Best Friend' if you can help me figure out which evil driver or piece of hardware is causing me to go bald.

TYVM!

Apryldaun · 28 Apr 2011

FYI just to clarify: Did not 'upgrade' a 32 bit to a 64 bit lmao

As I'm sure everyone knows that's not possible. I reformatted the HDD and did a clean install of the Windows 7 64bit O/S. Had previously had Vista then Windows 7 32 bit on the same system w/no errors or issues in any of the above mentioned programs. Only started having issues after upgrading to the 64 bit version.

Jonathan_King · 28 Apr 2011

Hello,

Start by uninstalling Daemon Tools, as it's using SPTD. Remove SPTD itself with the tool found here: DuplexSecure

Do you have another video card you could test out? Maybe borrow one from a friend, or purchase one from a store that will allow you to return it if need be.

Run all three Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

Run Memtest86 for 7 or 8 passes: RAM - Test with Memtest86+

...Summary of the dumps:

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Feb 23 20:06:39.331 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:53.581
*** 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+1c3139 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MassEffect2.ex
FAILURE_BUCKET_ID:  X64_0x7f_8_nvlddmkm+1c3139
SystemProductName = MS-7578
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Feb 23 18:58:49.755 2011 (UTC - 4:00)
System Uptime: 0 days 1:17:55.005
*** 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+1c3139 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MassEffect2.ex
FAILURE_BUCKET_ID:  X64_0x7f_8_nvlddmkm+1c3139
SystemProductName = MS-7578
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Feb 22 18:37:01.609 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:07.046
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 21:50:17.770 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:54.208
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LWEMon.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
SystemProductName = MS-7578
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 20:32:33.251 2011 (UTC - 4:00)
System Uptime: 0 days 1:48:30.705
*** 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+55282c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  MassEffect2.ex
FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+55282c
SystemProductName = MS-7578
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 18:44:09.906 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:07.359
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 17:04:56.031 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:07.468
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 16:39:25.467 2011 (UTC - 4:00)
System Uptime: 0 days 1:25:02.920
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
SystemProductName = MS-7578
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Feb 21 15:13:34.507 2011 (UTC - 4:00)
System Uptime: 0 days 1:33:09.960
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MassEffect2.ex
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
SystemProductName = MS-7578
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 20 16:29:31.114 2011 (UTC - 4:00)
System Uptime: 0 days 5:27:30.551
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  GameClient.exe
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
SystemProductName = MS-7578
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Apryldaun · 28 Apr 2011

TYVM for your help!

GAH Daemon Tools.. Nice... Not sure what program that piggy-backed on but I didn't install it *sigh* and I can't find it in the start menu, or by manually cking my Program Files Directories for a folder w/the name. I 'do' come up w/ Daemonu.exe in my Nvidia Settings Control Panel in the following directory: C:\NVIDIA\DisplayDriver\270.61\Vista 64-bit\English\Display.Update.

This is actually the second card I've purchased in the last month. The GTX 460 SE is about 2 wks old the previous card I bought a month ago was a GTX 550ti. Had same issues w/games esp Rift and DAO then also. NVIDIA had me use the Beta Driver and everything was fine. A week later they supposedly released the 'same' driver and and I updated it. Think perhaps they made a change from Beta to Release that brought back this nasty mess again?

So how should I approach this now? Should I just do a full uninstall then sweep w/DCpro then reinstall the previous Driver from Beta? Or is there a way to remove just the Daemonu.exe if it's the culprit here w/o affecting the existing NVIDIA drivers?

Should I wait to remove SPTD until after I perform w/e other steps are necessary to end that process first?
TYVM for your help! God I wish I'd kept my old 8800GTX instead of building it into my daughters new sys! LMAO! Not as shiney 'graphics' but way better stability. Doesn't matter how good the graphics work if you can't play the games.... *sigh*

Apryldaun · 28 Apr 2011

Don't know why it shows Vista 64bit and not Windows 7 64 bit unless that's just an 'Nvidia' thing... ><
Also have already run CPU stress test along w/Memtest86 when the issue originally started w/the GTX 550ti. All were fine. Ran Memtest86 again last night.. np found. Srsly beginning to think that it's the Nvidia drivers yet again...

Apryldaun · 28 Apr 2011

Haha! Just posting as an FYI in case anyone is running into a similar issue

Used the info you gave me and uninstalled all Nvidia drivers/wiped w/DCPro etc... Ck'd for Daemonu which was of course gone. Ck'd for SPTD in registry HKLM/System/Current Control Set/Control and was gone also. Installed the Beta driver 170.51 which I had previously.. made DOUBLE sure that 'Nvidia Update' was unchecked.
It did 'not' install Daemonu.exe or SPTD and so far so good

No BSOD's in DAO yet! TYVM again for pointing me in the 'right' direction!

Jonathan_King · 29 Apr 2011

Good, glad to hear.

The "Daemonu.exe" is not the same program as Daemon Tools; Daemon Tools Lite should be found in the Start Menu. If you have crashes again, post a new jcgriff2 report and we'll make sure it's gone.

Good luck!

Apryldaun · 29 Apr 2011

LMAO well usually it's the guys that are premature J/K!!

Srsly though, BSOD came back later last night so ran a couple of Prime95 stress tests and another CPU specific test. CPU was fine. Ran Memtest86 .. failed at Test #7.. *cry*. Tested each stick seperately in the second DDR3 slot. Both passed but noticed although the Bios identified it as DDR3, Under 'Chipset' in Memtest86 it said type DDR2? O.o
Testing each now in the first slot. Popped in the first one started up Memtest86, Under Chipset it now says 'DDR3'.... *Blink* I am SO confused? Could this be the problem? That the second DDR3 slot is incorrectly configured on the mobo itself, thus when running dual channel it fails? Or does it have something to do w/having the RAM in the second slot only that it defaults to DDR2? Never ran across this before so completely lost as to which part I need to replace. Got a sick feeling it's the mobo though, P5QC's were infamous for issues w/DDR3 slots according to several forum posts I found. Any advice is 'greatly' appreciated TYVM! :)

Apryldaun · 29 Apr 2011

Update instant fail at test 5 on first slot reading stick 1 in Memtest86 under Chipset as the correct DDR3. *cry* However 2nd DDR3 passed just fine w/it also showing under Memtest86 as DDR3. Is there a reason why when I test the RAM in the second slot only it reads it as DDR3 in Bios boot but DDR2 in Memtest86? Hoping that maybe it 'is' just bad RAM. *crossed fingers* since the 1st stick read bad immediately on the 1st slot.

Jonathan_King · 29 Apr 2011

I really can't account for the inaccurate reading in Memtest86, I'm sorry. My best guess is that it's a quirk in the program, and not necessarily indicative of the actual problem.

Do you have access to any other RAM you could try in your system? If replacement RAM has the same trouble, we can blame the motherboard.