Random BSOD NEED HELP! T_T W7 Ultimate 64bit

Thank you very much, Dave. I appreciate it.

Those CPU temperatures are Very High.

I would recommend to stop using the computer, now.

Before you have permanent damage to the CPU and motherboard.

Take it to your local shop and have them clean off the thermal paste (TIM) and apply new thermal paste and re-seat the CPU cooler.

This must be done correctly to prevent excessively high temperatures.

Looks like the CPU cooler came loose or a problem with the thermal paste.

We can address the other issues when the temperature is under control.

High temps can cause BSoDs.

If you have any questions, find another computer to use and reply here.

Ashwolves, thank you for the compliments. We work as a team here in order to give the poster the best help possible. Dave is giving you spot on, solid advice. Your overheating problem must be taken care of before he can begin to help with the RAM problem.

Checked TEAM ELITE is not there, but i have been using the same brand for years and I have never had a problem about this until this few months, what do you think is the problem ?

RAM must be compatible with the motherboard. Incompatible RAM can definitely cause problems. It does not matter how good the RAM is quality wise, it it is not compatible with your motherboard, you will likely have problems.

All four of your latest dumps are hardware errors and and blame or point to memory as the cause of the crashes.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002b132d4, fffff880009a99d8, fffff880009a9230}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+823 )

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

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

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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002b132d4, The address that the exception occurred at
Arg3: fffff880009a99d8, Exception Record Address
Arg4: fffff880009a9230, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MmZeroPageThread+823
fffff800`02b132d4 4d8b3f          mov     r15,qword ptr [r15]

EXCEPTION_RECORD:  fffff880009a99d8 -- (.exr 0xfffff880009a99d8)
ExceptionAddress: fffff80002b132d4 (nt!MmZeroPageThread+0x0000000000000823)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880009a9230 -- (.cxr 0xfffff880009a9230)
rax=0000000000000000 rbx=fa80044b716004c0 rcx=fffff880009a9ba8
rdx=0000000000000001 rsi=000000000009340d rdi=0000000000000002
rip=fffff80002b132d4 rsp=fffff880009a9c10 rbp=0000000000000000
 r8=fffffa8000e06670  r9=0000000000000000 r10=fffff80002d04400
r11=fffff880009a9be0 r12=0000000000000000 r13=0000000000000000
r14=0000058000000000 r15=fa80044b716004c0
iopl=0         nv up ei ng nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
nt!MmZeroPageThread+0x823:
fffff800`02b132d4 4d8b3f          mov     r15,qword ptr [r15] ds:002b:fa80044b`716004c0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d020e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!MmZeroPageThread+823
fffff800`02b132d4 4d8b3f          mov     r15,qword ptr [r15]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002d6f166 to fffff80002b132d4

STACK_TEXT:  
fffff880`009a9c10 fffff800`02d6f166 : fffffa80`024b93b0 00000000`00000080 fffffa80`024b9890 fffff800`02aaa479 : nt!MmZeroPageThread+0x823
fffff880`009a9d40 fffff800`02aaa486 : fffff800`02c44e80 fffffa80`024b93b0 fffff800`02c52c40 00060b01`30025003 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmZeroPageThread+823

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff880009a9230 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+823

BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+823

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002dc6ac1, fffff8800622bab0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+186 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002dc6ac1, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800622bab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObpWaitForMultipleObjects+186
fffff800`02dc6ac1 488b4a20        mov     rcx,qword ptr [rdx+20h]

CONTEXT:  fffff8800622bab0 -- (.cxr 0xfffff8800622bab0)
rax=0000000000000000 rbx=fffff8a000fefb00 rcx=fffff80002a5c000
rdx=0000000000000000 rsi=000000000000003a rdi=fffffa800597f010
rip=fffff80002dc6ac1 rsp=fffff8800622c490 rbp=fffff8800622cca0
 r8=0000000000000008  r9=fffff8a001010000 r10=fffffa800565c6d0
r11=fffffffffffffd80 r12=fffff8800622cb68 r13=fffff8a000e43400
r14=0000000000000039 r15=0000000000000040
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ObpWaitForMultipleObjects+0x186:
fffff800`02dc6ac1 488b4a20        mov     rcx,qword ptr [rdx+20h] ds:002b:00000000`00000020=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002dc6ac1

STACK_TEXT:  
fffff880`0622c490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x186


FOLLOWUP_IP: 
nt!ObpWaitForMultipleObjects+186
fffff800`02dc6ac1 488b4a20        mov     rcx,qword ptr [rdx+20h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpWaitForMultipleObjects+186

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff8800622bab0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+186

BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+186

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff80002a84b5c, fffff8800338dfd8, fffff8800338d830}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002a84b5c, The address that the exception occurred at
Arg3: fffff8800338dfd8, Exception Record Address
Arg4: fffff8800338d830, Context Record Address

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: 
+5cbc952f01a2dd98
fffff800`02a84b5c 0fb742c0        movzx   eax,word ptr [rdx-40h]

EXCEPTION_RECORD:  fffff8800338dfd8 -- (.exr 0xfffff8800338dfd8)
Cannot read Exception record @ fffff8800338dfd8

CONTEXT:  fffff8800338d830 -- (.cxr 0xfffff8800338d830)
Unable to read context, Win32 error 0n30

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ae5a3a to fffff880045859c2

STACK_TEXT:  
fffff800`041e6c98 fffff800`02ae5a3a : 00000000`0023c380 fffffa80`043558a8 fffff800`02c5ec40 00000000`00000001 : 0xfffff880`045859c2
fffff800`041e6ca0 00000000`0023c380 : fffffa80`043558a8 fffff800`02c5ec40 00000000`00000001 fffff800`02c50e80 : 0xfffff800`02ae5a3a
fffff800`041e6ca8 fffffa80`043558a8 : fffff800`02c5ec40 00000000`00000001 fffff800`02c50e80 fffff800`02ae3697 : 0x23c380
fffff800`041e6cb0 fffff800`02c5ec40 : 00000000`00000001 fffff800`02c50e80 fffff800`02ae3697 00000000`a6381606 : 0xfffffa80`043558a8
fffff800`041e6cb8 00000000`00000001 : fffff800`02c50e80 fffff800`02ae3697 00000000`a6381606 00000000`a63815fa : 0xfffff800`02c5ec40
fffff800`041e6cc0 fffff800`02c50e80 : fffff800`02ae3697 00000000`a6381606 00000000`a63815fa 00000000`a6381606 : 0x1
fffff800`041e6cc8 fffff800`02ae3697 : 00000000`a6381606 00000000`a63815fa 00000000`a6381606 00000000`000000dd : 0xfffff800`02c50e80
fffff800`041e6cd0 00000000`a6381606 : 00000000`a63815fa 00000000`a6381606 00000000`000000dd fffffa80`04355810 : 0xfffff800`02ae3697
fffff800`041e6cd8 00000000`a63815fa : 00000000`a6381606 00000000`000000dd fffffa80`04355810 400000c2`400000c1 : 0xa6381606
fffff800`041e6ce0 00000000`a6381606 : 00000000`000000dd fffffa80`04355810 400000c2`400000c1 00000009`400000c3 : 0xa63815fa
fffff800`041e6ce8 00000000`000000dd : fffffa80`04355810 400000c2`400000c1 00000009`400000c3 00000000`a0d3b1bf : 0xa6381606
fffff800`041e6cf0 fffffa80`04355810 : 400000c2`400000c1 00000009`400000c3 00000000`a0d3b1bf fffff800`041e0080 : 0xdd
fffff800`041e6cf8 400000c2`400000c1 : 00000009`400000c3 00000000`a0d3b1bf fffff800`041e0080 fffffa80`024b89e0 : 0xfffffa80`04355810
fffff800`041e6d00 00000009`400000c3 : 00000000`a0d3b1bf fffff800`041e0080 fffffa80`024b89e0 00000000`00000000 : 0x400000c2`400000c1
fffff800`041e6d08 00000000`a0d3b1bf : fffff800`041e0080 fffffa80`024b89e0 00000000`00000000 00000298`89153075 : 0x9`400000c3
fffff800`041e6d10 fffff800`041e0080 : fffffa80`024b89e0 00000000`00000000 00000298`89153075 00000298`891538af : 0xa0d3b1bf
fffff800`041e6d18 fffffa80`024b89e0 : 00000000`00000000 00000298`89153075 00000298`891538af fffff800`02c5ec40 : 0xfffff800`041e0080
fffff800`041e6d20 00000000`00000000 : 00000298`89153075 00000298`891538af fffff800`02c5ec40 fffff800`041e0080 : 0xfffffa80`024b89e0


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
---------

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, b43b, bf6100016872}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29fd7 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000b43b
Arg4: 0000bf6100016872

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002aefa08 to fffff80002a7ff00

STACK_TEXT:  
fffff880`094d99c8 fffff800`02aefa08 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0000b43b : nt!KeBugCheckEx
fffff880`094d99d0 fffff800`02a9a1a6 : 00000000`00000001 00000000`0d28a000 fffff880`094d9c20 fffff680`00069450 : nt! ?? ::FNODOBFM::`string'+0x29fd7
fffff880`094d9ac0 fffff800`02a7dfee : 00000000`00000001 00000000`0d289ffc 00000000`0f340d01 00000000`0014b568 : nt!MmAccessFault+0x5c6
fffff880`094d9c20 00000000`705f872e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0014b420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x705f872e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+29fd7
fffff800`02aefa08 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+29fd7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29fd7

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29fd7

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

Priorities:

1. Solve your cooling problem before using you computer any further.

2. Purchase and install compatible RAM

3. Follow Dave's advice.

Arctic cooling MX2 or Arctic Silver 5 are good.

Are you going to do this yourself?

If you do, just be sure to apply it correctly. Applying too much or too little and/or not getting the CPU cooler attached properly will cause excessive heat on your CPU.

First clean with 70%+ rubbing (isopropyl) alcohol, let dry before applying thermal paste.

Check for thermal paste application guides.

Arctic Silver 5 is a good guide.

Let us know if you have any questions.

Probably a combination of heat and incompatible RAM. You really should not be using the computer. You are in danger of frying your CPU.

EDIT:
I just read your last two posts.

WARNING

You must stop using your computer before the CPU and Motherboard are permanently damaged.

This can not only damage your computer it can result in an actual fire.

Your CPU temperature limit is 71c. your minimum temps are above this. Your max temp from your previous post was 100c, this is very dangerous.

You must stop using it now.

Get the thermal paste and remove the CPU cooler and re-apply the paste before using it again.

If your temps are above 65c, stop, shut down your computer.

/Edit


As mentioned, you need to get the temperatures down on your CPU, they are extremely high and will damage your CPU and motherboard.
Re-apply the thermal paste between the CPU and the CPU cooler.
Post your CPU temps from Real Temp when finished, with system at idle and with a full load.
Your maximum CPU temp is 71c(see Tcase at this link), you should not exceed these temps, if the temps are above 65c, shut down the program you are running. If the temps are still above 65c, shut down your computer.
Your CPU temps under stress conditions should not go above 60c, this will leave you a safety margin.
This will be task #1.

After this is repaired and your system temps are down to acceptable levels, we can start troubleshooting the other possibilities.

Let's take this slow, and get thorough information on each step.
Tell us what steps you tried and the results, try to be exact with good details.

Ashwolves said:

Dave76 said:

When testing RAM with memtest86+ you need to test for bad RAM and any possible bad motherboard RAM slots.

Follow these steps in the tutorial: How to Test and Diagnose RAM Issues with Memtest86+

I will do that later before I sleep I have lots of things to do today. =(
Is that ok with you ?

Of coarse, take your time, we can do this when you have the time.
When you get the CPU thermal paste replaced and run a temp check, you can run memtest86+ as described in the tutorial.
This will be task #2.
Always monitor your temps during any/all stress testing, memtest86+, Prime95, and all games, until all troubleshooting is done and you have no further BSoDs.

Ashwolves said:

I don't know but 2 weeks ago I reformated my computer because of the same bsod problem, but before I installed it I got a problem again on the win 7 Installation process the files can't be Installed or expand the process won't go further than 0% and gives an error. I researched about this problem and guess what, Its memory problem or a bad copy of windows.

But I try to Install Old OS's Including Ubuntu they won't Install, but by computing Instinct I guess or something I decided to put my 2 mem stick to the other mem slots. IT WORKED.

About adjusting RAM settings can you teach me about it, because my motherboard has built in Overclock system and I checked the bios and its all on AUTO and I checked the Mobo manual, the description tells me that AUTO mode means - to Load optimal settings for the system.

We will go through the RAM settings after the first two tasks are completed.

Ashwolves said:

What temperature my mobos temp last seen today is around 40°C-CPU 90°C

how can i check the mem's temp ?

As mentioned, 90c is extremely high, you should run your computer at these temps.

There is no way of monitoring the RAM temps.
An additional sensor would be required.

Ashwolves said:

I'm using real temp at the moment real temp tells me its:

Minimum -> 78°C 78°C 70°C 70°C <-3pm
Maximum ->94°C 92°C 85°C 85°C <-2pm

Posting it now, btw the cpu temp on the pic was taken earlier.

As mentioned, your minimum temps are past the shut down limit.

Ashwolves said:

NO I'm scared of doing OC unless I have water cooling system.

That is a good decision, until your computer is running well and cool, do not attempt any overclocking.

Ashwolves said:

I have an Asus BIOS updater for windows and Asus BIOS updater in the BIOS settings. It says that I can save my current BIOS settings before updating my BIOS if something goes wrong.

That is a good option.
We can review that at a later time.

Ashwolves said:

I have the hardcopy of my mobo manual right now so I'm ready to do what you want me to do. =p

For now just get more comfortable with your BIOS settings.
Read through it and let us know if you have any questions.

Ashwolves said:

Checked TEAM ELITE is not there, but i have been using the same brand for years and I have never had a problem about this until this few months, what do you think is the problem ?

I checked and used the snipping tool I'll post it here. ^^

I'm thinking of updating it on my own using Asus bios update what do you think Dave ?

We can try to get the RAM working, but you may have to find compatible RAM if there is no progress.

After some of the previous issues are dealt with we can come back to the BIOS update.

Ashwolves said:

Dave76 said:

#2.

Those temps are high.

What were you doing when you got these temps?

High stress at the time would still indicate that you have a cooling issue.

Check that all you fans are running.

Clean everything inside the case.

Are you running a stock CPU cooler?
You may need to consider getting a better one, the less expensive ones do a very good job of cooling, much better than the stock cooler.

Heat can slow down your system and cause BSoDs.

If your overclocking, return everything to optimum defaults until the other issues are sorted out.

Cleaned the CPU today there is a big cake of dust on the stock cooler, I almost panicked when I open my pc to check if there is any updates on my problem, my pc got multiple BSOD every after 5mins while checking the forums. Not only that when I decided to do system restore It BSOD, when I try to do system restore in safe mode it BSOD.

So I decided to clean my CPU FAN and VID CARD FAN and mem slots with a brush, load bios defaults and changed the CPU multiplier from 9 which is the default to 6 and I guess it did the trick I guess. But this is only a temp solution from what i can feel and see.

Dust build up is a common cause of over heating, be sure to clean all the dust from your case. This should be done on a regular schedule, every two months.

Ashwolves said:

I noticed on the cpu chip and the stock cooler there is a dry gray substance or something, does that mean I have to buy a cooling gel or something for the cpu ?

This is an indication that your CPU thermal paste was either not applied correctly or needs to be checked.

Ashwolves said:

Dave76 said:

Your RAM can be faulty and still run without errors some of the time. But, you will likely still get BSoDs.

The anti-virus can cause BSoDs, for trouble shooting, un-install it ant run MSE, as mentioned previously.

Uninstalled it and installed MSE so I'm ready to kill this BSOD's once and for all with all your help zigzag, carl and dave. ^^

Good choice.

Ashwolves said:

Btw I attached also the BSOD that I experienced this morning that I almost panicked. >.<

I believe Carl has taken a look at it.