New Build BSOD Issues

Hypersphere

Honorable
Jun 30, 2013
7
0
10,510
I recently built my first PC and about a week ago and ever since I began running it I have been getting several different Blue Screens.

Here are my specs:
CPU: i5-4670k
Video: GeForce GTX 770
Mobo: GIGABYTE Z87X-UD3H
RAM: 16GB Crucial Ballistix Sport 4GBx4
Seagate Barracuda 1TB HDD
Samsung 120GB SSD
Power: Corsair Gold AX850W
OS: Windows 7 Professional 64

I was getting everything set up when I began to see several different BSOD's happening. Some were IRQL_NOT_LESS_OR_EQUAL, IRQL_GT_ZERO_AT_SYSTEM_SERVICE, KMODE_EXCEPTION_NOT_HANDLED, BAD_POOL_CALLER, SYSTEM_SERVICE_EXCEPTION, AND PAGE_FAULT_IN_NONPAGED_AREA.

I ran WhoCrashed for several of them and fixed the drivers that it had identified but the problem still persisted, and keeps identifying ntoskrnl.exe as what probably caused the crash for most others. Most of my week has been spent troubleshooting for all of these issues in any way that I could and I seem to have exhausted most of my options and I'm now at a loss because the only troubleshooting left that I could do requires computer skills that are unfortunately beyond mine.

Something that I did notice though throughout these crashes was that all of them seemed to somehow relate to memory and system interactions. I looked that up and ran memtest for all four of my RAM sticks individually for three passes and it detected no errors so I am not convinced that it is a hardware issue.

I also ran the sfw /scannow command on an elevated command prompt and the most intriguing thing I've found in all of this was that the scan reported that some files were corrupted but it was unable to fix them, in the log I found these lines:

Info CSI 000001c5 [SR] Could not reproject corrupted file [ml:520{260},l:102{51}]"\??\C:\Windows\Microsoft.NET\Framework64\v2.0.50727"\[l:46{23}]"System.Transactions.dll"; source file in store is also corrupted

Info CSI 000002d2 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:30{15}]"NlsData0024.dll"; source file in store is also corrupted

These along with several others that looked very similar to it but I won't copy them all because I am unsure if they mean anything, though I can if necessary. I've tried several new installs of Windows with no different results.

The main problem that I am facing with all of this is that I am getting a lot of information and I do not have the expertise to really understand what it means or whether or not it is relevant. I can only deduce so far with my level of knowledge and the only thing that I can determine is that I might have a corrupt copy of Windows or there is a issue pertaining to memory that might originate in another area that I have not identified yet. It also seems to occur when I am using the internet in some form such as downloading things or just being in Firefox. I've let it idle for up to ten hours with no problems and ran BF3 single player for 5 hours with no issue, but I usually do not make it any longer than 4-6 hours when using the internet in some form.

I've run out of options and short of ordering a new OS or replacing parts I am no longer sure what to do.

Here are some of the Whocrashed notes:

This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4A (0x74EE2E09, 0x2, 0x0, 0xFFFFF8800B397B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFD8000FBE9008, 0x0, 0xFFFFF800030D4C26, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033C6261, 0xFFFFF8800C8BE020, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003081A0F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF800034C5E7E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

I apologize for the length but I am just unsure what is relevant information for this issue.
 
Solution
are you sure the memory you got is compatible with your motherboard... I found my self in the same pickle a few builds back.... come to find out the manufacturer had changed the model numbers and the company I ordered it from didnt take the time to look at the new model numbers.... I had to RMA the memory kit for a different one. I learned that I must always double check everything before ordering what I need or want.

Rahbot

Distinguished
Dec 12, 2008
231
0
18,710
are you sure the memory you got is compatible with your motherboard... I found my self in the same pickle a few builds back.... come to find out the manufacturer had changed the model numbers and the company I ordered it from didnt take the time to look at the new model numbers.... I had to RMA the memory kit for a different one. I learned that I must always double check everything before ordering what I need or want.
 
Solution

Hypersphere

Honorable
Jun 30, 2013
7
0
10,510


I'm fairly certain that it is compatible but I'm not sure how exactly to verify that it is. The manufacturer's site claims that it can support DDR3 1600 modules which is what mine are. Like I said though, I am not quite sure if that's what compatibility for it means.



I have not seen any LED errors. And I reinstalled the mobo disk drivers every for each time that I reinstalled Windows and updated those. My RAM speed says 1600.

Edit: I just got a new error line for a BSOD: PFN_LIST_CORRUPTED
Bugcheck code: 0x4E (0x99, 0x1A3576, 0x2, 0x1A3461)
 


Hmmm, 0x4E: PFN_LIST_CORRUPT is probably the single strongest error code to indicate corrupted memory and with your symptoms of randomness it would indicate all the more so.
 

satrow

Distinguished
Feb 18, 2013
128
5
18,715
Sounds like a bad driver.
WinDbg Output Example:
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 0008dd83, page frame number
Arg3: 00000002, current page state
Arg4: 0008de02, 0
Copy the minidumps to your Desktop then zip them, Upload the zip to somewhere publicly accessible like Skydrive.
 

Hypersphere

Honorable
Jun 30, 2013
7
0
10,510


Here's all of the minidumps I have from my current install of windows. The ones identified as driver_irql_not_less_or_equal I have addressed already.

Link
 

satrow

Distinguished
Feb 18, 2013
128
5
18,715
There's one potentially bad driver, AppleCharger.sys, the GIGABYTE On/Off Charge driver, maybe it's conflicting with UsbCharger.sys, (http://systemexplorer.net/file-database/file/usbcharger-sys/6381721 ?).

AppleCharger.sys has a previous history of being implicated in, or causing, BSODs: AppleCharger.sys Tue Feb 19 04:17:09 2013 (5122FCC5)
GIGABYTE On/Off Charge driver. See here for details - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
http://www.carrona.org/drivers/driver.php?id=AppleCharger.sys

If uninstalling one or other of the above drivers doesn't fix it (or both, if you've no need for charging over USB), please run Driver Verifier, carefully read and follow the notes here: http://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-blue-screen-death-related.html Once you have triggered 2-3 crashes with DV enabled, upload the new *.dmp files for further analysis.

List of likely causes for your BSOD types, from http://carrona.org/bsodindx.html :
0x1E, Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

0x50, Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

0x4E, Usual causes: Device driver, ?memory

0xD1, Usual causes: Device driver

0x4A, Usual causes: Device driver

0x3B, Usual causes: System service, Device driver, graphics driver, ?memory

0xA (already addressed), Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
 

Hypersphere

Honorable
Jun 30, 2013
7
0
10,510
Alright I have removed the potentially offending GIGABYTE On/Off driver and have so far run for a few hours with no issues, but it usually takes a while for any problems to arise so I will run everything normally as I usually would for a day or two and if I receive any more problems I will run the Driver Verifier and report back with the new minidump files.
 

Hypersphere

Honorable
Jun 30, 2013
7
0
10,510
Well nothing seems to have changed and quite frankly seems to be getting worse now regarding the Blue Screens, but I don't consider that a bad thing because these are much more definitive. I have received a few more BSOD's, some with and without the verifier enabled, and the most telling one that was new a few days ago was the error MEMORY_MANAGEMENT. I've had several ideas for what might be the problem and faulty hardware is still one. If I have to I might just go through in replacing most of what I used in putting this build together as it's wearing me down quite a bit in trying to piece the central issue together. Still though, here is a link to the new minidumps, aptly named minidumps_new.

Link
 

TenPc

Honorable
Jul 11, 2012
2,471
1
11,960

Hypersphere

Honorable
Jun 30, 2013
7
0
10,510
Sorry, I forgot to respond to this thread to say that I have fixed my problem. I replaced my RAM with a set of 2x8GB Corsairs and went through and tried a few more troubleshooting and ever since have been running it with no issues detected for about a week and a half now. I am grateful for the assistance though and am sure some of the things mentioned were also causing issues considering the variety of error messages I was receiving.
 

TenPc

Honorable
Jul 11, 2012
2,471
1
11,960


So, in effect, my previous reply about the ram was correct, the ram was the issue so my reply should be selected as BEST ANSWER :)