Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Motherboard? BSODs, and trouble starting up


  • Please log in to reply
19 replies to this topic

#1 monkseatcheese

monkseatcheese

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:12:00 PM

Posted 10 April 2009 - 09:01 PM

Hi all, new to the forum

anyways I have been having some problems, started out with BSODs, a few days ago, and i decided to reinstall vista. I have reinstalled it 3 times now, stil having same problems. BSODs still happening. BCP code for all of them has been 109, most recently with an absolutely clean vista install, no service packs or updates. It also has had some trouble starting up if it has justbeen turned off, it dosent get past the XFX logo, and the mobo numbers are stuck at 75, which is the loading harddrive step. I have to let it sit for 5 min to start it up again. system temps all moderate. any ideas? i think its the motherboard.

system specs:
XFX 780i SLI Motherboard
9800 GTX PNY GPU
Q6600 Intel Processor
320 gb Hard Drive
D-Link DWA-552 WLAN
Windows Vista 64bit

Edited by monkseatcheese, 10 April 2009 - 09:59 PM.


BC AdBot (Login to Remove)

 


#2 monkseatcheese

monkseatcheese
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:12:00 PM

Posted 10 April 2009 - 10:34 PM

for anyone who cares just crashed again, different code this time, and i updated windows some
BCCode: 1a
BCP1: 0000000000041201
BCP2: FFFFF68000001488
BCP3: AE00000058C65867
BCP4: FFFFFA8003EFB400
OS Version: 6_0_6000
Service Pack: 0_0

#3 fairjoeblue

fairjoeblue

  • Members
  • 1,594 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:02:00 PM

Posted 10 April 2009 - 10:42 PM

You left out an important system spec.
What brand & model power supply ?

Also, you need to test the memory with a utility like Memtest86.

http://www.memtest86.com/memtest86-3.5.iso.zip

Extract the ISO image from the zip file then use a burning program that has the "Burn image to disk" feature to make a disk
Boot the disk
If Memtest86 finds any errors the memory is bad.
OCZ StealthXstream 700W,Gigabyte GA-EP45-UD3R , E8500, Arctic Freezer Pro 7, 3GB G.Skill PC8500,Gigabyte Radeon HD 4850 OC [1GB ], Seagate 250GB SATA II X2 in RAID 0, Samsung SATA DVD burner.

#4 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:00 PM

Posted 10 April 2009 - 10:44 PM

I think BCCode: 1a refers to a memory management error, you could have faulty or mismatched RAM.

3939.png

 


#5 hamluis

hamluis

    Moderator


  • Moderator
  • 55,257 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:00 PM

Posted 10 April 2009 - 11:16 PM

I don't see anything definitive, but I believe this one is worth a look: http://forums.techguy.org/windows-vista-7/...quent-bsod.html

Louis

#6 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:00 PM

Posted 10 April 2009 - 11:34 PM

What is the full the error log? Here's how you can open the memory dump (if one occured) over at Major Geeks to see what is going on. The process is a little different if you use Vista. You cannot open the error file in the directory it's saved in, you have to move it to the desktop. I found this at Microsoft's website surrounding the BCCode error:

As a matter of information, 0x1A errors are memory management errors. This
can indicate faulty memory (system or video), or a hdd issue if it was
working with virtual memory.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Edited by DJBPace07, 10 April 2009 - 11:35 PM.

3939.png

 


#7 monkseatcheese

monkseatcheese
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:12:00 PM

Posted 11 April 2009 - 03:55 PM

Thanks, im in the process of getting the memory dumps, ill post results
memtest stopped on test one at 58%, and after letting it sit for a while, it still was stuck at the same spot.
I started taking my memory out (i have 3 gigs), and when i tried to start up, BIOS said no bootable partions found.
I only got it to start after going into BIOS and making sure that it showed a hard drive connected.
I dont really know much about this stuff, but maybe motherboard still? because it could concevable be causing all the other components to not connect or fail

#8 hamluis

hamluis

    Moderator


  • Moderator
  • 55,257 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:00 PM

Posted 11 April 2009 - 05:24 PM

The fact that you have memory errors...needs more attention. Those alone are capable of producing every symptom you've described thus far.

You need to solve that before jumping to something else.

That means systematic...systematic testing. All modules, fewer modules together, modules in different slots. If the same slot generates errors with any given module...but one or more of the modules doesn't generate errors in a different slot...that's the type of logic I would apply.

Louis

Have you replaced your CMOS battery?

Edited by hamluis, 11 April 2009 - 05:26 PM.


#9 monkseatcheese

monkseatcheese
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:12:00 PM

Posted 11 April 2009 - 08:09 PM

there are only 2 minidumps on my system, here is ther first ones results:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8963ca55b, b3b7465ee8b94f74, fffff800019d3000, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kerne...itPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8963ca55b, Reserved
Arg2: b3b7465ee8b94f74, Reserved
Arg3: fffff800019d3000, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

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


BUGCHECK_STR: 0x109

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000184e250

STACK_TEXT:
fffff980`00c0ca78 00000000`00000000 : 00000000`00000109 a3a039d8`963ca55b b3b7465e`e8b94f74 fffff800`019d3000 : nt!KeBugCheckEx


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: BAD_STACK

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

and here are the second ones:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff68000001488, ae00000058c65867, fffffa8003efb400}

Probably caused by : memory_corruption ( nt!MiGetPageProtection+1dd )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff68000001488
Arg3: ae00000058c65867
Arg4: fffffa8003efb400

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


BUGCHECK_STR: 0x1a_41201

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: mscorsvw.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000189dd2d to fffff8000184dbd0

STACK_TEXT:
fffff980`1072e988 fffff800`0189dd2d : 00000000`0000001a 00000000`00041201 fffff680`00001488 ae000000`58c65867 : nt!KeBugCheckEx
fffff980`1072e990 fffff800`0187f750 : fffff683`ff79b0b8 00000000`00000000 00000000`00000000 00000000`f88002f7 : nt!MiGetPageProtection+0x1dd
fffff980`1072e9e0 fffff800`0187fbca : fffffa80`03efb400 00000000`00000000 fffffa80`03e28c10 fffff980`1072eab0 : nt!MiQueryAddressState+0x2d0
fffff980`1072ea40 fffff800`01ac5a2f : 00000000`00000004 00000000`00292000 fffffa80`043a7bb0 00000000`00000000 : nt!MiQueryAddressSpan+0xaa
fffff980`1072eab0 fffff800`0184d673 : ffffffff`ffffffff fffffa80`043a7bb0 fffff880`00000000 00000000`0012e0d8 : nt!NtQueryVirtualMemory+0x6dd
fffff980`1072ebb0 00000000`77b704aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012e0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b704aa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiGetPageProtection+1dd
fffff800`0189dd2d cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiGetPageProtection+1dd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 46830f41

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x1a_41201_nt!MiGetPageProtection+1dd

BUCKET_ID: X64_0x1a_41201_nt!MiGetPageProtection+1dd

Followup: MachineOwner
---------
both seem to suggest memory as you were saying hamilus.
oh and i almost forgot my PSU is a 800W BFG, and my memory is 3 gigs of Crucial Ballistix

and thanks for the help thus far everyone, i really appreciate it

#10 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:00 PM

Posted 11 April 2009 - 09:58 PM

I strongly suggest you run memtest on all your RAM sticks, if you are able. Windows also comes with its own memory checker that can be accessed from the Boot menu (I think) or with the Windows CD. More information can be found here: http://www.bleepingcomputer.com/tutorials/using-vista-windows-memory-diagnostics-tool/ I prefer memtest, but the one that comes with Windows is good too.

Edited by DJBPace07, 11 April 2009 - 09:59 PM.

3939.png

 


#11 monkseatcheese

monkseatcheese
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:12:00 PM

Posted 12 April 2009 - 12:19 PM

I have been having trouble getting either memtest or the Windows Vista Memory Test to run all the way through (they freeze), so for vista I cant access the full results, but they do both say that there are hardware problems during the testing. I will continue trying, and if it works i will post results

Edited by monkseatcheese, 12 April 2009 - 12:20 PM.


#12 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:00 PM

Posted 12 April 2009 - 02:16 PM

Is your RAM new? You may need to RMA it.

3939.png

 


#13 monkseatcheese

monkseatcheese
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:12:00 PM

Posted 12 April 2009 - 03:58 PM

I bought them almost a year ago from newegg. too late to RMA, i beleive.

#14 DJBPace07

DJBPace07

  • BC Advisor
  • 4,869 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:00 PM

Posted 12 April 2009 - 04:39 PM

Have you done anything, hardware wise to the PC that may have triggered the BSOD's? Have you flashed the BIOS recently? Have you run a hard drive check?

3939.png

 


#15 monkseatcheese

monkseatcheese
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:12:00 PM

Posted 12 April 2009 - 05:50 PM

No i havent done anything. I hadnt even opened up the case since I built it. Within the past hour, though, these have started up, seems to be a differnt problem, i have gotten 2 oth them, both same bcp code:
BCCode: 109
BCP1: A3A039D895C11714
BCP2: B3B7465EE83DE344
BCP3: FFFFF80001C3E980
BCP4: 0000000000000001
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1
here is windows debug results:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d895c11714, b3b7465ee83de344, fffff80001c3e980, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kerne...itPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d895c11714, Reserved
Arg2: b3b7465ee83de344, Reserved
Arg3: fffff80001c3e980, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

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


BUGCHECK_STR: 0x109

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80001a58350

STACK_TEXT:
fffffa60`01bb8698 00000000`00000000 : 00000000`00000109 a3a039d8`95c11714 b3b7465e`e83de344 fffff800`01c3e980 : nt!KeBugCheckEx


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: BAD_STACK

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

i have no clue whats wrong




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users