Curse Client v4 - Windows

1472 - BSOD in W7 RC 64bit after version update (2 times now)

Submitted Via

Curse Client 4.0.0.784, Microsoft Windows NT 6.1.7100.0

Description

After two seperate updates, when restarting V4 got BSOD.
First one not sure the version update, may have been .721, but not positive.
BSOD:

PAGE_FAULT_IN_NONPAGED_AREA

0x00000050 (0xFFFFF88007316750, 0x0000000000000001, 0xFFFFF800030AA4D8, 0x0000000000000001)

The second one was after .784.
BSOD:

PAGE_FAULT_IN_NONPAGED_AREA

0x00000050 (0xFFFFF88007B2E750, 0x0000000000000001, 0xFFFFF800030B44D8, 0x0000000000000001)

Steps to Reproduce

So far it is happening after version update. Will see if it continues after next update.

Game Configuration

Game Type: World of Warcraft
Game Path: C:\Users\Public\Games\World of Warcraft\
Addon Path: C:\Users\Public\Games\World of Warcraft\interface/addons
Folder Count: 262
Addon Count: 106
Scanning Security Exceptions: 0
Scanning Unknown Exceptions: 0
Scanning Empty Directories: 27
Scanning Directories Not Found: 0

Game Type: World of Warcraft
Game Path: D:\Program Files\World of Warcraft\
Addon Path: D:\Program Files\World of Warcraft\interface/addons
Folder Count: 262
Addon Count: 105
Scanning Security Exceptions: 0
Scanning Unknown Exceptions: 0
Scanning Empty Directories: 26
Scanning Directories Not Found: 0

Game Type: World of Warcraft
Game Path: D:\Program Files\World of Warcraft Public Test\
Addon Path: D:\Program Files\World of Warcraft Public Test\interface/addons
Folder Count: 15
Addon Count: 9
Scanning Security Exceptions: 0
Scanning Unknown Exceptions: 0
Scanning Empty Directories: 0
Scanning Directories Not Found: 0

Time Details

UTC Time: 10/3/2009 4:53:49 AM
Local Time: 10/3/2009 12:53:49 AM
Timezone: Eastern Standard Time
Daylight Savings Time: True

Log Data

Log Opened

Curse Client Starting...

Version 4.0.0.784

Task Executing: Firewall

Task Executing: Connection

Task Executing: GameDatabase

Task Executing: AddOnDatabase

Task Executing: GameInstalls

Task Executing: Core

Startup Complete

User When Change
Adamar Tue, 06 Oct 2009 21:36:02 Changed status from Replied to Invalid
Adamar Tue, 06 Oct 2009 21:34:29 Changed status from Waiting to Replied
Adamar Sun, 04 Oct 2009 16:13:49 Changed status from Replied to Waiting
personanongratis Sun, 04 Oct 2009 00:48:02 Changed status from Waiting to Replied
Adamar Sat, 03 Oct 2009 13:33:01 Changed status from New to Waiting
personanongratis Sat, 03 Oct 2009 04:55:02 Create

You must login to post a comment. Don't have an account? Register to get one!

  • 4 comments
  • Avatar of Adamar Adamar Tue, 06 Oct 2009 21:34:29

    I am going to close this ticket. We have thoroughly tested Curse Client v4 with Windows 7 build 7600, and it works perfectly. The issue you're experiencing may be a bug with Windows 7 build 7100.

  • Avatar of Adamar Adamar Sun, 04 Oct 2009 16:13:44

    I really believe this is a bug in Windows 7. You appear to have build 7100, which is outdated. Can you update to the RTM, build 7600?

  • Avatar of personanongratis personanongratis Sun, 04 Oct 2009 00:48:01

    The update completes successfully, it BSOD when you go to start V4 after the update. It has only been twice, but so far only after the update has completed and try to start V4 the first time after updating. Restarting after BSOD, V4 runs fine and shows the proper version of the update. It runs fine otherwise, no noticeable issue, if any.

    It is definitely with the restart because I can do other things (surf web, use other programs [besides Minion], etc.) after the update completes and no BSOD.

    I didn't report the first one because W7 has had it's bugs that cause BSOD, but it was twice after trying open V4 that it BSOD with very same error. If you want to push an update, or there is a way we can just make it happen on mine, let me know if there is anything that will help figure out what is happening and I'll do it.

    Since I haven't seen anyone else reporting this issue, though I have seen a lot of crash reports, it may be just W7 related or possible something unique on my system.

    Last edited on 04 Oct 2009 by personanongratis
  • Avatar of Adamar Adamar Sat, 03 Oct 2009 13:32:53

    The BSOD happens after launching v4, or while it is updating? Then it never happens again until the next update?

  • 4 comments

Facts

Last updated on
06 Oct 2009
Reported on
03 Oct 2009
Status
Invalid - This was not a valid report.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.

Reported by

Possible assignees