Page 3 of 6
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 10:29
by Robbi
Just because you are bluescreening aswell doesnt mean it is linked Nikolai mate, what are you erroring with, and what are your specs?
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 14:19
by Nikolai[NL]
Sorry I'm a bit of a noob when it comes to technical computer stuff. I also have a post on the forums about sudden screen flickering when playing PR. The problem is that is doesnt occur or any map in particular or after a certain action its very random. Maybe the screen flickering and the occasional BSOD are linked in any way. With the screen problems I just see flickering bars comming over my screen, when I press ESC to go in to the menu and back into the game its gone.
I have an AMD X2 4200 with 2 gigs of ram and a nVidia 8600GTS superclocked card. Not sure what my mobo is but it has an on-board realtek soundcard. My PSU is 550w so that should be enough. Ive done memory checks on both my ram and there is no problem there. I already had the card with .85 so there must be something originating in .86 that casuses it.
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 14:25
by Robbi
Well what monitor have you got?
are you running the game at your optimal Resolution?
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 14:34
by Nikolai[NL]
I have a samsung syncmaster 913n, its a few years old. Not sure if its the optimal resolution, but Ive been running at 1280x1024 for ages with every game. I haven't changed any video settings in PR for a while either.
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 14:36
by Robbi
well, that res is right for it.
Does it flicker black and then to normal colours or some other way?
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 14:44
by Nikolai[NL]
the flickering looks a bit like a TV thats not entirely set on the right channel, you can see what's going on but there is interference (horizontal bars that flicker alot)
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 14:47
by Robbi
Have you checked your baling, made sure its not loose or damaged?
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 14:49
by Nikolai[NL]
[R-TEC]Robbi187 wrote:Have you checked your baling, made sure its not loose or damaged?
ok noob alert, whats baling?
I doubt its a hardware issue since I only have problems playing PR.
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 15:02
by Robbi
nah mate, noob alert my end....
Cabling, in a rush to sort other things and had the best Typo ever
Do you get the problems in Vanilla?
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 15:08
by Nikolai[NL]
Ill have to try vanilla, I play crysis, arma2, far cry 2, prototype, fallout and all without problems. Could be a BF2 related issue, Ill try some vanilla tonight (gonna be hell with all the noobtubers and bunnyhoppers) Thx for your input so far and Ill post the outcome. Come to think of it, I don't recall having any issues with FH2 I played that last weekend but not for a very long period.
Re: BSOD 4 times since .86 came out
Posted: 2009-07-07 15:14
by Robbi
Ok, try out vanilla for a bit, if it doesnt break it then ill have more of a think
Re: BSOD 4 times since .86 came out
Posted: 2009-07-08 07:20
by PepsiMachine
BSoD again on Archer. I spawn in, grab Grenadier, hear someone call out "We're getting wasted! Fall b---"
BSoD.
The grenadier sound loops while the memory dump is being performed. This should be sound related, but I thought Windows Vista was redesigned so that sound drivers couldn't crash the entire system?
Re: BSOD 4 times since .86 came out
Posted: 2009-07-08 12:55
by Robbi
not at all, and this doesnt mean its sound related just because a sound was being played.
What was the error from the dump?
Re: BSOD 4 times since .86 came out
Posted: 2009-07-08 16:00
by strickt
[R-TEC]Robbi187 wrote:not at all, and this doesnt mean its sound related just because a sound was being played.
What was the error from the dump?
So far ive yet to BSOD after disabling my X-Fi card, however I still crash to desktop during game play, Usually ill start to get a small stutter, then the mountains or houses will flicker black, then bingo CRASH TIME.
Re: BSOD 4 times since .86 came out
Posted: 2009-07-09 02:57
by PepsiMachine
[R-TEC]Robbi187 wrote:not at all, and this doesnt mean its sound related just because a sound was being played.
What was the error from the dump?
Same as bkandor's.
Ran memtest86+ and passed. Going to disable my X-Fi and give onboard sound a shot.
Strange too, PR .86 is the only thing causing me to BSoD.
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033
Extra information about the problem
BCCode: 50
BCP1: FFFFFFFF8E560000
BCP2: 0000000000000000
BCP3: FFFFF80002289882
BCP4: 0000000000000005
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1
UPDATE:
Sifted through the crashdump and found:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffff8e560000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002289882, If non-zero, the instruction address which referenced th
e bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000243a080
ffffffff8e560000
FAULTING_IP:
nt!MmProbeAndLockPages+112
fffff800`02289882 410fb601 movzx eax,byte ptr [r9]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: BF2.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffffa600e2304e0 -- (.trap 0xfffffa600e2304e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
(stuff I don't think matters or is readable)
LAST_CONTROL_TRANSFER: from fffff800022cda26 to fffff8000226d450
STACK_TEXT:
(lots of letters)
STACK_COMMAND: kb
FOLLOWUP_IP:
ctoss2k+5dde
fffffa60`04262dde ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: ctoss2k+5dde
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ctoss2k
IMAGE_NAME: ctoss2k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a115694
FAILURE_BUCKET_ID: X64_0x50_ctoss2k+5dde
BUCKET_ID: X64_0x50_ctoss2k+5dde
Followup: MachineOwner
Googled ctoss2k.sys and it seems to be a Creative driver...
Re: BSOD 4 times since .86 came out
Posted: 2009-07-09 07:43
by Nikolai[NL]
the agony of BF vanilla, tried it for about an hour last night to see if it gave any problems. It was absolute hell
but I didnt get any BSOD's or other errors. Ill try it again soon and if I can manage a bit longer
Re: BSOD 4 times since .86 came out
Posted: 2009-07-09 15:15
by Robbi
Pepsi machine, try reinstalling the creative driver, not sure if I said in this thread, but i'll post up a tutorial about it later.
Make sure its Uninstall | use a driver cleaner [like drivercleaner dot net |
Reinstall, bingo. Make sure you restart in between each process.
Another thing, is the XFi card PCI or PCI express?
Re: BSOD 4 times since .86 came out
Posted: 2009-07-09 15:17
by Robbi
Nikolai, seems weird that it is happening in PR but not BF2 ....
Have you got VSync enabled in nvidias control panel?
If not, try it on see if it helps, you can just set it to run with bf2.exe so all should be good.
Re: BSOD 4 times since .86 came out
Posted: 2009-07-09 16:33
by bkandor
MODULE_NAME: ctoss2k
IMAGE_NAME: ctoss2k.sys
Hi,
Doesn't the ctoss2k.sys in the dump indicate a sound driver based issue? I have the X-Fi Titanium Fatal1ty Series PCI-E Sound Card as well.
An update from me - nothing conclusive, but I put vista sp2 on my machine last week and I haven't blue screened yet.
Re: BSOD 4 times since .86 came out
Posted: 2009-07-09 16:41
by Robbi
yes it is a Creative Driver issue in the dump.
Also, SP2 with Vista may sort out a few problems with creative cards, this is why Creative released a new driver at SP2 release you see.