• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

new build ran fine now crashes bsod

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

gtochad

Registered
Joined
Aug 23, 2012
im more wondering on how i can self troubleshoot the problem although im not sure what i need to read the files in the "Files that help describe the problem:" section of the windows has shut down unexpectedly window that come up when it restarts.

ive ran windows memory test and memtest86 but nothings been found in that

it crashes maybe once or twice a day
 
Is the system overclocked?

Have you done in monitoring of core temps and CPU socket temps? (Try HWMonitor).

Does it crash under heavy use or at idle?

Please tell us some details about your hardware:

Make and model of CPU?

Make and model of motherboard?

Make and model of CPU cooler or is it the stock one that came boxed with the CPU?

Make and model of case?

Make and wattage of PSU?

Make and model of video card?

Make, amount and speed of ram?
 
Is the system overclocked? NO

Have you done in monitoring of core temps and CPU socket temps? just used asrocks tuning utility monitor stays under 55C at load 35c at idle, gpu seems withing range as well

Does it crash under heavy use or at idle? seems to not matter crashes with games and sometimes while just on the internet

Please tell us some details about your hardware:

Make and model of CPU? intel 3770k

Make and model of motherboard? asrock z77 extreem 4

Make and model of CPU cooler or is it the stock one that came boxed with the CPU? thermalright true spirit 140

Make and model of case? antec 900 v2

Make and wattage of PSU? corsair 650watts

Make and model of video card? galaxy 670 gtx 4gb

Make, amount and speed of ram? corsair vengance 8x2 16gb

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000000411
BCP2: FFFFF68000072018
BCP3: C5B00002929AC886
BCP4: FFFFF680000A6519
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
 
Last edited:
Post the *.dmp file from the %systemroot%\minidump folder, or the corresponding critical info from the Event Viewer log. Which OS are you running including any SP installed, and how long did you let both the built-in Windows Memory Diagnostic tool and Memtest86+ run for?
 
Your link has a PW or something. Please provide this info as redduc needs:

"
Post the *.dmp file from the %systemroot%\minidump folder, or the corresponding critical info from the Event Viewer log. Which OS are you running including any SP installed, and how long did you let both the built-in Windows Memory Diagnostic tool and Memtest86+ run for?"
 
figured out how to read dmp files. im not sure where else to upload files too but heres what it said and i have windows 7 sp1 and i ran those tests for approx 3 hours and may run them again

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80083b3f80, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80083b3f80
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: dllhost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002ef9b50 to fffff80002e8dfc0

STACK_TEXT:
fffff880`0a1a96e8 fffff800`02ef9b50 : 00000000`0000001a 00000000`00041790 fffffa80`083b3f80 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0a1a96f0 fffff800`02ec0b69 : 00000000`00000000 00000000`764fffff fffffa80`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x35054
fffff880`0a1a98b0 fffff800`031a0e21 : fffffa80`12b7dcb0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0a1a99d0 fffff800`031a1223 : 0000007f`00000000 00000000`763f0000 fffffa80`00000001 fffffa80`1017a010 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0a1a9a90 fffff800`02e8d253 : 00000000`00000000 00000000`764b2698 fffffa80`1278a0e0 00000000`764b12d4 : nt!NtUnmapViewOfSection+0x5f
fffff880`0a1a9ae0 00000000`770c15ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ae328 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770c15ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+35054
fffff800`02ef9b50 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+35054

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

Followup: MachineOwner
---------
 
the only thing that i think i could have done is i changed the temp folders from my c drive (ssd) to my d drive (hdd) but than a few weeks later i noticed this crashing and so i changed it back. and again it doesnt seem to be from any load on the system
 
Back