BSOD, what could cause this?? Please help!

[sorinu26]

Hi I have a problem. I got BSOD yesterday while i was playing a game. After restart network card started to search for network, and it said that cable is not connected, afters some restarts, network came back to normal. What it could be?

These are my PC specs:

Operating System
MS Windows 7 Ultimate 32-bit

CPU
Intel Core 2 Duo E7500 @ 2.93GHz 33 °C
Wolfdale 45nm Technology

RAM
2.0GB Single-Channel DDR2 @ 400MHz (5-5-5-18)

Motherboard
MSI G41M4 (MS-7592) (CPU 1)

Graphics
H-17 @ 1280x1024
512MB GeForce 9600 GT (Undefined) 40 °C

Hard Drives
313GB Western Digital WDC WD3200AAKS-00M9A0 ATA Device (SATA) 32 °C

Optical Drives
HL-DT-ST DVDRAM GH22NS40 ATA Device

Audio
Realtek High Definition Audio

Network
You are connected to the internet
Connected through Realtek RTL8139/810x Family Fast Ethernet NIC

I uploaded all files needed for bsod debugging.

Please help me find what cause this.

 

[zigzag3143]

Hi I have a problem. I got BSOD yesterday while i was playing a game. After restart network card started to search for network, and it said that cable is not connected, afters some restarts, network came back to normal. What it could be?

These are my PC specs:

Operating System
MS Windows 7 Ultimate 32-bit

CPU
Intel Core 2 Duo E7500 @ 2.93GHz 33 °C
Wolfdale 45nm Technology

RAM
2.0GB Single-Channel DDR2 @ 400MHz (5-5-5-18)

Motherboard
MSI G41M4 (MS-7592) (CPU 1)

Graphics
H-17 @ 1280x1024
512MB GeForce 9600 GT (Undefined) 40 °C

Hard Drives
313GB Western Digital WDC WD3200AAKS-00M9A0 ATA Device (SATA) 32 °C

Optical Drives
HL-DT-ST DVDRAM GH22NS40 ATA Device

Audio
Realtek High Definition Audio

Network
You are connected to the internet
Connected through Realtek RTL8139/810x Family Fast Ethernet NIC

I uploaded all files needed for bsod debugging.

Please help me find what cause this.

These two were caused by hardware

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try -http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\bluescreen\Windows_NT6_BSOD_jcgriff2\032511-11840-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a0b000 PsLoadedModuleList = 0x82b53810
Debug session time: Fri Mar 25 11:07:30.975 2011 (GMT-4)
System Uptime: 0 days 0:00:06.692
Loading Kernel Symbols
.....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 857638fc, 0, 0}

Probably caused by : hardware

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

1: 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: 00000000, Machine Check Exception
Arg2: 857638fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8ad13cc4 82ad9fc5 857638e0 82b72c28 82b72c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8ad13ce4 82adadef 82b72c20 857638e0 82b72c50 nt!WheapProcessWorkQueueItem+0x56
8ad13d00 82a78f2b 82b72c20 00000000 848e1020 nt!WheapWorkQueueWorkerRoutine+0x1f
8ad13d50 82c1966d 00000001 acd4c624 00000000 nt!ExpWorkerThread+0x10d
8ad13d90 82acb0d9 82a78e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

 

[sorinu26]

i have this prob. with bluescreen from long time ago. every time i reinstalled windows and everything was perfect for some time. after like one or two months bluescreens came back again. what could cause this? if its an hardware prob, why after reinstall everything works fine for some months and then bsods again?? i'm very confused (