Bluescreen Win 7 RC1 7100 64 Bit

[garack666 10]

Hi, i only run Arma 2 on this machine. No firewall no av.

9.15 ATI and creative xfi gamer win 7 drivers.

q6600 and msi p35 chipset. 4870 1gb.

fresh installation.

Bluescreen says Stop: 0x000000001E

comes after 10 minutes playing arma in multiplayer. not testet singleplayer.

vista32sp1 run smooth 8 hours with arma.

Win 7 Rc1 has all updates.

Problemsignatur

Problemereignisame: BlueScreen

Betriebsystemversion: 6.1.7100.2.0.0.256.1

Gebietsschema-ID: 1031

Weitere Informationen über das Problem

BCCode: f7

BCP1: 0000000000000F20

BCP2: 00001C81BCCD8B9D

BCP3: FFFFE37E43327462

BCP4: 0000000000000000

OS Version: 6_1_7100

Service Pack: 0_0

Product: 256_1

Bucket-ID: X64_0xF7_nt!IoGetDeviceProperty+c7

Serverinformationen: 82f3d9bf-6db5-4163-ac03-7a7ff945fe70

Any help?

Edited June 3, 2009 by garack666

[bangtail 0]

Hi, i only run Arma 2 on this machine. No firewall no av.

9.15 ATI and creative xfi gamer win 7 drivers.

q6600 and msi p35 chipset. 4870 1gb.

fresh installation.

Bluescreen says somethink about drivers...cant read it so fast.

comes after 10 minutes playing arma in multiplayer. not testet singleplayer.

vista32sp1 run smooth 8 hours with arma.

Win 7 Rc1 has all updates.

Problemsignatur

Problemereignisame: BlueScreen

Betriebsystemversion: 6.1.7100.2.0.0.256.1

Gebietsschema-ID: 1031

Weitere Informationen über das Problem

BCCode: f7

BCP1: 0000000000000F20

BCP2: 00001C81BCCD8B9D

BCP3: FFFFE37E43327462

BCP4: 0000000000000000

OS Version: 6_1_7100

Service Pack: 0_0

Product: 256_1

Bucket-ID: X64_0xF7_nt!IoGetDeviceProperty+c7

Serverinformationen: 82f3d9bf-6db5-4163-ac03-7a7ff945fe70

Any help?

Beta OS, nuff said.

Eth

[garack666 10]

Nope RC1 and defs testet win7 rc1 too.

[bangtail 0]

Nope RC1 and defs testet win7 rc1 too.

Use at your own risk. It's not a retail product. An RC is a glorified beta JFYI.

Eth

[garack666 10]

Please post if you can help or post not.

[pchaxor 0]

Run Diagnostics on your RAM

That would be my first guess.

I do not think ARMA is the issue. I run Windows 7 RC as well and I get no crashes at all.

Google Results:

"If you read the error code DRIVER_OVERRAN_STACK in the minidump description it means that you have an infection from a hacker and the system is shut down so that said hacker does not gain complete control."

"This is the classic "buffer overrun" hacking attack. The system has been brought down to prevent a malicious user from gaining complete control of it."

You have a Trojan perhaps?

Try getting malwarebytes or Spydot S&D and clean up the bugs.

Edited June 4, 2009 by pchaxor

[garack666 10]

Run Diagnostics on your RAM

That would be my first guess.

RAm works fine under vista32 and is not overclocked.

[garack666 10]

I do not think ARMA is the issue. I run Windows 7 RC as well and I get no crashes at all.

Google Results:

"If you read the error code DRIVER_OVERRAN_STACK in the minidump description it means that you have an infection from a hacker and the system is shut down so that said hacker does not gain complete control."

"This is the classic "buffer overrun" hacking attack. The system has been brought down to prevent a malicious user from gaining complete control of it."

You have a Trojan perhaps?

Try getting malwarebytes or Spydot S&D and clean up the bugs.

Sry was a stop error i editet first post.

[odjob 0]

Mine runs fine in Win7 RC even under stress, no bluescreens.

I used to have bluescreens with "stop" about a half year ago, as a last resort i removed/reinstalled the gf-card and mem-sticks and viola! I guess one of them wasnt properly seated, just a tip.

[pchaxor 0]

Sry was a stop error i editet first post.

Yup it is a Stop Error.

I am making an educated guess that your OS is infected with a Trojan

Google it friend.

Edited June 4, 2009 by pchaxor

[echo1 0]

Right now, I'd say it could well be down to your X-Fi. Speaking from personal experience, and from seeing problems that others have had, those things cause all sorts of headaches. Try removing it or disabling it and see if that does anything.

Beta OS, nuff said.

Eth

That's a bit of an oversimplified way of looking at things. There's nothing wrong with 7. Even the pre-beta alphas were a better OS than Vista, and that's no exaggeration.

(Or at least in my opinion based on my usage of both)

Edited June 4, 2009 by echo1

[garack666 10]

Yup it is a Stop Error.

I am making an educated guess that your OS is infected with a Trojan

Google it friend.

its a fresh install , brings rc1 a trojan with :)

[bangtail 0]

Right now, I'd say it could well be down to your X-Fi. Speaking from personal experience, and from seeing problems that others have had, those things cause all sorts of headaches. Try removing it or disabling it and see if that does anything.

That's a bit of an oversimplified way of looking at things. There's nothing wrong with 7. Even the pre-beta alphas were a better OS than Vista, and that's no exaggeration.

(Or at least in my opinion based on my usage of both)

No, it's not. I wont even deal with customers who tell me they have it installed. It's shaping up to be a great OS and it's substantially better than Vista was at launch BUT it is not a retail OS and you use a beta/RC OS at your own peril.

There are problems with Win 7 and a lot of the drivers are not stable yet and that's to be expected with beta software. You should never run a Beta OS as your main OS.

Saying that the Pre betas of Win 7 were better than Vista at launch is probably fair comment but Vista SP2 is actually very good and Win 7 is not the vast departure that Vista was from XP, making it easier to get it right the first time and, consequently, in less time.

Eth

Edited June 4, 2009 by BangTail

[garack666 10]

got another BSOD this time i analysed it with windows debugging and symbols_

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Tarabas\Desktop\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: C:\Symbols

Executable search path is:

Windows 7 Kernel Version 7100 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700

Machine Name:

Kernel base = 0xfffff800`02802000 PsLoadedModuleList = 0xfffff800`02a3be90

Debug session time: Thu Jun 4 03:16:00.001 2009 (GMT+2)

System Uptime: 0 days 0:11:35.501

Loading Kernel Symbols

...............................................................

................................................................

.........................

Loading User Symbols

Loading unloaded module list

....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffffffffff81, 2, 1, fffff88004917f3a}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSubmitSignalCommand+4a )

Followup: MachineOwner

---------

1: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: ffffffffffffff81, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, value 0 = read operation, 1 = write operation

Arg4: fffff88004917f3a, address which referenced memory

Debugging Details:

------------------

WRITE_ADDRESS: ffffffffffffff81

CURRENT_IRQL: 2

FAULTING_IP:

dxgmms1!VidSchiSubmitSignalCommand+4a

fffff880`04917f3a f687a800000001 test byte ptr [rdi+0A8h],1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff880023b8af0 -- (.trap 0xfffff880023b8af0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff88004917f3a rsp=fffff880023b8c80 rbp=fffffa800694e010

r8=fffff880023b8ca0 r9=fffffa800694e010 r10=fffff880049162b4

r11=fffffa8007699f28 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz ac po cy

dxgmms1!VidSchiSubmitSignalCommand+0x4a:

fffff880`04917f3a f687a800000001 test byte ptr [rdi+0A8h],1 ds:00000000`000000a8=??

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800028804e9 to fffff80002880f80

STACK_TEXT:

fffff880`023b89a8 fffff800`028804e9 : 00000000`0000000a ffffffff`ffffff81 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff880`023b89b0 fffff800`0287f160 : fffff880`023b8b50 fffffa80`07699d50 00000000`07699d50 fffffa80`0694e010 : nt!KiBugCheckDispatch+0x69

fffff880`023b8af0 fffff880`04917f3a : fffffa80`0694e658 fffffa80`07699d50 00000000`00000000 fffff880`04941dc0 : nt!KiPageFault+0x260

fffff880`023b8c80 fffff880`049423e9 : fffffa80`07699d50 00000000`00000080 00000000`00000000 fffffa80`0694e010 : dxgmms1!VidSchiSubmitSignalCommand+0x4a

fffff880`023b8cd0 fffff880`04941e96 : 00000000`00000000 fffffa80`07699d50 00000000`00000080 fffffa80`0694e010 : dxgmms1!VidSchiSubmitQueueCommand+0xa1

fffff880`023b8d00 fffff800`02b06e66 : 00000000`02c3c476 fffffa80`06a50b60 fffffa80`039cd040 fffffa80`06a50b60 : dxgmms1!VidSchiWorkerThread+0xd6

fffff880`023b8d40 fffff800`02833a86 : fffff880`009e9180 fffffa80`06a50b60 fffff880`009f3fc0 fffff880`01261a30 : nt!PspSystemThreadStartup+0x5a

fffff880`023b8d80 00000000`00000000 : fffff880`023b9000 fffff880`023b3000 fffff880`023b8690 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

dxgmms1!VidSchiSubmitSignalCommand+4a

fffff880`04917f3a f687a800000001 test byte ptr [rdi+0A8h],1

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: dxgmms1!VidSchiSubmitSignalCommand+4a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee92b2

FAILURE_BUCKET_ID: X64_0xD1_dxgmms1!VidSchiSubmitSignalCommand+4a

BUCKET_ID: X64_0xD1_dxgmms1!VidSchiSubmitSignalCommand+4a

Followup: MachineOwner

---------

perhaps some issues with track ir5...will test this.

Edited June 4, 2009 by garack666

[Nicholas 5]

It's not because of compatability issues, as of I have Windows 7 RC Build 7100 64-Bit also, and I got ArmA 2 runnign smooth as can be. Maybe a device error?

[sickboy 13]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

Sounds like a Vista driver used on Win7 that is causing the issue?

[papoose244 10]

Has anyone tested windows 7 vs vista 64 with this game in which OS does it perform better?

[garack666 10]

Win 7 performes way better for me.

Yes a driver issue, but i got 4 different blue screen errors ... i suppose it could be track ir 5 software. check this out today.

[xav 0]

There are blue screens with Win 7 ? :)

[garack666 10]

tested it, without track ir5 running game is stable. must be track ir5. ich check the forums there.

[Ruckus 0]

I'm also using Windows 7 64-bit RC without any problems. It is also possible that you may be having issues with either your vid driver or the X-Fi driver as they are both probably beta.

I don't recall without being at home but I think I was using the Vista 64 bit X-Fi driver.

[garack666 10]

yes xfi gamer is beta but i figured out hte problem. its track ir5 software.arma is running fine without. i do some test, test older version re/deinstall and let you all know.

[papoose244 10]

Win 7 performes way better for me.

Yes a driver issue, but i got 4 different blue screen errors ... i suppose it could be track ir 5 software. check this out today.

Thanks garack by how much fps is it faster?

[garack666 10]

Thanks garack by how much fps is it faster?

perhaps 5 fps.

loading is faster too and streaming. but this could be cause my hdd is a new setup with no rubbish. its a raptor btw.

track ir 4.1 final works with NO bs so long...but its horrible with track ir 5 i cant look in all directions..so its the track ir 5 beta software..lol beta track ir beta os beta game...the world is beta:cool::cool::D;):o

[Kr3v 10]

Personaly I get a blue screen saying Bad_Pool_header...