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

Constant BSOD in Windows 7 64


  • Please log in to reply
19 replies to this topic

#1 timmybadshoes

timmybadshoes

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:02 AM

Posted 06 January 2010 - 03:13 AM

Been getting constant BSODs on my new build and new install of windows 7. Ive reinstalled more times than I can count and even replaced all hardware except for cpu and hard rive but still crashing. If anyone could help would be greatly appreciated. Here are some of the minidumps.

Microsoft
® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\010210-16723-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 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Sat Jan 2 22:00:49.938 2010 (GMT-6)
System Uptime: 0 days 0:00:10.732
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, fffffa8002bdd8f8, 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: 0000000000000000, Machine Check Exception
Arg2: fffffa8002bdd8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02f396f0 fffff800`02ecfa89 : fffffa80`02bdd8d0 fffffa80`018e7040 00000000`0000000a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02f39c10 fffff800`02db1547 : fffffa80`02bdd8d0 fffff800`02e2a5f8 fffffa80`018e7040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02f39c40 fffff800`02d19b95 : fffff800`02e8c360 fffffa80`02bde158 fffffa80`02bde150 fffffa80`018e7040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02f39c80 fffff800`02c94161 : fffff880`010f4e00 fffff800`02d19b70 fffffa80`018e7040 02020003`03010303 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02f39cb0 fffff800`02f2a166 : 00000100`00010000 fffffa80`018e7040 00000000`00000080 fffffa80`0184f9e0 : nt!ExpWorkerThread+0x111
fffff880`02f39d40 fffff800`02c65486 : fffff880`02d63180 fffffa80`018e7040 fffff880`02d6df80 33031b2f`03182a03 : nt!PspSystemThreadStartup+0x5a
fffff880`02f39d80 00000000`00000000 : fffff880`02f3a000 fffff880`02f34000 fffff880`03b0d540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

1: kd> lmvm hardware
start end module name
Mini Kernel Dump does not contain unloaded driver list

----------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------



Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\010610-18330-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 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`01c05000 PsLoadedModuleList = 0xfffff800`01e42e50
Debug session time: Wed Jan 6 01:47:28.590 2010 (GMT-6)
System Uptime: 0 days 0:00:12.355
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, fffffa8002b01208, 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: 0000000000000000, Machine Check Exception
Arg2: fffffa8002b01208, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`021326f0 fffff800`01ebfa89 : fffffa80`02b011e0 fffffa80`018fbb60 00000000`00000006 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02132c10 fffff800`01da1547 : fffffa80`02b011e0 fffff800`01e1a5f8 fffffa80`018fbb60 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02132c40 fffff800`01d09b95 : fffff800`01e7c360 fffffa80`02862e68 fffffa80`02862e60 fffffa80`018fbb60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02132c80 fffff800`01c84161 : fffff880`0111ee00 fffff800`01d09b70 fffffa80`018fbb60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02132cb0 fffff800`01f1a166 : 00000000`00000000 fffffa80`018fbb60 00000000`00000080 fffffa80`018f2b30 : nt!ExpWorkerThread+0x111
fffff880`02132d40 fffff800`01c55486 : fffff880`01e5c180 fffffa80`018fbb60 fffff880`01e66f80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02132d80 00000000`00000000 : fffff880`02133000 fffff880`0212d000 fffff880`024c5540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

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


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`021326f0 fffff800`01ebfa89 : fffffa80`02b011e0 fffffa80`018fbb60 00000000`00000006 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02132c10 fffff800`01da1547 : fffffa80`02b011e0 fffff800`01e1a5f8 fffffa80`018fbb60 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02132c40 fffff800`01d09b95 : fffff800`01e7c360 fffffa80`02862e68 fffffa80`02862e60 fffffa80`018fbb60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02132c80 fffff800`01c84161 : fffff880`0111ee00 fffff800`01d09b70 fffffa80`018fbb60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02132cb0 fffff800`01f1a166 : 00000000`00000000 fffffa80`018fbb60 00000000`00000080 fffffa80`018f2b30 : nt!ExpWorkerThread+0x111
fffff880`02132d40 fffff800`01c55486 : fffff880`01e5c180 fffffa80`018fbb60 fffff880`01e66f80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02132d80 00000000`00000000 : fffff880`02133000 fffff880`0212d000 fffff880`024c5540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

1: kd> lmvm hardware
start end module name
Mini Kernel Dump does not contain unloaded driver list

BC AdBot (Login to Remove)

 


#2 Aus Smithy

Aus Smithy

  • Members
  • 160 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Brisbane QLD Australia
  • Local time:10:02 PM

Posted 07 January 2010 - 02:45 AM

Check the supplier sites for Windows 7 versions of your Display card, NIC etc.

Also some software applications (e.g. firewalls) may need to be upgraded to Windows 7 versions.

#3 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:02 AM

Posted 08 January 2010 - 01:44 PM

I've installed every driver I could possibly find. Except south bridge driver because Catalyst will only attempt to install the north bridge one. Also all the software im running is 64bit version or for windows 7.

#4 OldGrumpyBastard

OldGrumpyBastard

  • Members
  • 781 posts
  • OFFLINE
  •  
  • Location:"Way South of 'da Bridge"
  • Local time:07:02 AM

Posted 09 January 2010 - 09:59 AM

BIOS Updates?

Worth a read:

http://www.sevenforums.com/crash-lockup-de...s-what-try.html
Does this look like an OldGrumpyBastard or what?

#5 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:02 AM

Posted 09 January 2010 - 05:02 PM

Thank you but I've gone thru this list before and tested everything. Ram and video card were replaced when this first began just in case. Even the motherboard. I've installed every driver except for what I noticed the monitor drivers. Was able ot get the one for my acer monitor but not the samsung one yet. Don't know if that could cause a problem but I'm grasping at everything.

#6 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:02 AM

Posted 12 January 2010 - 02:55 AM

another crash dump if anyone can help


Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\011210-22479-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 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02e9ce50
Debug session time: Tue Jan 12 01:51:09.925 2010 (GMT-6)
System Uptime: 0 days 0:00:09.455
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, fffffa8002b138f8, 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: 0000000000000000, Machine Check Exception
Arg2: fffffa8002b138f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02f4e6f0 fffff800`02f19a89 : fffffa80`02b138d0 fffffa80`01907b60 00000000`00000014 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02f4ec10 fffff800`02dfb547 : fffffa80`02b138d0 fffff800`02e745f8 fffffa80`01907b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02f4ec40 fffff800`02d63b95 : fffff800`02ed6360 fffffa80`02d48978 fffffa80`02d48970 fffffa80`01907b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02f4ec80 fffff800`02cde161 : fffff880`00dd0e00 fffff800`02d63b70 fffffa80`01907b60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02f4ecb0 fffff800`02f74166 : 00000000`00000000 fffffa80`01907b60 00000000`00000080 fffffa80`0184a9e0 : nt!ExpWorkerThread+0x111
fffff880`02f4ed40 fffff800`02caf486 : fffff880`02d63180 fffffa80`01907b60 fffff880`02d6df80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f4ed80 00000000`00000000 : fffff880`02f4f000 fffff880`02f49000 fffff880`02f4e2c0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

1: kd> lmvm hardware
start end module name
Mini Kernel Dump does not contain unloaded driver list

#7 mybuddyeric

mybuddyeric

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia
  • Local time:07:02 AM

Posted 12 January 2010 - 11:03 AM

man i wish i had paid more attention in error log class... :huh:

[EDIT] Oh. Can you tell me if you somehow installed 32-bit versions of hardware drivers? Also, you stated that this was a "new build" and "new install". Can you be more specific? Did you build this machine yourself? Did you check the Windows 7 hardware compatibility list? Try researching your hardware via: http://www.microsoft.com/windows/compatibi...us/default.aspx

Post back when you're done so we can continue this investigation! Good luck.

Edited by mybuddyeric, 12 January 2010 - 11:09 AM.

fueled by coffee™

#8 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:02 AM

Posted 12 January 2010 - 07:24 PM

I did build it myself and I checked everything and all of it is compatible.

Asus M4A78 Plus
Phenom II x3XFX
Radeon 4770 HD
2gb Kingston 800

When I installed it went and got the 64bit drivers for everything, off Asus and Ati's site. I keep thinking it's video drivers, only because when I run speccy it never finds the card on the system. Also northbridge and southbridge drivers don't seem to install from catalyst manager. It says they do but if I run it again ti will say they haven't

#9 mybuddyeric

mybuddyeric

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia
  • Local time:07:02 AM

Posted 13 January 2010 - 11:31 AM

Have you tried basic hardware troubleshooting with removing various non-essential pieces of hardware one at a time? Also, did you follow Old Grumpy Bastard's advice?

BIOS Updates?

Worth a read:

http://www.sevenforums.com/crash-lockup-de...s-what-try.html


Give us an update as to where you are now in the resolution process. Thanks!
fueled by coffee™

#10 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:02 AM

Posted 13 January 2010 - 12:47 PM

Yes I've followed the guide. Just reinstalled again last night to go through it again. BIOS is updated along with the drivers, as much as I could and very little installed on it. For cooling it doesn't run hot when i monitor it and I added 3 12mm fans anyways, temperture never goes above 33c for cpu and 37c mobo.

Can't really remove any hardware because it only has the essentials in it. Plus most of it has been replaced form when he problem first started almost 3 months ago. Only ting from the original build is cpu and hard drive. I've tested hard drive with seatools multiple times and ran memtest and 3dmark06 and it goes through every test fine.

System is slightly dust but not any amount ot be concerned about but cleaned it anyway.

#11 mybuddyeric

mybuddyeric

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia
  • Local time:07:02 AM

Posted 13 January 2010 - 01:49 PM

I know you may not want to hear this, but have you tried installing another OS? I'm just afraid I'm not much of a hardware guru, and that's all I can think of. Try snagging a Linux distro (http://www.ubuntu.com/GetUbuntu/download) or even rolling back to a previous version of Windows. At least if you can't boot into another OS, you know it's a hardware conflict. Can anyone else come up with anything?
fueled by coffee™

#12 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:02 AM

Posted 13 January 2010 - 07:48 PM

I did install a copy of XP 32bit...it worked for a bit and would blue screen less but I would never get a chance to see the error codes. So I put 7 back on just to try and troubleshoot it from 7. Also the last couple blue screens have listed ci.dll

#13 mybuddyeric

mybuddyeric

  • Members
  • 51 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia
  • Local time:07:02 AM

Posted 13 January 2010 - 10:47 PM

Have you tried booting to your Win7 DVD and selecting the 'repair' function? Or running an 'sfc /scannow' command? How far into loading Windows can you get before you're BSOD'd out? Is it possible to narrow down what triggers the BSOD? Have you noticed any patterns or predictable time tables that seem to trigger the BSOD? I would suggest asking in the Microsoft forums about those specific stop error codes too. Keep us posted.
fueled by coffee™

#14 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:02 AM

Posted 14 January 2010 - 02:08 AM

Thank you for the help.

I can usually boot all the way in and use the computer for a few hours. Sometimes even play games for 3 or 4 hours. Usually when that happens if I turn it off and come back to it, it will blue screen a few times in a row before logging in.

The BSOD's seem to be pretty random, sometimes during video, game, just on the internet. I'll try and pay more close attention but I did notice that if it starts blue screening a lot in a row and i go into BIOS and change a setting like memory voltage or PCIE selections it will stop for a few hours and then BSOD again and I'll change them back for it to stop.

#15 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:08:02 AM

Posted 14 January 2010 - 05:35 PM

In the event log i see the errors as this:

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor ID: 2

So thinking bad cpu maybe?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users