Question Multiple BSODs ?

[yyaas0]

Hi,
I've been getting a blue screen for about a couple months now.
the system works fine in stress tests and does not crash (OCCT,prime95,furmark,memtest). so far i have changed PSU,ssd,motherboard and ram. i have tested them all separately and no problem. it does not crash in stress tests. BIOS and drivers are the latest version.
XMP enabled. I've also gotten blue screens when xmp was disabled so I don't think that's what triggered it. also the motherboard has this ram in the supported ram section, normally I should be able to use it with xmp (if xmp is the problem).
I reinstalled the driver with DDU.

Specs:
GPU: RTX 3070
RAM : GSKILL Trident Z neo 16x2 32GB 3200 Mhz CL 16 F4-3200C16D-32GTZN
CPU: Ryzen 7 3800xt
motherboard: ASUS B550-F GAMING
SSD & HDD : 2 TB SSD ZP2000GM30021 & 2TB HDD ST2000DM008
PSU : ROG-STRIX-750G 80+ GOLD
OS : Windows 11 (despite reinstalling Windows many times the problem is not solved)

minidumps:
https://disk.yandex.com.tr/d/GLXAkWw9aDkzJA

Yandex

Her şey bulunur

disk.yandex.com.tr

https://disk.yandex.com.tr/d/X4nSN4eroTretw

Can you help me with this?

 

[Satan-IR]

Welcome to the forums!

Since you said you reinstalled Windows after changing hardware I'm thinking this might be a RAM issue.

The debugger says "*** Memory manager detected 71680 instance(s) of page corruption, target is likely to have memory corruption.".

I would test memroy sticks one at a time with MemTest86. You can make a bootale MemTest on a USB flash. Boot system with that a let it run at least 4 passes to see if you have a bad RAM module. Windows has a builtin Memory Diagnostic Tool as well.

Also you have two 16GB RAM which is enough to run Windows and even some games. Another thing you can try is take one of the out and use only one 16GB module in the relevant slot for a few days and see if it gives to any BSODs. That way too you can single out the possibly faulty module.

 

[yyaas0]

Welcome to the forums!

Since you said you reinstalled Windows after changing hardware I'm thinking this might be a RAM issue.

The debugger says "*** Memory manager detected 71680 instance(s) of page corruption, target is likely to have memory corruption.".

I would test memroy sticks one at a time with MemTest86. You can make a bootale MemTest on a USB flash. Boot system with that a let it run at least 4 passes to see if you have a bad RAM module. Windows has a builtin Memory Diagnostic Tool as well.

Also you have two 16GB RAM which is enough to run Windows and even some games. Another thing you can try is take one of the out and use only one 16GB module in the relevant slot for a few days and see if it gives to any BSODs. That way too you can single out the possibly faulty module.

Hi @Satan-IR Thanks for response but 2 days ago I did a memtest86 and found no errors in the memory.

 

[yyaas0]

Hi @Satan-IR Thanks for response but 2 days ago I did a memtest86 and found no errors in the memory.

also the motherboard is very new (I had blue screens like this on the previous motherboard) but when I tested the ram and motherboards I found no errors.

 

[Satan-IR]

Hi @Satan-IR Thanks for response but 2 days ago I did a memtest86 and found no errors in the memory.

I've seen it in more than one occasion that some bad RAM are not picked up by MemTest and similar tests either.

Also getting BSODs on two different board with same RAM (if that's the case) makes RAM even more likely to be the culprit.

Also I would try to run the system with XMP disabled and see if it causes less or no BSODs.

 

[yyaas0]

I've seen it in more than one occasion that some bad RAM are not picked up by MemTest and similar tests either.

Also getting BSODs on two different board with same RAM (if that's the case) makes RAM even more likely to be the culprit.

Also I would try to run the system with XMP disabled and see if it causes less or no BSODs.

Hi @Satan-IR ,
actually you are right but I don't get bsod when xmp is disabled. the system doesn't work stably when xmp is on. i also changed ram 2 times and encountered the same xmp problems. the xmp profile doesn't work stably even though it is in the supported ram section of the motherboard. now i have xmp disabled and i can use it without any problems. no crashes in games or crashes in browsers. how can i solve this. the latest version of bios. I want to use it with xmp profile how can i run my ram at 3200 mhz?
I was using G.SKILL before and I changed the ram because of crashes, but the new ram I bought does not work stably in xmp. for example, crashes can occur within 1 week in an unpredictable way. it does not crash in stress tests.
your help is appreciated.

 

[Satan-IR]

actually you are right but I don't get bsod when xmp is disabled. the system doesn't work stably when xmp is on.

Well that was exactly the point. If system in unstable with XMP enabled might mean problem with RAM or board can not handle it with that RAM.

I want to use it with xmp profile how can i run my ram at 3200 mhz?

What exatly do you mean by this? Above you listed your RAM as: "RAM : GSKILL Trident Z neo 16x2 32GB 3200 Mhz CL 16 F4-3200C16D-32GTZN"

Do you mean it's not rated as 3200Mhz and it's lower and you want to run it at 3200 with XMP? Or it's rated 3200 and you want to run it at higher clock with XMP?

it is in the supported ram section of the motherboard

You mean that RAM is in the motherboards QVL? If so yes it should work properly.

 

[yyaas0]

Well that was exactly the point. If system in unstable with XMP enabled might mean problem with RAM or board can not handle it with that RAM.


What exatly do you mean by this? Above you listed your RAM as: "RAM : GSKILL Trident Z neo 16x2 32GB 3200 Mhz CL 16 F4-3200C16D-32GTZN"

Do you mean it's not rated as 3200Mhz and it's lower and you want to run it at 3200 with XMP? Or it's rated 3200 and you want to run it at higher clock with XMP?


You mean that RAM is in the motherboards QVL? If so yes it should work properly.

Hi @Satan-IR ,
How can I run the xmp profile so there is no way to run the ram stably at 3200 mhz? I tried entering manual values but again it was not stable, crashes occur within a maximum of 1 week.

+ You mean that RAM is in the motherboards QVL? If so yes it should work properly.
- Yes, I'm talking about QVL. CL 16 F4-3200C16D-32GTZN I can find the model number in the ram section of the motherboard. Motherboard : B550-F GAMING xmp profile doesn't seem to be working properly. i just select Profile 1 on BIOS and at startup windows loads without errors but in the following days it can give blue screens (ram related) i used this ram "CL18 F4-3600C18D-32GTZR" before and it had the same problems. I changed ram 2 times.

 

[yyaas0]

Well that was exactly the point. If system in unstable with XMP enabled might mean problem with RAM or board can not handle it with that RAM.


What exatly do you mean by this? Above you listed your RAM as: "RAM : GSKILL Trident Z neo 16x2 32GB 3200 Mhz CL 16 F4-3200C16D-32GTZN"

Do you mean it's not rated as 3200Mhz and it's lower and you want to run it at 3200 with XMP? Or it's rated 3200 and you want to run it at higher clock with XMP?


You mean that RAM is in the motherboards QVL? If so yes it should work properly.

I got a blue screen error even though xmp was off.
minidump :
https://disk.yandex.com.tr/d/kXig7tSnNJ4PYw
https://disk.yandex.com.tr/d/z4gB6hdRvZUmOw @Satan-IR

 

[Satan-IR]

Hi @Satan-IR ,
How can I run the xmp profile so there is no way to run the ram stably at 3200 mhz? I tried entering manual values but again it was not stable, crashes occur within a maximum of 1 week.

+ You mean that RAM is in the motherboards QVL? If so yes it should work properly.
- Yes, I'm talking about QVL. CL 16 F4-3200C16D-32GTZN I can find the model number in the ram section of the motherboard. Motherboard : B550-F GAMING xmp profile doesn't seem to be working properly. i just select Profile 1 on BIOS and at startup windows loads without errors but in the following days it can give blue screens (ram related) i used this ram "CL18 F4-3600C18D-32GTZR" before and it had the same problems. I changed ram 2 times.

You have manuualy changed RAM-related variables in BIOC. You can reset BIOS to defaults so if anything is wrong that might fix it. Although when you enable an XMP profile that should change all variables to the preset that's set by the XMP profile.

You can also try reseting the CMOS. Turn PC off, turn PSU off, take you CMOS battery, when battery is out press and hold case power button for 10-20 seconds (to drain any residual power stored in the PSU capacitors), leave it like 5-10 mintes, then put battery back in, turn on and see how system runs with default BIOS settings.

You said you have changed motherboards and RAMs too. It's very odd that both series of components be faulty. Maybe some setting in the the BIOS is messed up. If you can post screenshots of BIOS setting pages for RAM or Memory and SPD tabs/pages from CPU-Z. We can take a look at them.

You can also take a look at this:
https://www.tomshardware.com/how-to/how-to-test-ram

 

[yyaas0]

Hi @Satan-IR ,
I have already tried resetting the BIOS and opening xmp as you said, but the computer crashes when idle. for example, it gives a blue screen when I wait 5 minutes on the desktop while doing nothing.
here is the SPD information when xmp is off;

https://imgur.com/83NUz5Q

https://imgur.com/pXX4TaP

I just tested with memtest86, should I run these tests with xmp enable or xmp disable?

 

[yyaas0]

You have manuualy changed RAM-related variables in BIOC. You can reset BIOS to defaults so if anything is wrong that might fix it. Although when you enable an XMP profile that should change all variables to the preset that's set by the XMP profile.

You can also try reseting the CMOS. Turn PC off, turn PSU off, take you CMOS battery, when battery is out press and hold case power button for 10-20 seconds (to drain any residual power stored in the PSU capacitors), leave it like 5-10 mintes, then put battery back in, turn on and see how system runs with default BIOS settings.

You said you have changed motherboards and RAMs too. It's very odd that both series of components be faulty. Maybe some setting in the the BIOS is messed up. If you can post screenshots of BIOS setting pages for RAM or Memory and SPD tabs/pages from CPU-Z. We can take a look at them.

You can also take a look at this:
https://www.tomshardware.com/how-to/how-to-test-ram

BIOS page looks like this when xmp is activated. This is the xmp enable settings;

https://imgur.com/aoBZhsj

https://imgur.com/GXpbbSz

https://imgur.com/MrVGbWj

https://imgur.com/jo4QjNM

https://imgur.com/iXpskcu

https://imgur.com/lzDiPVT

@Satan-IR

 

[Satan-IR]

To make sure is this your motherboard here? If yes with that board and that Ryzen 7 3800xt RAM should be able to run at 3200Mhz natively and you don't need to activate XMP or DOCP if I'm not mistaken.

You didn't post screenshots or the Memory tab of CPU-Z (left of SPD) , that's where you can see with which profile and frequency the RAM is actually running.

Some of the BIOS shots miss some parts of the page. The 3rd BIOS shot shows RAM is running at 2133Mhz also Profile#1 of DOCP is selected/highlighted. But I guess this is before you apply the profile#1 and save changes to BIOS and reboot?

I just tested with memtest86, should I run these tests with xmp enable or xmp disable?

I would run diabled first and one stick at a time. Turn off system. Put one of the RAM sticks in slot B2. Boot with MemTest86 bootable run at least 4 passes. Note if RAM throws any errors and when finished repeat with other RAM stick. Although some RAM errors are not caught by MemTest86 either. So if it passed it's not a 100% guarantee.

Did you reset BIOS from wihtin BIOS settings then save changes? I would clear CMOS. Turn off. Take moterboard CMOS battery out. Short CLRTC headers with jumber or a screw driver. Wait 10-15 minutes and then put battery back in motherboard and power on.

 

[yyaas0]

Hi @Satan-IR ,
yes my motherboard is B550-F GAMING and the cpu is ryzen 7 3800xt but unfortunately they don't run at 3200 mhz by default. yes i took those photos through BIOS after selecting profile 1. can you look at the new BIOS photo after selecting profile 1 and booting?
new screenshot BIOS (after selecting and starting profile 1, I restarted the computer and viewed the BIOS.);

https://imgur.com/VvrHe2S

I also cleaned the BIOS battery and CMOS before but again the system was running unstable within certain days.

I think you are talking about the memory section in CPU-Z. I have now set the ram's at 3200 mhz (profile 1) and selected it and ran it. here is the screenshot you asked for;

https://imgur.com/E39AAnm

I also got a blue screen again while writing this message. (when I set the ram to 3200.)
minidump:
https://disk.yandex.com.tr/d/w7TsP2Ns235LVA

 

[yyaas0]

Hi @Satan-IR ,

https://imgur.com/A50sD1U

After clearing CMOS the system is running stable but after selecting the docp profile I get a warning like this, what is the reason for this?

 

[Satan-IR]

Hi @Satan-IR ,

https://imgur.com/A50sD1U

After clearing CMOS the system is running stable but after selecting the docp profile I get a warning like this, what is the reason for this?

It's not an easy way to say with certainty, Ryzen is kind of fussy with RAM, really sensitive to frequency/clock and so on. Maybe the board (with that CPU) can not run at that high clock with stability.

Does crashes BSODs happen as much or at all if you disable the RAM overclocking (DOCP)? If it runs with no problem at lower frequency it might indicate that the high RAM speed/freq. is what is causing the issues. More so because you said you have changed RAM and even if we assume the first kit/pack was faulty, getting a second faulty kit is highly unlikely.

Although you said it doens't happen when you stress test the system.

I also cleaned the BIOS battery and CMOS before but again the system was running unstable within certain days.

What happened in these certain days? Any repeatable patterns? Like running a certain game or a certain combination of apps?

I also got a blue screen again while writing this message. (when I set the ram to 3200.)

This could also make system instability caused by RAM running at higher speed more likely.

And to make sure the two 16GB RAM sticks came as a kit/pack right? You're not by any chance mixing RAM modules from different packs?

THREAD ffffe40a6540f080  Cid 4950.4764  Teb: 00000000002b1000 Win32Thread: ffffe40a681aa1b0 RUNNING on processor a
Not impersonating
GetUlongFromAddress: unable to read from fffff80358a0be4c
Owning Process            ffffe40a69fa60c0       Image:         cpuz.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      30300      
Context Switch Count      4636            
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000001401ab650
Stack Init ffff84044fd6bc70 Current ffff84044fd688e0
Base ffff84044fd6c000 Limit ffff84044fd66000 Call 0
Priority 15 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffff8404`4fd6b598 fffff803`5823b070 : 00000000`00000162 ffffe40a`6540f080 ffff9a0b`27807f38 00000000`ffffffff : nt!KeBugCheckEx
ffff8404`4fd6b5a0 fffff803`58014f07 : 00000000`00000000 ffff8404`4fd6b6f9 ffff8404`4fd6b838 00000000`00000000 : nt!KeAbPostRelease+0x225220
ffff8404`4fd6b5e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExReleasePushLockSharedEx+0x37

This is the dump of the BSOD you said happened when you were sending message. The application it points to is CPU-Z. This also makes RAM more likely to be faulty. Or a result of mixed RAM.

 

[yyaas0]

It's not an easy way to say with certainty, Ryzen is kind of fussy with RAM, really sensitive to frequency/clock and so on. Maybe the board (with that CPU) can not run at that high clock with stability.

Does crashes BSODs happen as much or at all if you disable the RAM overclocking (DOCP)? If it runs with no problem at lower frequency it might indicate that the high RAM speed/freq. is what is causing the issues. More so because you said you have changed RAM and even if we assume the first kit/pack was faulty, getting a second faulty kit is highly unlikely.

Although you said it doens't happen when you stress test the system.


What happened in these certain days? Any repeatable patterns? Like running a certain game or a certain combination of apps?



This could also make system instability caused by RAM running at higher speed more likely.

And to make sure the two 16GB RAM sticks came as a kit/pack right? You're not by any chance mixing RAM modules from different packs?

THREAD ffffe40a6540f080  Cid 4950.4764  Teb: 00000000002b1000 Win32Thread: ffffe40a681aa1b0 RUNNING on processor a
Not impersonating
GetUlongFromAddress: unable to read from fffff80358a0be4c
Owning Process            ffffe40a69fa60c0       Image:         cpuz.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      30300     
Context Switch Count      4636           
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000001401ab650
Stack Init ffff84044fd6bc70 Current ffff84044fd688e0
Base ffff84044fd6c000 Limit ffff84044fd66000 Call 0
Priority 15 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffff8404`4fd6b598 fffff803`5823b070 : 00000000`00000162 ffffe40a`6540f080 ffff9a0b`27807f38 00000000`ffffffff : nt!KeBugCheckEx
ffff8404`4fd6b5a0 fffff803`58014f07 : 00000000`00000000 ffff8404`4fd6b6f9 ffff8404`4fd6b838 00000000`00000000 : nt!KeAbPostRelease+0x225220
ffff8404`4fd6b5e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExReleasePushLockSharedEx+0x37

This is the dump of the BSOD you said happened when you were sending message. The application it points to is CPU-Z. This also makes RAM more likely to be faulty. Or a result of mixed RAM.

Hi @Satan-IR ,
on certain days I watch videos on youtube or when I'm watching a tv series and black screen and reboot issues when playing games. it gives me a blue screen or when I leave it empty on the desktop it gives me a blue screen within 5 minutes. but after cleaning the CMOS I didn't see any blue screen errors, I think there is a problem with the voltages and timings of the ram. I don't really understand how to solve this problem, the ram kits are not very old and my previous ram kit was not stable because it was 3600 mhz, so I bought the triden z neo /ryzen optimized) version, but again docp does not work properly.

no they are both the same ram so they are both using the same brand and model ram I can send you a picture of it if you want.
yes i usually get ram errors when i select 3200 mhz.
How can I solve this problem, should I volt up myself or is there a problem with the xmp profile, maybe asus will fix this problem in a new BIOS update or I need to manually increase the voltage. any idea?
I can verify that the system remains stable after clearing CMOS.
but I want to use my ram at 3200 mhz.

 

[Satan-IR]

no they are both the same ram so they are both using the same brand and model ram I can send you a picture of it if you want.
yes i usually get ram errors when i select 3200 mhz.

This doesn't exactly answer my question. "They are the same RAM" is not exactly the same as they came out of the same kit/pack. Did the RAM you are currently using come in a single package of two 16Gb stick?

How can I solve this problem, should I volt up myself or is there a problem with the xmp profile, maybe asus will fix this problem in a new BIOS update or I need to manually increase the voltage. any idea?

Sometimes manually tweaking the RAM variables like voltage and clock and timings helps with stability instead of running XMP or DOCP or other OCing methods. Not sure if they'd work here. Yes, maybe Asus would solve this issue as some BIOS versions are released to help with stability.

In the meantime you can disable DOCP and wait and see if there's BIOS updates or if anyone else here has experience with that particular board + CPU like you. Maybe others will have somea advice. I haven't really experimented with RAM manually on Ryzen boards recently. Ask for advice or watch relevant videos before increasing voltages too much.

 

[yyaas0]

This doesn't exactly answer my question. "They are the same RAM" is not exactly the same as they came out of the same kit/pack. Did the RAM you are currently using come in a single package of two 16Gb stick?

yes 2x16gb ram.

Sometimes manually tweaking the RAM variables like voltage and clock and timings helps with stability instead of running XMP or DOCP or other OCing methods. Not sure if they'd work here. Yes, maybe Asus would solve this issue as some BIOS versions are released to help with stability.

In the meantime you can disable DOCP and wait and see if there's BIOS updates or if anyone else here has experience with that particular board + CPU like you. Maybe others will have somea advice. I haven't really experimented with RAM manually on Ryzen boards recently. Ask for advice or watch relevant videos before increasing voltages too much.

Yes, I guess I should wait for a BIOS update. :/

 

[yyaas0]

It's not an easy way to say with certainty, Ryzen is kind of fussy with RAM, really sensitive to frequency/clock and so on. Maybe the board (with that CPU) can not run at that high clock with stability.

Does crashes BSODs happen as much or at all if you disable the RAM overclocking (DOCP)? If it runs with no problem at lower frequency it might indicate that the high RAM speed/freq. is what is causing the issues. More so because you said you have changed RAM and even if we assume the first kit/pack was faulty, getting a second faulty kit is highly unlikely.

Although you said it doens't happen when you stress test the system.


What happened in these certain days? Any repeatable patterns? Like running a certain game or a certain combination of apps?



This could also make system instability caused by RAM running at higher speed more likely.

And to make sure the two 16GB RAM sticks came as a kit/pack right? You're not by any chance mixing RAM modules from different packs?

THREAD ffffe40a6540f080  Cid 4950.4764  Teb: 00000000002b1000 Win32Thread: ffffe40a681aa1b0 RUNNING on processor a
Not impersonating
GetUlongFromAddress: unable to read from fffff80358a0be4c
Owning Process            ffffe40a69fa60c0       Image:         cpuz.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      30300    
Context Switch Count      4636          
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000001401ab650
Stack Init ffff84044fd6bc70 Current ffff84044fd688e0
Base ffff84044fd6c000 Limit ffff84044fd66000 Call 0
Priority 15 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffff8404`4fd6b598 fffff803`5823b070 : 00000000`00000162 ffffe40a`6540f080 ffff9a0b`27807f38 00000000`ffffffff : nt!KeBugCheckEx
ffff8404`4fd6b5a0 fffff803`58014f07 : 00000000`00000000 ffff8404`4fd6b6f9 ffff8404`4fd6b838 00000000`00000000 : nt!KeAbPostRelease+0x225220
ffff8404`4fd6b5e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExReleasePushLockSharedEx+0x37

This is the dump of the BSOD you said happened when you were sending message. The application it points to is CPU-Z. This also makes RAM more likely to be faulty. Or a result of mixed RAM.

Hi @Satan-IR ,
Update:
the whole problem was that it was running in CPU saver mode (the cause of the idle blue screen and many other errors). After updating the BIOS to AMD CBS > Global C-State Control Auto to Disable, I don't get any more blue screens. I don't know if turning this setting off will damage the CPU, but I hope they fix this bug in a new BIOS version. After turning this setting off, I checked the CPU temperature and it seems to be the same, only it is no longer in saving mode. this seems to have solved the problem, but I don't know if this means that the CPU is faulty.
Solved.

 

[Satan-IR]

Hi @Satan-IR ,
Update:
the whole problem was that it was running in CPU saver mode (the cause of the idle blue screen and many other errors). After updating the BIOS to AMD CBS > Global C-State Control Auto to Disable, I don't get any more blue screens. I don't know if turning this setting off will damage the CPU, but I hope they fix this bug in a new BIOS version. After turning this setting off, I checked the CPU temperature and it seems to be the same, only it is no longer in saving mode. this seems to have solved the problem, but I don't know if this means that the CPU is faulty.
Solved.

No I don't think it will damage the CPU. As long any user you doesn't do heavy OCing, increase voltages aggressively and as long as the cooling keeps CPU temperatures within safe limits there is no need to worry about damaging the CPU.

Yes, I agree. If it is a widepsread issue with th BIOS for these boards and CPUs like yours they would probably fix it soon. Look on Asus website for your board every once in a while and see if a new BIOS is released to 'increase stability' or if they explicitly mention fixing the problem with the C-States etc.

Glad you worked it out in the end and that your PC is working properly. When you make sure there's no more BSOD and you feel the problem is resolved you can contact any of the moderators to mark the thread as 'SOLVED'.

 

[yyaas0]

No I don't think it will damage the CPU. As long any user you doesn't do heavy OCing, increase voltages aggressively and as long as the cooling keeps CPU temperatures within safe limits there is no need to worry about damaging the CPU.

Yes, I agree. If it is a widepsread issue with th BIOS for these boards and CPUs like yours they would probably fix it soon. Look on Asus website for your board every once in a while and see if a new BIOS is released to 'increase stability' or if they explicitly mention fixing the problem with the C-States etc.

Glad you worked it out in the end and that your PC is working properly. When you make sure there's no more BSOD and you feel the problem is resolved you can contact any of the moderators to mark the thread as 'SOLVED'.

Update :
the problem was completely caused by the CPU and now I have changed my CPU, I no longer get blue screen or crash errors in games. thank you also for helping me solve the problem. finally solved the problem! you can close the Post as solved. @Wolfshadw