New
#1
Randomly Reboots BSOD for months!
Hi there
I have some trouble with my pc,
It's crashing and rebooting randomly especially when playing games.
This has been going on for months and several times I thought I had the solution but then it started again. I tried three different types of OS: XP, Vista and currently 7. Replaced my PSU with an Antec TruePower 750, replaced my ram several times and tested them, no luck. Updated my drivers by hand with removing them first and updating through driver updaters. My ATI Hd4850 goes no higher than 65 degrees celcius which is pretty low for these kind of cards I think. My CPU is not warmer than 50 degrees celsius. I read something about broken capcitors but I looked and couldn't find anything. I raised the voltage on my RAM by 0.1 it seemed to help for a few days, and it only happens when i'm using more than 1 stick of RAM. I'm thinking my motherboards is broken , but it's not very nice when you find out the replaced hardware wasn't faulty and you spent 100 bucks on it, so I would really be sure of it before replacing .
And o yeah I checked everything for rootkits,spyware, malware and virusses. Do you guys have any suggestions? Here are my minidumps and Specs:
Antec truePower 550
Ati Sapphire HD4850
Kingston KVR800D2N5K2/4G
E8400 Intel Core 2Duo
Crashes:
Code:SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002f7ce39, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88008866eb0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: +0 fffff800`02f7ce39 488b4910 mov rcx,qword ptr [rcx+10h] CONTEXT: fffff88008866eb0 -- (.cxr 0xfffff88008866eb0) Unable to read context, Win32 error 0n30 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002c8aa3a to fffff88003c3a9c2 STACK_TEXT: fffff800`00b9cc58 fffff800`02c8aa3a : 00000000`002cd0a9 fffffa80`0311c698 fffff800`02e03c40 00000000`00000001 : 0xfffff880`03c3a9c2 fffff800`00b9cc60 00000000`002cd0a9 : fffffa80`0311c698 fffff800`02e03c40 00000000`00000001 fffff800`02df5e80 : 0xfffff800`02c8aa3a fffff800`00b9cc68 fffffa80`0311c698 : fffff800`02e03c40 00000000`00000001 fffff800`02df5e80 fffff800`02c88697 : 0x2cd0a9 fffff800`00b9cc70 fffff800`02e03c40 : 00000000`00000001 fffff800`02df5e80 fffff800`02c88697 00000001`4793fa73 : 0xfffffa80`0311c698 fffff800`00b9cc78 00000000`00000001 : fffff800`02df5e80 fffff800`02c88697 00000001`4793fa73 00000001`0001d480 : 0xfffff800`02e03c40 fffff800`00b9cc80 fffff800`02df5e80 : fffff800`02c88697 00000001`4793fa73 00000001`0001d480 00000001`4793fa73 : 0x1 fffff800`00b9cc88 fffff800`02c88697 : 00000001`4793fa73 00000001`0001d480 00000001`4793fa73 00000000`00000080 : 0xfffff800`02df5e80 fffff800`00b9cc90 00000001`4793fa73 : 00000001`0001d480 00000001`4793fa73 00000000`00000080 fffffa80`0311c600 : 0xfffff800`02c88697 fffff800`00b9cc98 00000001`0001d480 : 00000001`4793fa73 00000000`00000080 fffffa80`0311c600 400000c2`400000c1 : 0x1`4793fa73 fffff800`00b9cca0 00000001`4793fa73 : 00000000`00000080 fffffa80`0311c600 400000c2`400000c1 fffff800`400000c3 : 0x1`0001d480 fffff800`00b9cca8 00000000`00000080 : fffffa80`0311c600 400000c2`400000c1 fffff800`400000c3 00000000`ea4db85b : 0x1`4793fa73 fffff800`00b9ccb0 fffffa80`0311c600 : 400000c2`400000c1 fffff800`400000c3 00000000`ea4db85b fffff800`00b96080 : 0x80 fffff800`00b9ccb8 400000c2`400000c1 : fffff800`400000c3 00000000`ea4db85b fffff800`00b96080 fffffa80`018c7740 : 0xfffffa80`0311c600 fffff800`00b9ccc0 fffff800`400000c3 : 00000000`ea4db85b fffff800`00b96080 fffffa80`018c7740 00000000`00000000 : 0x400000c2`400000c1 fffff800`00b9ccc8 00000000`ea4db85b : fffff800`00b96080 fffffa80`018c7740 00000000`00000000 0000051d`c93063b0 : 0xfffff800`400000c3 fffff800`00b9ccd0 fffff800`00b96080 : fffffa80`018c7740 00000000`00000000 0000051d`c93063b0 0000051d`c93071ed : 0xea4db85b fffff800`00b9ccd8 fffffa80`018c7740 : 00000000`00000000 0000051d`c93063b0 0000051d`c93071ed fffff800`02c831a2 : 0xfffff800`00b96080 fffff800`00b9cce0 00000000`00000000 : 0000051d`c93063b0 0000051d`c93071ed fffff800`02c831a2 fffff800`00b96080 : 0xfffffa80`018c7740 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: CORRUPT_MODULELIST Followup: MachineOwner 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: fffff8060196cd3c, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff8800185944c, address which referenced memory Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd fffff8060196cd3c CURRENT_IRQL: 0 FAULTING_IP: +0 fffff880`0185944c ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 LAST_CONTROL_TRANSFER: from fffff80002c8c469 to fffff80002c8cf00 STACK_TEXT: fffff800`00b9c1b8 fffff800`02c8c469 : 00000000`0000000a fffff806`0196cd3c 00000000`00000002 00000000`00000001 : 0xfffff800`02c8cf00 fffff800`00b9c1c0 00000000`0000000a : fffff806`0196cd3c 00000000`00000002 00000000`00000001 fffff880`0185944c : 0xfffff800`02c8c469 fffff800`00b9c1c8 fffff806`0196cd3c : 00000000`00000002 00000000`00000001 fffff880`0185944c 00000000`00000000 : 0xa fffff800`00b9c1d0 00000000`00000002 : 00000000`00000001 fffff880`0185944c 00000000`00000000 00000000`00000000 : 0xfffff806`0196cd3c fffff800`00b9c1d8 00000000`00000001 : fffff880`0185944c 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2 fffff800`00b9c1e0 fffff880`0185944c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1 fffff800`00b9c1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`0185944c STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: CORRUPT_MODULELIST Followup: MachineOwner 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: fffffa0003aedf60, memory referenced Arg2: 0000000000000002, IRQL Arg3: 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: fffff80002ccd1c2, address which referenced memory Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd fffffa0003aedf60 CURRENT_IRQL: 0 FAULTING_IP: +0 fffff800`02ccd1c2 48894108 mov qword ptr [rcx+8],rax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from fffff80002cc8469 to fffff80002cc8f00 STACK_TEXT: fffff800`00ba23f8 fffff800`02cc8469 : 00000000`0000000a fffffa00`03aedf60 00000000`00000002 00000000`00000001 : 0xfffff800`02cc8f00 fffff800`00ba2400 00000000`0000000a : fffffa00`03aedf60 00000000`00000002 00000000`00000001 fffff800`02ccd1c2 : 0xfffff800`02cc8469 fffff800`00ba2408 fffffa00`03aedf60 : 00000000`00000002 00000000`00000001 fffff800`02ccd1c2 00000000`00000001 : 0xa fffff800`00ba2410 00000000`00000002 : 00000000`00000001 fffff800`02ccd1c2 00000000`00000001 00000000`00000000 : 0xfffffa00`03aedf60 fffff800`00ba2418 00000000`00000001 : fffff800`02ccd1c2 00000000`00000001 00000000`00000000 00000000`00000000 : 0x2 fffff800`00ba2420 fffff800`02ccd1c2 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1 fffff800`00ba2428 00000000`00000001 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`02ccd1c2 fffff800`00ba2430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: CORRUPT_MODULELIST Followup: MachineOwner
Last edited by Mkkl; 10 Jan 2010 at 13:55. Reason: forgot something