Hi gzaf and welcome to SF!
I looked at your dumps and you see the causes are all over the place. Which can mean 2 things: either more than one cause or some underlying incompatibility/low level driver poblem. A system that runs Vista OK shouldn't have problems with windows 7 tho. You said the trouble started after the update to W7.You didn't do a clean install, did you?
Before I start guesswork I need some more information. Please follow this tut
https://www.sevenforums.com/crashes-d...tructions.html
This should have been done by now already:
Learn how to install Windows 7 Service Pack 1 (SP1)
Code:
IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 8348769f, Address of system function (system call routine)
Arg2: 807d0a02, Current IRQL
Arg3: 00000000, 0
Arg4: 00000000, 0
------------------------------------------------------------------------------------
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: ffe0fffe, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8366b391, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
--------------------------------------------------------------------------------
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 83484ec3, The address that the exception occurred at
Arg3: 8b318c30, Exception Record Address
Arg4: 8b318810, Context Record Address
----------------------------------------------------------------------------
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 807cf120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
--------------------------------------------------------------------------------------------------
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 835d914b, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 834a0d02, address which referenced memory
-DG
Quote