Windows – How to identify the faulty driver if the computer working good in safe mode

bsodcrashsafe-modewindows 7

I had 64bit windows 10 computer, it then suddenly started BSOD. I tried everything in the internet but nothing solves the problem, so I just reformatted the pc and go back to windows 7. Everything went well, until I installed web browser. Everytime I open a web browser, again it turns BSOD again collecting crash dump. It works perfectly fine in safe mode. So I tried to change the RAM. It then again went very well. Everythings working fine. I was able to surf the net install and download applications. So I thought everything's is fine already until the next day, everytime I open any application that uses internet, it again went to BSOD collecting crash dump.

Are there any explanation what might causes this BSOD?

—UPDATE—-

I tried the whocrashed software and based on the dump file, it might be driver issue.

enter image description here

Is there a way to locate which driver is causing a problem?Because I was able to surf in safe mode with networking.

This is the dump files.

—Update prt 2—

So, as per suggestion this might be hardware issue so I tried other hard drive and same thing happens, but this time, BSOD happens when logging in.

What's wrong with this computer????

Best Answer

You don't have a driver issue. Your CPU (L2 Cache - GCACHEL2_ERR_ERR) is damaged:

1: kd> !errrec fffffa80043c3028
===============================================================================
Common Platform Error Record @ fffffa80043c3028
-------------------------------------------------------------------------------
Record Id     : 01d2a3a2169ca603
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/23/2017 6:56:23 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80043c30a8
Section       @ fffffa80043c3180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000001

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80043c30f0
Section       @ fffffa80043c3240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000001
CPU Id        : a9 06 03 00 00 08 10 01 - bf e3 9a 3d ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80043c3240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80043c3138
Section       @ fffffa80043c32c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : GCACHEL2_ERR_ERR (Proc 1 Bank 5)
  Status      : 0xbe2000000005110a
  Address     : 0x0000000025ac4280
  Misc.       : 0x0000031084000086

Windbg only shows generic Cache error, so we can't see in detail what it wrong. Replace the CPU with a new one.

Related Question