MagicAndre1981

Webradio: http://laut.fm/best_of_80s

the crash happens in steam.exe while doing GDI operation (win32k!vFillGRectDIB32BGRA): ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 000000000000001c, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: fffff800010f141f, address which referenced memoryDebugging Details:------------------WRITE_ADDRESS: GetUlongPtrFromAddress: unable to read from fffff800011db3c0GetUlongFromAddress: unable to read from fffff800011db3e0 000000000000001c CURRENT_IRQL: 2FAULTING_IP: nt!MiRestoreTransitionPte+9ffffff800`010f141f 83411cff add dword ptr [rcx+1Ch],0FFFFFFFFhCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: Steam.exeSTACK_TEXT: 00 nt!KeBugCheckEx01 nt!KiBugCheckDispatch02 nt!KiPageFault03 nt!MiRestoreTransitionPte04 nt!MiRemovePageFromList05 nt!MiRemoveZeroPage06 nt!MiResolveDemandZeroFault07 nt!MiResolveProtoPteFault08 nt!MiDispatchFault09 nt!MmAccessFault0a nt!KiPageFault0b win32k!vFillGRectDIB32BGRA0c win32k!bRectangleMesh0d win32k!EngGradientFill0e win32k!GreGradientFill0f win32k!NtGdiGradientFill10 nt!KiSystemServiceCopyEnd11 0x012 nt!KiCallUserMode13 0x014 0x0IMAGE_NAME: win32k.sysFAILURE_BUCKET_ID: X64_0xA_win32k!vFillGRectDIB32BGRA+36dFAILURE_ID_HASH_STRING: km:x64_0xa_win32k!vfillgrectdib32bgra+36dnt!MiRestoreTransitionPte still looks like RAM issues. Post some pictures of CPU-Z, please.

slipstreaming a Sp is difficult since Vista. It is better to take a clean ISO. If you don't want this I can't help you, sorry.

thanks for the Update

Download an official Win7 ISO which has the Sp1incuded from here: http://www.heidoc.net/joomla/technology-science/microsoft/14-windows-7-direct-download-links

try this: http://xbmc.org/xbmc-13-0-gotham-rises/

I also tried this and it failed for me, too.

please install all Updates for Win7 Sp1. You still use the Sp1 RTM without any update (7601.17514.x86fre.win7sp1_rtm.101119-1850). Debugging shows Powermanagement operations. ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************MULTIPLE_IRP_COMPLETE_REQUESTS (44)A driver has requested that an IRP be completed (IoCompleteRequest()), butthe packet has already been completed. This is a tough bug to find becausethe easiest case, a driver actually attempted to complete its own packettwice, is generally not what happened. Rather, two separate drivers eachbelieve that they own the packet, and each attempts to complete it. Thefirst actually works, and the second fails. Tracking down which driversin the system actually did this is difficult, generally because the trailsof the first driver have been covered by the second. However, the driverstack for the current request can be found by examining the DeviceObjectfields in each of the stack locations.Arguments:Arg1: 88776008, Address of the IRPArg2: 00000eaeArg3: 00000000Arg4: 00000000Debugging Details:------------------IRP_ADDRESS: 88776008FOLLOWUP_IP: pci!PciBusDevicePowerCompletion+628c315b10 5f pop ediCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULTBUGCHECK_STR: 0x44PROCESS_NAME: SystemCURRENT_IRQL: 2ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64freDPC_STACK_BASE: FFFFFFFF8E921000LAST_CONTROL_TRANSFER: from 8c315b10 to 82e8fcbdSTACK_TEXT: 8e920e2c 8c315b10 85c7b910 c8bb6d98 8e920e64 nt!IopfCompleteRequest+0x4b08e920e3c 82e2db03 863f4d68 c8bb6d03 00000004 pci!PciBusDevicePowerCompletion+0x628e920e64 82e9aa63 00000000 85c7b910 c8bb6d03 nt!PopRequestCompletion+0x388e920e8c 82e8f933 00000000 85c7b910 889e63d8 nt!IopUnloadSafeCompletion+0x4a8e920ed0 8c2c3573 89f00770 8e920efc 8c2c3425 nt!IopfCompleteRequest+0x1288e920edc 8c2c3425 859eda60 85c7b910 00000000 ACPI!ACPIDeviceIrpCompleteRequest+0x278e920efc 8c2c3777 89f00770 8c2e3bb8 8c2e3b98 ACPI!ACPIDeviceCompleteRequest+0x938e920f20 8c2c3ba6 8c2e3b78 8c2e1a6c 00000001 ACPI!ACPIDevicePowerProcessGenericPhase+0x718e920f48 82e8f1b5 8c2e3b40 00000000 00000000 ACPI!ACPIDevicePowerDpc+0x1848e920fa4 82e8f018 8e900120 85a7baf0 00000000 nt!KiExecuteAllDpcs+0xf98e920ff4 82e8e7dc 8eb49b54 00000000 00000000 nt!KiRetireDpcList+0xd58e920ff8 8eb49b54 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2cWARNING: Frame IP not in any known module. Following frames may be wrong.82e8e7dc 00000000 0000001a 00d6850f bb830000 0x8eb49b54STACK_COMMAND: kbSYMBOL_STACK_INDEX: 1SYMBOL_NAME: pci!PciBusDevicePowerCompletion+62FOLLOWUP_NAME: MachineOwnerMODULE_NAME: pciIMAGE_NAME: pci.sysDEBUG_FLR_IMAGE_TIMESTAMP: 4ce788e5IMAGE_VERSION: 6.1.7601.17514FAILURE_BUCKET_ID: 0x44_pci!PciBusDevicePowerCompletion+62BUCKET_ID: 0x44_pci!PciBusDevicePowerCompletion+62ANALYSIS_SOURCE: KMFAILURE_ID_HASH_STRING: km:0x44_pci!pcibusdevicepowercompletion+62

seems to work now

ok, I tested it with a 2008 VM and I can't get it installed. WUSA and also pkgmgr fail to install the update.

what is the "Like this" button good for? I only see "You have reached your quota of positive votes for the day" when I click it.

country and OS is now shown again

and the used OS is no longer shown.

Thanks for the update. what else is new?

have you applied the posted theme?

I think it is wrong to patch XP. Now the users think they still get patches for all issues and will never go to Windows 7.

your TOSHIBA MK3265GSXN is a slow 5400rpm drive. You can't expect miracles from such a slow drive. Get an SSD. You can find good ones with 200GB for 100€.

I see no reason why the update doesn't install on a Server 2008. The update.mum doesn't include any Vista checks.

what do you mean with cursor issue? The largest issue with your boot is, that your HDD is very busy during boot.

the update is for Vista Sp1 and I think you use Server 2008 Sp2, so the update can't be installed.

this disable the Eventlogs and you can't find information if you have issues.

the issues come from mixing versions from different SP levels. Use the Server 2003 as workstation OS which supports PAE and can use all RAM:

Welcome to msfn

the string for closing apps is not translated to German:

yeah. Win8, Office 2013, VS2012/2013 all GUIs are broken