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 random

07 Sep 2010   #1
hometech99

Windows 7 Ultimate x64
 
 
BSOD random

This is my 3rd re-install.


Its Window 7 Ultimate x64 retail full copy (not upgrade).

It was a clean install on a custom system that is new. It ran memtest for 3 days stable.
This install has been up for less than 2 months.

Ive hadn't had a witnessed BSOD, but did find the PC had sitting at the login screen when I came home.

Last night I had Rhapsody on and was not at the PC- again, I went into the office and saw it had restarted.

Then I was at the PC just doing some work and did see the BSOD with USBPORT.SYS. But I read another post that said it might be something else.

My file is attached as per instructions.

I might have to go buy Vista if I cant stop this!


My System SpecsSystem Spec
07 Sep 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by hometech99 View Post
This is my 3rd re-install.


Its Window 7 Ultimate x64 retail full copy (not upgrade).

It was a clean install on a custom system that is new. It ran memtest for 3 days stable.
This install has been up for less than 2 months.

Ive hadn't had a witnessed BSOD, but did find the PC had sitting at the login screen when I came home.

Last night I had Rhapsody on and was not at the PC- again, I went into the office and saw it had restarted.

Then I was at the PC just doing some work and did see the BSOD with USBPORT.SYS. But I read another post that said it might be something else.

My file is attached as per instructions.

I might have to go buy Vista if I cant stop this!

These were caused by hardware and old drivers. One in particular is well known to cause BSOD's (ASACPI.sys from 2005)

ASACPI.sys Sun Mar 27 22:30:36 2005
[quote]
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
[/quote

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 Stop 0x124 - what it means and what to try

Thanks


Ken



Old drivers needing up date

Code:
ASACPI.sys        fffff880`04346000    fffff880`0434e000    0x00008000    0x42476c4c    3/27/2005 22:30:36                        
                     
Sahdad64.sys        fffff880`019dc000    fffff880`019e7000    0x0000b000    0x49068d5b    10/27/2008 23:56:11                        
Saibad64.sys        fffff880`019d3000    fffff880`019dc000    0x00009000    0x49068d5f    10/27/2008 23:56:15                        
SaibVdAd64.sys        fffff880`03e3e000    fffff880`03e48000    0x0000a000    0x49068d64    10/27/2008 23:56:20                        
spldr.sys        fffff880`019cb000    fffff880`019d3000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
spsys.sys        fffff880`094d6000    fffff880`09547000    0x00071000    0x4a085e7a    5/11/2009 13:20:58                        
amdxata.sys        fffff880`01466000    fffff880`01471000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
PxHlpa64.sys        fffff880`014d1000    fffff880`014dce00    0x0000be00    0x4a416253    6/23/2009 19:16:35
Analysis
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\Windows_NT6_BSOD_jcgriff2\080110-13041-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e66000 PsLoadedModuleList = 0xfffff800`030a3e50
Debug session time: Sun Aug  1 20:35:50.933 2010 (GMT-4)
System Uptime: 0 days 20:55:04.870
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800f074028, be000000, 800400}

Unable to load image \SystemRoot\System32\Drivers\fiodrive.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fiodrive.sys
*** ERROR: Module load completed but symbols could not be loaded for fiodrive.sys
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: fffffa800f074028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`02e2f903 : 00000000`00000124 00000000`00000000 fffffa80`0f074028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02fec4d3 : 00000000`00000001 fffffa80`0edcacc0 00000000`00000000 fffffa80`0edcad10 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`02e2f5c8 : 00000000`00000728 fffffa80`0edcacc0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`02e2ef1a : fffffa80`0edcacc0 fffff800`00ba8e70 fffffa80`0edcacc0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`02e2edd5 : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`02e22e88 : fffffa80`0ab71f50 fffffa80`0ab746a0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02ed4eac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02ed4d13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`010c9750 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0371dcc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fiodrive+0xb750


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------
My System SpecsSystem Spec
08 Sep 2010   #3
hometech99

Windows 7 Ultimate x64
 
 

HI & thanks

I got the newer asacpi from asus for my motherboard. So far so good! So, Ill see how it goes and report back if I get any more BSOD.
My System SpecsSystem Spec
11 Sep 2010   #4
hometech99

Windows 7 Ultimate x64
 
 

I changed the file as you suggested, and i was good for a few days.

I started with BSOD again yesterday & today again (9/10 & 9/11).

I ran the diagnostic again and attached the new files. Hopefully it shows the new problem.
My System SpecsSystem Spec
15 Sep 2010   #5
hometech99

Windows 7 Ultimate x64
 
 

any change in the second file?
My System SpecsSystem Spec
Reply

 BSOD random




Thread Tools




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 02:18 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App