Solved Computer freezing, BSOD, no particular reason

[sebasebus]

Hi!

I'm getting this problem. I turn computer on and it either immedately freezes, and I have to restart it with the power nutton or it's giving me BSOD and restarts. After multiple restarts it usually starts working and it works for few days without turning off, no problem. I had a graphic card that was refurbished, and i thought this is the issue so I recently replaced it with geforce 560. Well I still have this problem. I'm starting to think this is issue with either my mother board or maybe hard drive? Or maybe even CPU? How can I check? What should I do?

Im using ASUS with the phenom x2 3.3 ghz (6cores) 12 gb ram, geforce 560

 

[sebasebus]

Oh I should add that it happens particularly often if I have two monitors connected. Sometimes even the bios message doesnt show up when i start computer it just turns on and stays dark. Currently I disconnected second screen, since I trned on computer without second screen it froze once and I got BSOD twice.

 

[lehnerus2000]

Have you checked that all of your power and data connectors are properly seated?

I had problems booting when I had a loose power connector on my DVD drive.

 

[sebasebus]

I think everything should be fine with connectors but I'll check again. I managed to get the contents of the dump file. Maybe somebody will know what to do with that?


Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff880c3088281, 2, 0, fffff80002e9e4e6}

Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+82f )

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: fffff880c3088281, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002e9e4e6, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ca100
fffff880c3088281

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiDeferredReadyThread+82f
fffff800`02e9e4e6 488b01 mov rax,qword ptr [rcx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff88005dcee70 -- (.trap 0xfffff88005dcee70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007fffff96000 rbx=0000000000000000 rcx=fffff880c3088281
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e9e4e6 rsp=fffff88005dcf000 rbp=fffffa800c7ab060
r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
r11=fffffa8009a1b8e8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiDeferredReadyThread+0x82f:
fffff800`02e9e4e6 488b01 mov rax,qword ptr [rcx] ds:fffff880`c3088281=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e971e9 to fffff80002e97c40

STACK_TEXT:
fffff880`05dced28 fffff800`02e971e9 : 00000000`0000000a fffff880`c3088281 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05dced30 fffff800`02e95e60 : fffffa80`09aa2060 fffff880`05dcef00 00000000`00000000 fffff880`03088180 : nt!KiBugCheckDispatch+0x69
fffff880`05dcee70 fffff800`02e9e4e6 : 00000000`00000000 00000000`00000001 fffffa80`09a1ba78 fffffa80`0c5d3b30 : nt!KiPageFault+0x260
fffff880`05dcf000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadyThread+0x82f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDeferredReadyThread+82f
fffff800`02e9e4e6 488b01 mov rax,qword ptr [rcx]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiDeferredReadyThread+82f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

FAILURE_BUCKET_ID: X64_0xA_nt!KiDeferredReadyThread+82f

BUCKET_ID: X64_0xA_nt!KiDeferredReadyThread+82f

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: fffff880c3088281, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002e9e4e6, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: fffff880c3088281

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiDeferredReadyThread+82f
fffff800`02e9e4e6 488b01 mov rax,qword ptr [rcx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff88005dcee70 -- (.trap 0xfffff88005dcee70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007fffff96000 rbx=0000000000000000 rcx=fffff880c3088281
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e9e4e6 rsp=fffff88005dcf000 rbp=fffffa800c7ab060
r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
r11=fffffa8009a1b8e8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiDeferredReadyThread+0x82f:
fffff800`02e9e4e6 488b01 mov rax,qword ptr [rcx] ds:fffff880`c3088281=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e971e9 to fffff80002e97c40

STACK_TEXT:
fffff880`05dced28 fffff800`02e971e9 : 00000000`0000000a fffff880`c3088281 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05dced30 fffff800`02e95e60 : fffffa80`09aa2060 fffff880`05dcef00 00000000`00000000 fffff880`03088180 : nt!KiBugCheckDispatch+0x69
fffff880`05dcee70 fffff800`02e9e4e6 : 00000000`00000000 00000000`00000001 fffffa80`09a1ba78 fffffa80`0c5d3b30 : nt!KiPageFault+0x260
fffff880`05dcf000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadyThread+0x82f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDeferredReadyThread+82f
fffff800`02e9e4e6 488b01 mov rax,qword ptr [rcx]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiDeferredReadyThread+82f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

FAILURE_BUCKET_ID: X64_0xA_nt!KiDeferredReadyThread+82f

BUCKET_ID: X64_0xA_nt!KiDeferredReadyThread+82f

Followup: MachineOwner

 

[lehnerus2000]

It seemed to be complaining about a driver (I don't have much experience reading dump files though).

Can you boot using "Safe Mode" and reinstall (or uninstall) whichever driver you installed most recently?

I had an NVidia XP driver install failure, which disabled all of my operating systems (Ubuntu, XP & W7)!
I had to re-image my machine to recover from it.

 

[sebasebus]

Thing is I'm getting this for a while now. No more then two days ago i replaced the graphic card and I was forced to reinstall the windows, so I have a new clean installation of Windows 7 with barely anything on the hard drive. And still the same issue

 

[lehnerus2000]

Do you have another graphics card (or onboard graphics)?
You could remove the new card and see if that fixes the problem.

 

[mgp1964]

Boot up in safe mode and see if your problem remains.

 

[sebasebus]

Ok so it seems my RAM was faulty or at least two different brands were incompatible. after removing 2x2gb of Ram that came with system originally and leaving only 2x4gb I purchased separetely everything seems to be fine. I'm using system for few days now and not even single BSOD.

Thanks for the help everybody!