Multiple BSOD, Different Errors, Please Help

RapidFire4Life

Distinguished
May 29, 2011
10
0
18,510
0
I've been having issues with my computer for about a month now where I get several blue screens a day. First let me list my system specs...

  • CPU: Intel Core i5-3570K Ivy Bridge 3.4GHz (http://www.newegg.com/Product/Product.aspx?Item=N82E16819116504)
    MoBo: ASUS SABERTOOTH Z77 (http://www.newegg.com/Product/Product.aspx?Item=N82E16813131821)
    RAM: CORSAIR Vengeance 8GB (2 x 4GB) DDR3 1600 (PC3 12800) (http://www.newegg.com/Product/Product.aspx?Item=N82E16820233144)
    GPU: EVGA SC+ GTX 680 2GB 256-bit GDDR5 (http://www.newegg.com/Product/Product.aspx?Item=N82E16814130771)
    SSD: SAMSUNG 840 Pro Series 128GB (http://www.newegg.com/Product/Product.aspx?Item=N82E16820147192)
    HDD: SAMSUNG Spinpoint F3 500GB (http://www.newegg.com/Product/Product.aspx?Item=N82E16822152181)
    PSU: CORSAIR TX Series CMPSU-750TX 750W (http://www.newegg.com/Product/Product.aspx?Item=N82E16817139006)
So here my attempt to describe the issue, It started while using Windows 7. When I turn on my PC for the first time for the day (after its been off for 8-14 hours) It will attempt to boot up normally, get to the Windows loading screen with the logo and then it crashes with a blue screen that usually shows errors for either MEMORY MANAGEMENT or PFN LIST CORRUPT. It blue screens and attempts to reboot multiple times sometimes once or twice other times upwards of 9-10 times, eventually it will boot though. Once the machine starts it is usually fairly stable, you can even restart without any errors, however every once in a while it will blue screen when opening a web page, playing a game, or just performing any task.

What I've attempted to do to find the problem and fix it...

Testing...

  • I've run Memtest86+ Several times over night, allowing about 8 passes and a total of 10 hours, and have received absolutely no errors. I'm running it again right now its been 10 hours and made 9 passes, and I plan on letting it run all night and into tomorrow (so between 24-48 hours).

    I've also checked both hard drives. I've used Samsung Magician to check my SSD (the one the OS is installed on) and the drive reads a good. I've also used Seagate tools to run tests on my HDD. Neither of these drives show any errors.

    I've run Hot CPU Tester to check my CPU and received no error.

    I've checked my PSU in the bios and the 12V rail is reading a solid 12 Volts, and the 5V rail is holding a solid 5.0(something) Volts.

    Most interestingly i ran driver verifier and upon restarting my machine it repeatedly crashed at the password screen pointing to the Nvidia driver as the reason. I poped out my GTX 680 and put in my old GTS 250 and this allowed me to login without crashing. However later I started experiencing crashes again.
Attempts to fix...

  • I re-installed my OS replacing Windows 7 with Windows 8.1 (Because I had a copy and wanted to give it a second chance) shortly after the BSODs continued. After deciding it might be a driver issue, I tried re-installing Windows 8.1 and didn't install any driver but crashed almost immediately, leading me to believe it was hardware related.

    Unplugged my HDD in case it was conflicting with my SSD.

    Swapped the slots of my RAM.

    Flashed my BIOS to the latest version (Flashed it again later in case something went wrong the first time).

    Changed my memory settings in my BIOS to the present X.M.P.
None of this has worked, none of it has helped my determine the cause. I cant remove the CMOS battery because its hidden under the TUF armor on the MoBo, so i cant try that.

I will upload my dump files from the most recent windows install tomorrow as soon as Memtest86+ is done running. I've read them with the windows debugging tools, but I haven't been able to determine anything useful from them, so maybe someone else can.

Any suggestions and solutions are welcome, thank you for the help.
 

curioususer123

Honorable
Sep 15, 2013
174
0
10,680
0
This is really similar to my problem (http://www.tomshardware.co.uk/answers/id-1878770/major-bsod-boot-loop-repair-errors-randomly-win8-pro.html).

How often do you have these BSOD? I have the same SSD and RAM as you.
 

RapidFire4Life

Distinguished
May 29, 2011
10
0
18,510
0
I get these fairly often. Like I said after my PC has been off over night it blue screens multiple times at the first attempt to start up, but after that it is fairly stable.

The other errors you list in your post...
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (ACPI.sys)
BAD_POOL_HEADER
ATTEMPTED EXECUTE OF NO EXECUTE MEMORY
KMODE EXEPTION NOT HANDLED
MEMORY MANAGEMENT

those are all errors I have received during these blue screens as well.
 

curioususer123

Honorable
Sep 15, 2013
174
0
10,680
0


I just had another BSOD, I decided to update Gigabyte On/Off Charge and what do you know, right when it started installing - boom, KMODE EXEPTION NOT HANDLED, then a restart to SYSTEM THREAD NOT HANDLED. This driver was said to be on the bad side, so I'm uninstalling it in safe mode. http://www.eightforums.com/bsod-crashes-debugging/32038-random-bsod.html

EDIT: Mine are not that often, I started getting them today after a week or so.
 

curioususer123

Honorable
Sep 15, 2013
174
0
10,680
0
Not sure if you still need help, but one of my RAM modules ended up being faulty - I ran that memtest86 in the end (I always denied my RAM could be the cause beforehand!). I will be getting it RMA.
 

RapidFire4Life

Distinguished
May 29, 2011
10
0
18,510
0
I honestly can't tell, I really don't think its my RAM. I just stopped memtest86+ after a 34 hour run where it made 30 passes with 0 errors. I just don't see how it could be unless its a fault that's just not being picked up by memtest.

I have had a couple more crashes since then so i will upload the dump files, but here't the WinDbg x64 from the most recent one.

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041793, The subtype of the bugcheck.
Arg2: fffff68067393688
Arg3: 0000000000000004
Arg4: 0000000000000003

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


BUGCHECK_STR: 0x1a_41793

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: rundll32.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff8031e59220a to fffff8031e568ca0

STACK_TEXT:
ffffd000`211a2688 fffff803`1e59220a : 00000000`0000001a 00000000`00041793 fffff680`67393688 00000000`00000004 : nt!KeBugCheckEx
ffffd000`211a2690 fffff803`1e484fdd : 00000000`00000001 00000000`00000000 00000000`00000000 ffffe000`012aaa28 : nt! ?? ::FNODOBFM::`string'+0x1907a
ffffd000`211a28f0 fffff803`1e7f0071 : ffffe000`01bbf660 00000000`00000000 ffffe000`00000000 ffffe000`00000000 : nt!MiDeleteVad+0x22d
ffffd000`211a29e0 fffff803`1e7ef987 : fffff6fb`40339c00 fffff680`00000008 000000ce`718a0000 00000000`00000901 : nt!MiUnmapViewOfSection+0xf9
ffffd000`211a2ab0 fffff803`1e5744b3 : ffffe000`00e1d080 00000000`00008001 00000000`00000001 ffffe000`012aa540 : nt!NtUnmapViewOfSectionEx+0x73
ffffd000`211a2b00 00007ff8`401c681a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000ce`6f7ace88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`401c681a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+1907a
fffff803`1e59220a cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1907a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 52341cf4

IMAGE_VERSION: 6.3.9600.16404

BUCKET_ID_FUNC_OFFSET: 1907a

FAILURE_BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_

BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1a_41793_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH: {2bb49b32-09fa-a96d-8b93-292cf7a50b3f}

Followup: MachineOwner
---------
 

Similar threads


ASK THE COMMUNITY