Windows 7: Windows 7 Ultimate 64 bit on new computer BSOD

iceman42 · 21 Jan 2010

Well I just finished about 3 days ago putting together a new system for my wife. Pretty standard setup; AMD 64 Bit Quad Core, Hitachi 1TB Deskstar, XFX Radeon HD 4670, DVD RW, 2x 2048 800 Mhz.

I did a 24 burn in and nothing, installed all her programs and let it sit for about 12 hours. Since then its BSOD 3 times in a 28 hour period. I have uploaded the dump files in case someone is interested in looking at them. I checked with an analysis software and it gave me a bit of nothing.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 1/21/2010 3:41:57 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xE56A95DB, 0xD, 0x0, 0xFFFFF80002EDABC2)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\012010-19390-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

On Thu 1/21/2010 2:52:58 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF8803B9E97E0, 0x2, 0x0, 0xFFFFF80002EDE8DD)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\012010-23680-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

On Wed 1/20/2010 2:19:17 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFFFFF8B483868, 0x2, 0x0, 0xFFFFF80002EC8114)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\011910-16926-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

Any help would be greatly appreciated.

**Pauly** · 21 Jan 2010

Hello Iceman, Welcome to SF

This fault is probably driver or memory based

I would start by running some basic hardware tests, download and run memtest86+ http://www.carrona.org/memdiag.html to check your ram and i would also run chkdsk and/or HDD diagnostic http://www.carrona.org/hddiag.html from your manufacturers website

Check system file integrity
Start>cmd.exe>right click run as admin>sfc /scannow

Check all drivers are up to date, and update this driver
bios64.sys 08/06/03 its extremely old, probably related to biostar
if you cant update it try removing the program its associated with temporarily till you get this problem sorted

If your OCing stop til this sorted, check ram settings in bios are correct ie voltage/timing/speed

Hope this helps, post back your results

iceman42 · 23 Jan 2010

Checked all drivers and ran memtest and the hitachi hdd test and all passed. ran the bios update and it said it was up to date, I looked at bios64.sys and it had a date of 03/05/09 on it. not sure if it ran and I didnt notice or if something else is up.

iceman42 · 25 Jan 2010

One other thing I have noticed and its a small sample size is that it seems that when my wife is playing World of Warcraft it will happen more frequently. It happened on the 23rd about 4 times all during a 3 hour span before that it had not happened for a day or so, all 4 times she was playing WoW and the previous crash she was playing WoW.

ickymay · 25 Jan 2010

I ran your minidump and got different results for the second one than you

Quote:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffff8b483868, 2, 0, fffff80002ec8114}

Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXSave+11 )

Followup: MachineOwner
---------
=========================================
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {e56a95db, d, 0, fffff80002edabc2}

Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )

Followup: MachineOwner
---------
===================================================
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8803b9e97e0, 2, 0, fffff80002ede8dd}

Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+1fd )

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

regarding the ntkrnlmp.exe microsoft says :
This problem occurs if one or more of the processors in the computer:
•Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
•Are damaged or defective.
•Are operating outside their specified ranges for temperature, power, or other conditions.

this error could also relate to the second error and or CPU temperatures ?
----------------------------------------
the second error amdppm.sys :
This behavior can occur if either one of the following conditions is true: There are incorrect settings in the computer's basic input/output system (BIOS) configuration.
-or-
One or more of the random access memory (RAM) modules that is installed on the computer is faulty.

this is an AMD Processor Driver and I reckon if you have the microsoft version installed I would try the driver version from the motherboard manufacturers website or vice-versa ?

I would also try running the system with only one stick of ram to see if this may be the issue ?

this file

Quote:

BIOS64.sys fffff880`03dae000 fffff880`03db6000 0x00008000 0x3ee27f50 08/06/2003 00:12:00

is old and needs removing and\or updating ?

iceman42 · 26 Jan 2010

Quote: Originally Posted by ickymay

this file

Quote:

BIOS64.sys fffff880`03dae000 fffff880`03db6000 0x00008000 0x3ee27f50 08/06/2003 00:12:00

is old and needs removing and\or updating ?

do you know where that file is located, I looked at the BIOS64.sys and it had a date of 9/2/2009 on it, maybe I am looking at the wrong date.

One thing I did last night cause it had a problem last night was remove the PCI Express Graphics card and went with the on-board card, and didnt seem to have any problems, but it wasn't a long test with WoW.

usasma · 26 Jan 2010

It should be in C:\Windows\System32\drivers - but not all 3rd party driver developers follow that convention.
Search your hard drive for all instances of BIOS64.sys

You can also use this free tool to locate the drivers: Autoruns for Windows

iceman42 · 30 Jan 2010

Okay so I did that and then ran the BIOS updater with the newly downloaded BIOS file from the MB site. My question is I have also removed the graphics card and gone with the on-board graphics card. Should I put that back in and then see if it crashes it again (I imagine that you are going to say yes). It was a pain in the neck to get the computer to work with it had to fumble around with BIOS to force it to choose that adapter.

**Pauly** · 30 Jan 2010

Quote: Originally Posted by iceman42

Okay so I did that and then ran the BIOS updater with the newly downloaded BIOS file from the MB site. My question is I have also removed the graphics card and gone with the on-board graphics card. Should I put that back in and then see if it crashes it again (I imagine that you are going to say yes). It was a pain in the neck to get the computer to work with it had to fumble around with BIOS to force it to choose that adapter.

Its up to you, have you regained stability since testing/updating or are there still errors, if all is well could try it with card back in, post back your results

Windows 7: Windows 7 Ultimate 64 bit on new computer BSOD

Windows 7 Ultimate 64 bit on new computer BSOD problems?