Need Help With BSOD

Operating Systems & Open Source Windows
1

I just finished building a new PC and it is has a few bugs, that im not sure where they are coming from. All the drivers should be up to date. its onlty given me a problem signature a few times upon reboot

mini dump: https://www.dropbox.com/sh/4utd9bjrbpxpw6b/FmFtuF9_GK

 

 

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    3b
  BCP1:    00000000C0000005
  BCP2:    FFFFF800031FA509
  BCP3:    FFFFF8800B912DF0
  BCP4:    0000000000000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\110312-15272-01.dmp
  C:\Users\Dakota Reese\AppData\Local\Temp\WER-14103020-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt



Workload work failed with error message: Process exited unexpectedly


Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    1a
  BCP1:    0000000000005003
  BCP2:    FFFFF70001080000
  BCP3:    00000000000002FF
  BCP4:    00000301040005FE
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\110412-9578-01.dmp
  C:\Users\Dakota Reese\AppData\Local\Temp\WER-15834-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


CPU: 3570k
GPU: MSI 660ti
RAM: 8GB G.skill ares DDR3x2
PSU: COOLER MASTER Silent Pro Hybrid 850
Mainboard: ASUS Maximus V FORMULA
HDD / SSD:
OCZ Agility 3 90gb
Seagate Barracuda ST1000DM003 1TB
CPU Cooler: stock
Case: haf x

2

Hi, can you post the STOP code, as well as the first set of numbers that appears? 

If windows skips by it quickly, press f8 before windows boots and disable the auto restart 

3

I belive i tied the cause to a bad stick of ram, i did some research about similar codes, so I ran metest one of my sticks gave 70,000+ errors in the first test let alone pass. the other came up clean in 2 passes.

 I'll disable auto boot and come back if it still happens

 

 

4

i'll crack it open in windbg

see if i can spot anything

5

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Downloads\other minidumps\minidumps\minidumps\Minidump\110412-9578-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*f:\symbols\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`030a2670
Debug session time: Sun Nov 4 12:06:02.781 2012 (UTC - 6:00)
System Uptime: 0 days 1:00:29.015
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 2ff, 301040005fe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29031 )</p><p>Followup: MachineOwner<br />---------</p><p>3: kd&gt; !analyze -v<br />*******************************************************************************<br />* *<br />* Bugcheck Analysis *<br />* *<br />*******************************************************************************</p><p>MEMORY_MANAGEMENT (1a)<br /> # Any other values for parameter 1 must be individually examined.<br />Arguments:<br />Arg1: 0000000000005003, The subtype of the bugcheck.<br />Arg2: fffff70001080000<br />Arg3: 00000000000002ff<br />Arg4: 00000301040005fe</p><p>Debugging Details:<br />------------------</p><p><br />BUGCHECK_STR: 0x1a_5003</p><p>CUSTOMER_CRASH_COUNT: 1</p><p>DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT</p><p>PROCESS_NAME: svchost.exe</p><p>CURRENT_IRQL: 0</p><p>LAST_CONTROL_TRANSFER: from fffff80002f44369 to fffff80002edcfc0</p><p>STACK_TEXT: <br />fffff880`0d0956b8 fffff800`02f44369 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`000002ff : nt!KeBugCheckEx<br />fffff880`0d0956c0 fffff800`02f0d5bf : 80000003`b80c78a0 80000003`b80c7321 fffffa80`0b282550 fffffa80`11c34ec8 : nt! ?? ::FNODOBFM::`string'+0x29031
fffff880`0d095750 fffff800`02efaed5 : 00000000`00000000 80000003`b80c78a0 00000000`00000000 fffffa80`11c34ec8 : nt!MiResolveTransitionFault+0x32f
fffff880`0d0957e0 fffff800`02ef9893 : 00000000`003c7228 000007fe`fdf6c068 fffff683`ff7efb60 fffffa80`11c34ec8 : nt!MiResolveProtoPteFault+0x325
fffff880`0d095870 fffff800`02ee9549 : 00000000`00000000 000007fe`fdf6c068 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0d095980 fffff800`02edb0ee : 00000000`00000000 000007fe`fdf6c068 00000000`77812501 00000000`00413ce0 : nt!MmAccessFault+0x359
fffff880`0d095ae0 000007fe`fdf1b6ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0067e7f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fdf1b6ca</p><p><br />STACK_COMMAND: kb</p><p>FOLLOWUP_IP: <br />nt! ?? ::FNODOBFM::`string'+29031
fffff800`02f44369 cc int 3</p><p>SYMBOL_STACK_INDEX: 1</p><p>SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+29031

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be

FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29031

BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29031

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

 

6

I think you be right

7

after taking out the bad stick i have been running solid. I was able to get threw a full test of 3D mark, and play a few rounds of BF3 without the system crashing.

Thank both of you for taking the time to respond.

8

hey, no prob, I like to help people as much as possible