Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD 124 code please help DUmp attached

17 Feb 2010   #1
sepholdem

7 ultima 32 bit
 
 
BSOD 124 code please help DUmp attached

HI all - i decide to replace my Pentium D with a Q6600 2.4 Ghz on windows 7 . For 20 mins it was fine then the first bsd - then another - re boot ok for 10 mins then another ....... so i re install windows just before desktop -bsd. Try ram sticks one by one but no good. Im sure there is no overheating - i updated the dell bios to 2.4.0 -i applied thermal paste. The main board Q6600 and 775socket are all compatiable - voltage is fine. ran mem test 5 times ok.
I feel that it has somthing to do with the driver i installed for the 8400GS card as i see some people using lap top drivers from different sites -
ANY HELP IS WELCOME


My System SpecsSystem Spec
.
17 Feb 2010   #2
Capt.Jack Sparrow

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Quote   Quote: Originally Posted by sepholdem View Post
HI all - i decide to replace my Pentium D with a Q6600 2.4 Ghz on windows 7 . For 20 mins it was fine then the first bsd - then another - re boot ok for 10 mins then another ....... so i re install windows just before desktop -bsd. Try ram sticks one by one but no good. Im sure there is no overheating - i updated the dell bios to 2.4.0 -i applied thermal paste. The main board Q6600 and 775socket are all compatiable - voltage is fine. ran mem test 5 times ok.
I feel that it has somthing to do with the driver i installed for the 8400GS card as i see some people using lap top drivers from different sites -
ANY HELP IS WELCOME
Hello Welcome to SF,

Follow this article this should help you https://www.sevenforums.com/crash-loc...-what-try.html

Good Luck,
Captain
My System SpecsSystem Spec
17 Feb 2010   #3
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by sepholdem View Post
HI all - i decide to replace my Pentium D with a Q6600 2.4 Ghz on windows 7 . For 20 mins it was fine then the first bsd - then another - re boot ok for 10 mins then another ....... so i re install windows just before desktop -bsd. Try ram sticks one by one but no good. Im sure there is no overheating - i updated the dell bios to 2.4.0 -i applied thermal paste. The main board Q6600 and 775socket are all compatiable - voltage is fine. ran mem test 5 times ok.
I feel that it has somthing to do with the driver i installed for the 8400GS card as i see some people using lap top drivers from different sites -
ANY HELP IS WELCOME
This crash was indeed caused by hardware. See here for what it means and how to fix. https://www.sevenforums.com/crash-loc...-what-try.html

Let us know if you need help

Ken
My System SpecsSystem Spec
.

17 Feb 2010   #4
sepholdem

7 ultima 32 bit
 
 

Thanks guys - but i have swapped every bit of hardware and still same problem - i have also went though the checklist Mr jacksparrow posted - but no joy.
However when i did uninstall my graphics card drivers i stopped getting the BSOD - then i went to the NVidea site and updated the latest driver and i got BSOD again - i have tried to the read the dump files and debbuging stuff and symbols but its got my head messed up. Is there any info on the dumpfile plz - thanks in advance
My System SpecsSystem Spec
17 Feb 2010   #5
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by sepholdem View Post
Thanks guys - but i have swapped every bit of hardware and still same problem - i have also went though the checklist Mr jacksparrow posted - but no joy.
However when i did uninstall my graphics card drivers i stopped getting the BSOD - then i went to the NVidea site and updated the latest driver and i got BSOD again - i have tried to the read the dump files and debbuging stuff and symbols but its got my head messed up. Is there any info on the dumpfile plz - thanks in advance

The entire analysis is below.

Where did you get your win dvd from?

The debugger doesnt have the correct symbols because it is a different build

Code:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS

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


Loading Dump File [C:\Users\K\Desktop\DUMP1f62.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x82843000 PsLoadedModuleList = 0x82982570
Debug session time: Wed Feb 17 17:03:33.850 2010 (GMT-5)
System Uptime: 0 days 0:46:34.004
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
......
2: 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: 84e8101c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 82843000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
80e088ac 8281af3f 00000124 00000000 84e8101c nt+0xd1454
80e088e8 82906004 8671e4c9 84e8101c 82898870 hal+0xef3f
80e08918 8281b1f1 84e82ea8 82828e40 00000000 nt+0xc3004
80e08a2c 8281b2e3 84e82ea8 84e82ef8 00000004 hal+0xf1f1
80e08a50 8281b3ff 00000000 84e82ef8 00000000 hal+0xf2e3
80e08a70 8281b548 00000000 84e82ea8 80e08b90 hal+0xf3ff
80e08a80 828115f5 00000000 00000000 00000000 hal+0xf548
80e08b90 8280e261 00000002 80e03750 00000000 hal+0x55f5
00000000 00000000 00000000 00000000 00000000 hal+0x2261


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------
My System SpecsSystem Spec
17 Feb 2010   #6
sepholdem

7 ultima 32 bit
 
 

Thanks ZigZag - i got the win dvd off a friend - maybe its a non legal one its called win 7 tiny -has alot of stuff stripped out but has some very useful applications . Maybe i try the a different o/s and re-post ?
I just bought the q6600 a few weeks ago brand new from canada - i hope thats not the problem !!
My System SpecsSystem Spec
17 Feb 2010   #7
Capt.Jack Sparrow

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Quote   Quote: Originally Posted by sepholdem View Post
Thanks ZigZag - i got the win dvd off a friend - maybe its a non legal one its called win 7 tiny -has alot of stuff stripped out but has some very useful applications . Maybe i try the a different o/s and re-post ?
I just bought the q6600 a few weeks ago brand new from canada - i hope thats not the problem !!
Well I'm sorry .. Here were would only support Legal version of Windows.

- Captain
My System SpecsSystem Spec
17 Feb 2010   #8
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by sepholdem View Post
Thanks ZigZag - i got the win dvd off a friend - maybe its a non legal one its called win 7 tiny -has alot of stuff stripped out but has some very useful applications . Maybe i try the a different o/s and re-post ?
I just bought the q6600 a few weeks ago brand new from canada - i hope thats not the problem !!

Knew it wasnt MS because of the build. It wold be a whole lot easier for us to support something we know.

Ken
My System SpecsSystem Spec
Reply

 BSOD 124 code please help DUmp attached




Thread Tools




Similar help and support threads
Thread Forum
Please help with BSOD, DUMP attached
Please help with BSOD, DUMP attached Thanks in advance, L,
BSOD Help and Support
BSOD error code system service exception (attached mini dump)
i have windows 7 home premium x64. i installed from disk 2 days ago. my pc is about 3 days old i built it myself. i am getting BSOD at least twice a day i got the error message 'system service exception' i have attached the mini dump files. thanks scott
BSOD Help and Support
BSOD (dump attached)
BSODs, various messages. This is all post fresh install on a clean drive. Ran Memtest a couple of times, 7 passes each time, no errors. All drivers are most recent versions (as far as I know, I update regularly) Windows update is up to date. I found a bios update but haven't flashed it yet. It...
BSOD Help and Support
Daily BSOD (dump attached)
Hey folks, My machine is blue screening daily. could someone read the dump file for me to help track down the culprit of the issue? I have attached the dump. thanks for the help!
BSOD Help and Support
New BSOD Dump file attached
A new BSOD, wonder whatever could be wrong this time...I just clicked a link on Firefox to watch a Youtube video when it happened.
BSOD Help and Support
Bsod code 124 dump attached
HI all - i decide to replace my Pentium D with a Q6600 2.4 Ghz on windows 7 . For 20 mins it was fine then the first bsd - then another - re boot ok for 10 mins then another ....... so i re install windows just before desktop -bsd. Try ram sticks one by one but no good. Im sure there is no...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 10:45.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App