Solved BSODs with multiple error codes on fresh install

[Tdongo]

I’m having some BSOD issues. I assembled this PC for a friend based on the Tom’s Hardware 500$ Gaming PC from Q4 2012. The only piece of hardware that was different was the optical drive. System Builder Marathon, Q4 2012: $500 Gaming PC : Squeezing More Bang From The Same Buck

Specs:
CPU: Intel Pentium G850 (Sandy Bridge)
Motherboard: ASRock H77 Pro4/MVP: LGA 1155, Intel H77 Express
RAM: G.Skill Value Series 8 GB (2 x 4 GB) DDR3-1333 F3-10600CL9D-8GBNT
Graphics: PowerColor AX7850 1GBD5-DH: Radeon HD 7850 1 GB
Hard Drive: Western Digital WD3200AAKX: 320 GB, 7200 RPM SATA 6Gb/s Hard Drive
Power Supply: Antec VP-450 450W
Optical Drive: LITE-ON IHAS124-04

After a few weeks she started getting a lot of BSODs, so I took it back and did a fresh install of Win 7 and updated all the drivers. The machine continues to get a lot of BSODs (with varying error codes) and I've been unable to figure out exactly what I can do to cause them (I got one while writing this post), but they typically happen when it’s idle or at low load. At one point I had enabled driver verifier and could force the system to freeze-up (with video corruption), but couldn't get a BSOD with a minidump.

I've scanned through the forums and have tried many of the troubleshooting methods that are listed, but I am happy to start at square-one to figure out the cause of this. I've enclosed a zip file from the diag tool to get started. I’m sure there is something I overlooked and would appreciate any assistance.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 4A[/COLOR], {73532e09, [COLOR="Blue"]2[/COLOR], 0, fffff880080f3c60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

Usual causes:  Device driver

This bugcheck indicates that a driver was returning from a system function call to user mode, when the IRQL level was higher than PASSIVE_LEVEL, as we can see from the parameters the current IRQL level was 2.

0: kd> [COLOR="SeaGreen"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`05a6f000 fffff880`065e2000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="Red"]Fri Mar 29 02:27:04 2013[/COLOR] (5154FBF8)
    CheckSum:         00B25604
    ImageSize:        00B73000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update to the latest WHQL driver available here - http://www.sevenforums.com/graphic-cards/1810-latest-amd-catalyst-video-driver-windows-7-a.html

WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104

1. Download Driver
2. Start rb: Type: Device Manager
3. Expand Display Adapters
4. Right-Click Driver Name, Uninstall
5. Reboot
6. Run Driver Sweeper
7. Reboot
8. Install Downloaded Driver

Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

 

[Tdongo]

I followed the instructions above and while the driver date in device manager still shows 3/28/13 the Driver version matches up with the latest WHQL release. Should I install the beta drivers?

I also received a few more BSODs in the meantime and I've uploaded another zip.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 19[/COLOR], {22, de00000000000000, 0, 0}

GetPointerFromAddress: unable to read from fffff80003313100
GetUlongFromAddress: unable to read from fffff800033131c0
GetUlongFromAddress: unable to read from fffff80003281a38
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72e6 )

Usual causes:  Device driver

The bugcheck indicates that a pool header is corrupt, this indicates there is a problem with the Windows memory allocation, drivers are the most the common cause for this bugcheck, however, RAM and hard-drive corruption can also be contributing problems.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[Tdongo]

Memtest - I tested both sticks of RAM individually in each of the slots they're in and didn't get any errors.

HDD - The Western Digital Lifeguard Diagnostic passed. I got another BSOD shortly after completing that diagnostic.

Chkdsk - No file system errors or bad sectors

CrystalDiskInfo - Included Screenshot

The latest BSOD I received was during a full malwarebytes scan, so I'm going to see if I can replicate that again. I've included another diag zip.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff80003173d37, fffff88007374c50, 0}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+317 )

Usual causes:  System service, Device driver, graphics driver, memory

There's seems to be many graphics driver and graphics card related routines within the raw call stack, the drivers are being blamed, however, this could suggest a faulty graphics card.

• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

   Warning

Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components.

Use GPU-z to monitor your GPU temperature, remember, to use the Log to File option seen in the screenshot (see download link website).

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[Tdongo]

After about 20 minutes into the Furmark test, I got a BSOD. I attached another zip. The GPU temp was holding steady at around 69C and the framerate was around 11 with a max of 15. Should I go ahead and enable driver verifier?

 

[Tdongo]

After enabling Driver Verifier, Windows would freeze at the welcome screen (with a lot of video corruption) every time I booted into windows. I booted into safe mode and turned off DV.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1E[/COLOR], {[COLOR="SeaGreen"]ffffffffc0000005[/COLOR], fffff800030b5d79, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiCheckForConflictingVadExistence+1d )

Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

What do you mean by video corruption? The screen going funny and distorted?

0: kd> [COLOR="SeaGreen"]!sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=1524]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = [COLOR="red"]P1.50[/COLOR]
BiosReleaseDate = [COLOR="red"]12/06/2012[/COLOR]
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
SystemFamily = To Be Filled By O.E.M.
SystemVersion = To Be Filled By O.E.M.
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = [COLOR="red"]ASRock[/COLOR]
BaseBoardProduct = [COLOR="red"]H77 Pro4/MVP[/COLOR]
BaseBoardVersion =

There most likely seems to be graphics related issue so far, either the drivers or the card itself, have you checked for a BIOS update? Many BIOS version updates will contain greater hardware stability and compatibility.

Do you have a onboard graphics card or a spare graphics card to switch to?

 

[Tdongo]

I have updated the BIOS to the most recent version (1.50). There is onboard video (which I currently have disabled). I could try removing the AMD card and use that for a while. I also have a spare Nvidia card kicking around somewhere as well.

Should I just use it normally for a while to see if the issue persists?

Thanks so much for all your help on this so far. I really appreciate it.

 

[x BlueRobot]

Welcome, and use your computer you normally would, and then switch to a different graphics card if any problems arise.

 

[Tdongo]

After removing the video card I got two more BSODs. So I went ahead and removed all of the AMD drivers using Driver Sweeper. I enclosed the minidumps in case they are helpful.

 

[x BlueRobot]

[COLOR="red"]BugCheck 1000007E[/COLOR], {ffffffffc0000005, fffff8000317ea5c, fffff8800337f818, fffff8800337f070}

Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

CONTEXT:  fffff8800337f070 -- ([COLOR="SeaGreen"].cxr 0xfffff8800337f070[/COLOR])
[COLOR="red"]rax[/COLOR]=[COLOR="red"][B]7[/B][/COLOR]cfffa800992e738 rbx=000000000020a404 rcx=00000000000000f0
[COLOR="red"]rdx[/COLOR]=[COLOR="red"][B]fffff[/B][/COLOR]8a007939258 rsi=fffffa8006b71968 rdi=0000000000000400
rip=fffff8000317ea5c rsp=fffff8800337fa50 rbp=0000000000000000
 r8=fffffa800b1e0004  r9=fffffa8006b71048 r10=fffffa800992d0d0
r11=fffffa800982b7a0 r12=0000000000000000 r13=fffffa8006b71000
r14=fffff8a007942060 r15=000000000000001e
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!MiEmptyPageAccessLog+0xdc:
fffff800`0317ea5c 488b08          mov     rcx,qword ptr [rax] ds:002b:7cfffa80`0992e738=????????????????

0: kd> [COLOR="seagreen"].formats 7cfffa800992e738[/COLOR]
Evaluate expression:
  Hex:     7cfffa80`0992e738
  Decimal: 9007193207587661624
  Octal:   0763777650001144563470
  Binary:  [COLOR="Red"][B]0[/B][/COLOR]1111100 11111111 11111010 10000000 00001001 10010010 11100111 00111000
  Chars:   |......8
  Time:    Fri Aug 30 04:19:18.766 30143 (UTC + 1:00)
  Float:   low 3.53657e-033 high 1.06329e+037
  Double:  1.27648e+294
0: kd> [COLOR="SeaGreen"].formats fffff8a007939258[/COLOR]
Evaluate expression:
  Hex:     fffff8a0`07939258
  Decimal: -8108771143080
  Octal:   1777777612000744711130
  Binary:  [COLOR="red"][B]1111[/B][/COLOR]1111 11111111 11111000 10100000 00000111 10010011 10010010 01011000
  Chars:   .......X
  Time:    ***** Invalid FILETIME
  Float:   low 2.22041e-034 high -1.#QNAN
  Double:  -1.#QNAN

FAULTING_IP: 
[COLOR="red"]nt!MiEmptyPageAccessLog+dc[/COLOR]
fffff800`0317ea5c 488b08          mov     rcx,qword ptr [COLOR="Red"][rax][/COLOR]

I think there may be a possibility of a flipped bit, in one of the CPU registers, the register with the flipped bit also seems to be the register in which the crash occurred. Your Intel onboard graphics card is also being blamed, this makes sense, since I'm sure that the Intel graphics are integrated with the CPU.

0: kd> [COLOR="SeaGreen"]lmvm igdkmd64[/COLOR]
start             end                 module name
fffff880`04aa5000 fffff880`04fc11c0   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        [COLOR="Red"]Sat Mar 09 02:10:00 2013[/COLOR] (513A99F8)
    CheckSum:         0052A265
    ImageSize:        0051C1C0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Run this stress test (CPU) - http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

 

[Tdongo]

The first two times I ran the standard test it would BSOD, and it passed on the third. It passed the test on high on the 2nd try. But it BSODs each time on the very high test. The temps were under 55C each time. I've attached the minidumps if they're helpful.

This is the first thing I've been able to do that will force a BSOD every time. Does this conclusively point to the CPU or the MoBo socket? Anything else I can do to narrow it down?

 

[x BlueRobot]

The NTSTATUS error is consistent throughout all the crashes:

[COLOR="SeaGreen"]0xc0000005[/COLOR] - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

memory_corruption also seems to be a common factor, and can relate to the CPU caches and registers.

We can check the CPU again with a different stress test, to see if we get the same results:

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Enable "Round off checking" before the test (see first post below tutorial).

 

[Tdongo]

I ran three tests with Prime95 and each time I got a BSOD before the two hour mark (though the last time got real close to two hours). I've enclosed the minidumps.

I poked around online and a lot of folks seem to think reseating the CPU might help. Do you think that should be my next course of action?

 

[x BlueRobot]

You could try reseating the CPU, and see if it makes any difference, and I'll look at the dumps now. It does seem to pointing to a CPU fault if it constantly crashes on CPU tests.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 7F[/COLOR], {[COLOR="Blue"]8[/COLOR], 80050033, 406f8, fffff800030cee2f}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

The bugcheck indicates the CPU generated a trap (type of interrupt), which the kernel wasn't able to catch and process. More specifically, the first parameter contains the value of 8 which indicates that a Double Fault occurred this happens, when the the CPU was processing a earlier fault (General Protection Fault) and failed to copy the contents of the fault into the registers.

The most common cause for this BSOD is a hardware problem, furthermore, the other two BSODs indicated your Intel graphics driver as a potential cause, which I'm sure resides as your onboard graphics card on your Intel processor.

 

[Tdongo]

After reseating the CPU, the temps are still good, but now I'm getting a BSOD about every 45 minutes. It was initially pretty stable, so I reinstalled the video card and uninstalled the onboard graphics, but after several hours I started getting a pretty steady stream of BSODs. I've attached the minidumps.

I'm leaning towards the MoBo as the faulty part in the chain, but I'm not sure. I guess I could RMA the Motherboard first and see if the problem persists.

 

[x BlueRobot]

[COLOR="red"]BugCheck 1E[/COLOR], {[COLOR="Blue"]ffffffffc0000005[/COLOR], fffff88003120ad0, 0, 0}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : [COLOR="Red"]Rt64win7.sys [/COLOR]( Rt64win7+1a7d0 )

Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

1: kd> [COLOR="SeaGreen"]lmvm Rt64win7[/COLOR]
start             end                 module name
fffff880`05c1d000 fffff880`05cec000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR="Red"]Mon Mar 04 07:25:55 2013[/COLOR] (51344C83)
    CheckSum:         000D1FB8
    ImageSize:        000CF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Realtek network adapter seems to be causing problems, however, the driver seems to be most probably the most update version, therefore it may well be a bad motherboard.

1: kd> [COLOR="SeaGreen"]lmvm atikmpag[/COLOR]
start             end                 module name
fffff880`04730000 fffff880`047c4000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        [COLOR="Red"]Fri Mar 29 01:09:45 2013[/COLOR] (5154E9D9)
    CheckSum:         00091A60
    ImageSize:        00094000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your graphics card driver was also blamed for the issue, I've noticed that it will blame any device which is not disabled and connected to the motherboard.