Solved random BSODs with new build - error related to "ntoskrnl.exe+7cc40"?

[blenky]

random BSODs with new build - error related to "ntoskrnl.exe+7cc40"?

Hi

A few days ago I did a new hardware build and installed W7 64 ultimate. I included a Corsair SSD as my boot drive for the speed advantage.



I have done some investigation and tried to track down the cause of the BSOD but to no avail. Currently they are happening once\ twice or more a day but very erratic so have no confidence in the system at the moment.

I have uploaded dumps of recent crashes in the hope someone here can help.

Anything would be appreciated. Thanks.

 

[yowanvista]

Run a RAM test http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Stop any Overclocking if any.

Remove any Avast software, use MSE instead.
Uninstall Asus PC Probe, Smart Doctor, Asus update or any other Asus utilities.

Are you using any old(pre-Vista) software that might not be 64-bit compatible?

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89c614680, Reserved
Arg2: b3b7465eeede15d6, Reserved
Arg3: fffff80001dfe036, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80001cd0c40

STACK_TEXT:  
fffff880`021c45d8 00000000`00000000 : 00000000`00000109 a3a039d8`9c614680 b3b7465e`eede15d6 fffff800`01dfe036 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80001dfe44d - nt!ExDeferredFreePool+9ed
    [ 40:00 ]
1 error : !nt (fffff80001dfe44d)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

 

[blenky]

OK followed your advice as follows

• Did the RAM test separately on each 4GB module. No errors found.
• Removed AVAST and now running MSE
• Removed all the ASUS software.
• No over clocking the BIOS, RAM and video card have always been set on defaults.
• I'm not aware of any running any pre Vista software. Some of the BSODs happen when the PC is idle.

Still getting BSODs - see attachment. The error messages seem random so not sure what to try next!

 

[yowanvista]

OK followed your advice as follows

• Did the RAM test separately on each 4GB module. No errors found.
• Removed AVAST and now running MSE
• Removed all the ASUS software.
• No over clocking the BIOS, RAM and video card have always been set on defaults.
• I'm not aware of any running any pre Vista software. Some of the BSODs happen when the PC is idle.

Still getting BSODs - see attachment. The error messages seem random so not sure what to try next!

Same Bugcheck, critical kernel code was corrupted, this could be as a result of malware or system corruption
Run a scan of Malawarebytes

Use SFC to fix any corrupt system files
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Post back with your results.

 

[blenky]

Same Bugcheck, critical kernel code was corrupted, this could be as a result of malware or system corruption
Run a scan of Malawarebytes

Use SFC to fix any corrupt system files
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Post back with your results.

Thanks for your suggestions - really appreciate the help

Ran Malawarebytes - clean

Tried three time to run SFC. The first two times got a BSOD. Third time lucky. It completed and told me it had found some errors and could not fix them all. Said to refer to the log file 'CBS.log' which I have attached. Does that throw any light?

Would a re-install of W7 help?

Cheers

 

[yowanvista]

Same Bugcheck, critical kernel code was corrupted, this could be as a result of malware or system corruption
Run a scan of Malawarebytes

Use SFC to fix any corrupt system files
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Post back with your results.

Thanks for your suggestions - really appreciate the help

Ran Malawarebytes - clean

Tried three time to run SFC. The first two times got a BSOD. Third time lucky. It completed and told me it had found some errors and could not fix them all. Said to refer to the log file 'CBS.log' which I have attached. Does that throw any light?

Would a re-install of W7 help?

Cheers

Seems some kind of system corruption is the cause. I would recommend a http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[blenky]

Same Bugcheck, critical kernel code was corrupted, this could be as a result of malware or system corruption
Run a scan of Malawarebytes

Use SFC to fix any corrupt system files
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Post back with your results.

Thanks for your suggestions - really appreciate the help

Ran Malawarebytes - clean

Tried three time to run SFC. The first two times got a BSOD. Third time lucky. It completed and told me it had found some errors and could not fix them all. Said to refer to the log file 'CBS.log' which I have attached. Does that throw any light?

Would a re-install of W7 help?

Cheers

Seems some kind of system corruption is the cause. I would recommend a http://www.sevenforums.com/tutorials/3413-repair-install.html

Thanks. I tried the repair linked but kept getting a BSOD part way through! Therefore I did a fresh install of W7 formatting my SSD as part of the install.

I was having a problem trying to update the firmware on my SSD - I couldn't get this to work while it was the boot drive. So I did another W7 install on a HDD and booted to that with the SSD connected. That way I managed to sucessfully upgrade the firmware. I was hoping this might help

I swapped the SSD back to the boot drive but I'm still getting BSOD's - but not as frequent. I repeated some of the earlier tests - SCANNOW found no issues. I ran 'verifier' and this BSOD'd and reported a Deamon Tools file as the cause. So I have removed Daemon Tools.

All drivers are up to date.

I do have strange problem with my DVD ROM which maybe unrelated. It no longer reads DVDs\CDs but appears OK in Device Manager! That means that currently I am unable to boot from any disk. I attach the latest dump files since I re installed W7.

I just can't seem to find any real pattern. Again any insight would be graetfully received.

 

[yowanvista]

Thanks for your suggestions - really appreciate the help

Ran Malawarebytes - clean

Tried three time to run SFC. The first two times got a BSOD. Third time lucky. It completed and told me it had found some errors and could not fix them all. Said to refer to the log file 'CBS.log' which I have attached. Does that throw any light?

Would a re-install of W7 help?

Cheers

Seems some kind of system corruption is the cause. I would recommend a http://www.sevenforums.com/tutorials/3413-repair-install.html

Thanks. I tried the repair linked but kept getting a BSOD part way through! Therefore I did a fresh install of W7 formatting my SSD as part of the install.

I was having a problem trying to update the firmware on my SSD - I couldn't get this to work while it was the boot drive. So I did another W7 install on a HDD and booted to that with the SSD connected. That way I managed to sucessfully upgrade the firmware. I was hoping this might help

I swapped the SSD back to the boot drive but I'm still getting BSOD's - but not as frequent. I repeated some of the earlier tests - SCANNOW found no issues. I ran 'verifier' and this BSOD'd and reported a Deamon Tools file as the cause. So I have removed Daemon Tools.

All drivers are up to date.

I do have strange problem with my DVD ROM which maybe unrelated. It no longer reads DVDs\CDs but appears OK in Device Manager! That means that currently I am unable to boot from any disk. I attach the latest dump files since I re installed W7.

I just can't seem to find any real pattern. Again any insight would be graetfully received.

Your SSD seems to be having some hardware defects or a firmware issue, i would recommend to get it replaced.
As for your DVD-Drive problem a firmware upgrade might help.

 

[RhapsodyOfFire]

I would recommend harddisk drive test for bad sectors lide Hdat or HddRegenerator and the vendor diagnostic test.

 

[blenky]

Still working on this!

Updated BIOS and checked everything installed on MB OK.

BSODs have reduced but still happening.

I'm running Prime95 using the Blend tests. After 3.5 hours one of the 'workers' errored with the following

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

Any idea what this indicates?

Thanks

 

[yowanvista]

Still working on this!

Updated BIOS and checked everything installed on MB OK.

BSODs have reduced but still happening.

I'm running Prime95 using the Blend tests. After 3.5 hours one of the 'workers' errored with the following

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

Any idea what this indicates?

Thanks

This means that a hardware fault was detected in your CPU, you should replace it.

 

[blenky]

Happy New Year!

My quest goes on. I don't think its the CPU but I suspect the memory. Could someone please take a look at the last three mini dump files and performance analysis I have attached and see if they throw any more light on this really frustrating situation!

Thanks again for all your valued contributions.

 

[RhapsodyOfFire]

Solved: Prime 95: FATAL ERROR: Rounding was 0.5, expected less than 0.4 - PC Help Forum
It was a MB case with the same issue. It is better to have a second test like MemTest86 for several hours and try swapping memory sticks or removing some of them. Check the voltages too.
Prime95 FATAL ERROR Rounding Question
this thread is very interesting too. Maybe you need to increase the vcore voltage (cpu voltage).

 

[blenky]

Solved: Prime 95: FATAL ERROR: Rounding was 0.5, expected less than 0.4 - PC Help Forum
It was a MB case with the same issue. It is better to have a second test like MemTest86 for several hours and try swapping memory sticks or removing some of them. Check the voltages too.
Prime95 FATAL ERROR Rounding Question
this thread is very interesting too. Maybe you need to increase the vcore voltage (cpu voltage).

Thanks for that. Interestingly the second issue was a bad motherboard. As I'm not o/c on a frsh install I'm sure it's got to be RAM, CPU or m/b. Just not sure which due to most tests passing OK such as memtest.

As I can't test m/b by using other components (all my old components are not comaptable with new board) I'm going to RMA the RAM as a starter to see if that helps! If not I'll return\replace the m/b. Hopefully I'll get lucky

 

[blenky]

Replaced the RAM and the system is now running sweet as a nut!

Thanks for all the advice.