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

BSOD // windbg log inside


  • Please log in to reply
9 replies to this topic

#1 m0h1t

m0h1t

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:46 AM

Posted 28 February 2009 - 10:19 PM

Hey guys, cant seem to solve this issue by myself.
Please advise.


My system config
CPU: Intel E7200 - 375*9.5 @ 1.2750v (266*9.5@1.15v default)
RAM: Gskill DDR2 2x2gb 900Mhz CL4 @ 2.05v (800Mhz CL4@1.9v default)
Mobo: MSI P35 Neo3
GPU: XFX 8800GT 710/1825/1000 (Core Clock/Shader/Memory)
PSU: Corsair VX450
OS: Windows 7 beta build 7000 64bit



I am getting BSOD during startup, either during logon where one puts in the password or within 2 minutes after login.
This doesn't happen every time.

I have succesfully stress tested my overclock, 7 Hours OCCT and 4 hours memtest86+(6 loops).
All temps are within limits, though I'm not sure about the northbridge. It was very hot when I touched it after 4 hours of successful memory testing.

I got 3 BSOD consecutively on each restart after completing the 4 hours of memory testing. No bsod on 4th restart and after that.
I was having a similar issue in Vista Ultimate x64 before i decided to try Win7.

Below is my Windows debugger(x64) log.
Please help me identify whats causing the BSOD.

Microsoft Windows Debugger Version 6.11.0001.402 AMD64
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\030109-17234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7000 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c51050
Debug session time: Sun Mar 1 05:08:21.322 2009 (GMT+6)
System Uptime: 0 days 0:00:30.494
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004f10038, b6200006, 80a01}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004f10038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6200006, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000080a01, Low order 32-bits of the MCi_STATUS value.

Debugging Details:



BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff800`03fe8a98 fffff800`02ff4063 : 00000000`00000124 00000000`00000000 fffffa80`04f10038 00000000`b6200006 : nt!KeBugCheckEx
fffff800`03fe8aa0 fffff800`02b8f2c3 : 00000000`00000001 fffffa80`04f10ea0 00000000`00000000 fffffa80`04f10ef0 : hal!HalBugCheckSystem+0x1e3
fffff800`03fe8ae0 fffff800`02ff3d28 : 00000000`00000728 fffffa80`04f10ea0 fffff800`03fe8e70 fffff800`03fe8e00 : nt!WheaReportHwError+0x263
fffff800`03fe8b40 fffff800`02ff36af : fffffa80`04f10ea0 00000000`00000000 fffffa80`04f10ea0 fffff800`03fe8e70 : hal!HalpMcaReportError+0x4c
fffff800`03fe8c90 fffff800`02ff3578 : 00000000`00000002 00000000`00000001 fffff800`03fe8ef0 00000000`00000000 : hal!HalpMceHandler+0x90
fffff800`03fe8cd0 fffff800`02fe7d50 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`03fe8d00 fffff800`02a9d1ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`03fe8d30 fffff800`02a9d053 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`03fe8e70 fffff880`034db842 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`03fdcc68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN

BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN

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




The report generated by Windbg stated the following multiple times, but I removed them to make the report short.

Posted Image


TIA

Edited by m0h1t, 28 February 2009 - 10:20 PM.


BC AdBot (Login to Remove)

 


#2 Guest_Jay-P VIP_*

Guest_Jay-P VIP_*

  • Guests
  • OFFLINE
  •  

Posted 28 February 2009 - 10:37 PM

Hi there!

This may be a processor issue. You may want to get your processor tested at a local computer repair shop!

#3 m0h1t

m0h1t
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  

Posted 28 February 2009 - 11:46 PM

No.. OCCT stress the cpu very well. If there was something wrong with the cpu, It would have shown an error over the 7 hours test
I just measured my Nothbridge temp at 66*C.
Is this within limits?


edit: Okay so I don't think this is a thermal issue, since a just got BSOD on cold boot after 20 minutes.

Edited by m0h1t, 01 March 2009 - 12:44 AM.


#4 Guest_Jay-P VIP_*

Guest_Jay-P VIP_*

  • Guests
  • OFFLINE
  •  

Posted 01 March 2009 - 06:20 AM

WHEA_UNCORRECTABLE_ERROR -- Processor reporting error: Machine Processor could not write to the system log

CURRENT_IRQL: 0 -- Processor cannot communicate with the RPC service: FATAL ERROR 0 IRQL

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN <----This is the name of your Processor and the error it produced

BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN <----This is the name of your Processor and the error it produced


This is why, friend, that I requested that you get it checked!

#5 m0h1t

m0h1t
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:46 AM

Posted 01 March 2009 - 07:42 AM

ok. will do. :huh:

thnx :huh:

#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA

Posted 02 March 2009 - 07:50 AM

FWIW, this is an error generated by your processor. Not necessarily an error with the processor. Newer systems have the ability for the processor (and other hardware items) to report their issues to Windows.

Since you're overclocking, the first step would be to remove the overclock settings and test with default settings.
If the BSOD's don't recur, then it's the overclock causing this.

66 degrees C is awfully hot for a northbridge. Normally, the northbridge is cooler than the CPU, and 66 is awful high (although not critical) for a CPU. I'd suggest checking the specs for your mobo at the manufacturer's website to see if it can handle those temps.

FWIW - temp isn't the only thing that limits overclocks, but it's the most easily measurable. The other methods involve achieving a "successful" overclock. By that I mean that the system doesn't BSOD regularly - and is achieved by repeatedly adjusting settings until it becomes stable.

This is normally done by starting with a system that functions well at stock settings.
Then slowly increase the settings (one at a time) until instability is detected.
Then back off the overclock until stability returns - then stress test to ensure it's stable.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 m0h1t

m0h1t
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:46 AM

Posted 02 March 2009 - 09:30 AM

Hmm... I've been running the cpu on stock since over 30 hours, havn't encountered any bsod's as of yet.
What I'm not able to figure out is that if the cpu overclock (volt/thermal issue) was causing the bsod's then, why were they showing up only at startup.. why not occur during the stress test?
Does the cpu demand extra volts during startup?

and since I got a stop error at cold boot after 30 min gap, I'm guess it isn't a thermal issue.

Edited by m0h1t, 02 March 2009 - 09:30 AM.


#8 Guest_Jay-P VIP_*

Guest_Jay-P VIP_*

  • Guests
  • OFFLINE
  •  

Posted 03 March 2009 - 07:32 AM

Overclocking is rough. I usually prefer to overclock when cooling is at its best.

#9 m0h1t

m0h1t
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:16 PM

Posted 06 March 2009 - 07:30 PM

Problem solved. It was an OC issue.

#10 eastonch

eastonch

  • Members
  • 110 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:46 AM

Posted 15 March 2009 - 05:22 PM

i know you have sovled it but it was mostlikely Volatage settings that was prventing the CPU to communicate properly as it was not corretly set. ;)

hyope you learn next time nad why the hell have it on for 30hours? :huh:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users