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: Random BSOD's with random error messages after a new setup


15 Mar 2011   #1

Windows 7 Ultimate x64
 
 
Random BSOD's help :(

Hey!

I recently upgraded my setup with an Asus M4A78LT-M mobo, Athlon II X4 640 processor and TakeMS 2x2GB 1333MHz DDR3 memory. After installing the parts I tried to boot to Windows but it always resulted in the same BSOD so I reinstalled my system.

After installing Windows for the first time I had some problems downloading updates and I got a couple of BSOD's during the update process. I then thought the installation was faulty and reinstalled it again from a different DVD. Once again I got two BSOD's during the Windows update but after all updates and drivers had been installed the problems vanished and three days pass without any problems.

Today I was watching a movie from my computer and suddenly the computer made a BSOD. I rebooted, opened Event Viewer and got a BSOD again.

I ran memtest for 6 hours and it passed 5 times without errors. I had set the memory timings to 9-9-9-24 and memory voltage to 1.5 after the first BSOD's a few days back to ensure they were running at the proper settings. Apparently it didn't help.

I'm really not sure what might the problem. The new processor consumes 25W more than my previous E5200 so maybe my 500W power can't keep up with it sometimes?

All the required files are attached and information of my setup can be found in my profile. I really hope someone smarter than me could figure out what might be the problem!

My System SpecsSystem Spec
.

18 Mar 2011   #2

Windows 7 Ultimate x64
 
 

Added a new minidump from the latest crash. Happened again while watching a HD-movie. Also a bump.
My System SpecsSystem Spec
18 Mar 2011   #3

Windows 7 Ultimate x86 SP1
 
 

Hi,
I think you must update these 2 drivers:
Code:
ASACPI.sys   Sun Mar 27 18:30:36 2005 → Asus ATK0110 ACPI Utility 
PAC7302.SYS  Wed Nov 07 18:29:20 2007 → PC Camera (uninstall it if you cannot find the update)
Then we'll see how it goes.

Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02ca5e90
Debug session time: Wed Mar 16 17:05:16.019 2011 (GMT-8)
System Uptime: 0 days 11:57:16.705
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002d81ee1, fffff880031fc988, fffff880031fc1e0}

Probably caused by : memory_corruption ( nt!MiSegmentDelete+21 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002d81ee1, The address that the exception occurred at
Arg3: fffff880031fc988, Exception Record Address
Arg4: fffff880031fc1e0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiSegmentDelete+21
fffff800`02d81ee1 418b7d0c        mov     edi,dword ptr [r13+0Ch]

EXCEPTION_RECORD:  fffff880031fc988 -- (.exr 0xfffff880031fc988)
ExceptionAddress: fffff80002d81ee1 (nt!MiSegmentDelete+0x0000000000000021)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880031fc1e0 -- (.cxr 0xfffff880031fc1e0)
rax=0000000000000000 rbx=0000000000088081 rcx=fffffa8003e17800
rdx=0000000080000000 rsi=fffffa8003e17800 rdi=fffffa8003e17800
rip=fffff80002d81ee1 rsp=fffff880031fcbc0 rbp=0000000000000001
 r8=0000000000000000  r9=fffff880009ea180 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=fffdf8a0072e7190
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!MiSegmentDelete+0x21:
fffff800`02d81ee1 418b7d0c        mov     edi,dword ptr [r13+0Ch] ds:002b:fffdf8a0`072e719c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d110e8
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!MiSegmentDelete+21
fffff800`02d81ee1 418b7d0c        mov     edi,dword ptr [r13+0Ch]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002b2d8b1 to fffff80002d81ee1

STACK_TEXT:  
fffff880`031fcbc0 fffff800`02b2d8b1 : fffffa80`03e17808 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x21
fffff880`031fcc00 fffff800`02b2d76d : 00000000`00000000 00000000`00000080 fffffa80`039cc040 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`031fccc0 fffff800`02d7dcce : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`031fcd40 fffff800`02ad1fe6 : fffff880`02f63180 fffffa80`039ea480 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031fcd80 00000000`00000000 : fffff880`031fd000 fffff880`031f7000 fffff880`031fc7f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiSegmentDelete+21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

STACK_COMMAND:  .cxr 0xfffff880031fc1e0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MiSegmentDelete+21

BUCKET_ID:  X64_0x7E_nt!MiSegmentDelete+21

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

1: kd> lmvm nt
start             end                 module name
fffff800`02a60000 fffff800`0304a000   nt         (pdb symbols)          c:\symbols\ntkrnlmp.pdb\3844DBB920174967BE7AA4A2C20430FA2\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: C:\Symbols\ntkrnlmp.exe\4CE7951A5ea000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Sat Nov 20 01:30:02 2010 (4CE7951A)
    CheckSum:         0055CE0C
    ImageSize:        005EA000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
My System SpecsSystem Spec
.


18 Mar 2011   #4

Windows 7 Ultimate x64
 
 

Thanks for the reply!

I unplugged the PC Camera device but there don't seem to be new ATK0110 drivers for my motherboard available on ASUS website. I tried downloading the driver package called "chipset" but it only contained the onboard ATI graphics card drivers. Do you have any idea where I could get an up to date driver?
My System SpecsSystem Spec
18 Mar 2011   #5

Windows 7 Ultimate x86 SP1
 
 

Try this link → ASUSTeK Computer Inc.-Support-
ATK0110 is under utilities , could be part of the Asus PCProbe and AISuite Utilities.
My System SpecsSystem Spec
18 Mar 2011   #6

Windows 7 Ultimate x64
 
 

Thanks again wish The driver was part of the AISuite and is now up to date. We'll see if the system runs stable now. Thanks for the help!
My System SpecsSystem Spec
18 Mar 2011   #7

Windows 7 Ultimate x86 SP1
 
 

You're welcome.
My System SpecsSystem Spec
20 Mar 2011   #8

Windows 7 Ultimate x64
 
 

Well... Apparently the problem didn't vanish. Just woke up computer from sleep, tried to login to Live Messenger and got a BSOD (also included in the first zip):

Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c5ae90
Debug session time: Sun Mar 20 18:21:24.055 2011 (UTC + 2:00)
System Uptime: 0 days 0:00:05.740
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, fffffa80042448f8, 0, 0}

Probably caused by : hardware

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

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: 0000000000000000, Machine Check Exception
Arg2: fffffa80042448f8, 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`031a86f0 fffff800`02cd8d29 : fffffa80`042448d0 fffffa80`039fa680 fffffa80`00000005 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8c10 fffff800`02bb8217 : fffffa80`042448d0 fffff800`02c32658 fffffa80`039fa680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8c40 fffff800`02b1f865 : fffff800`02c943a0 00000000`00000001 fffffa80`04116fa0 fffffa80`039fa680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8c80 fffff800`02a9fa21 : fffff880`010bae00 fffff800`02b1f840 fffffa80`039fa600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8cb0 fffff800`02d32cce : 00000000`00000000 fffffa80`039fa680 00000000`00000080 fffffa80`039e6040 : nt!ExpWorkerThread+0x111
fffff880`031a8d40 fffff800`02a86fe6 : fffff880`02f63180 fffffa80`039fa680 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8d80 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`037a9540 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
---------

2: kd> lmvm nt
start             end                 module name
fffff800`02a15000 fffff800`02fff000   nt         (pdb symbols)          c:\windows\localsymbols\ntkrnlmp.pdb\3844DBB920174967BE7AA4A2C20430FA2\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\windows\localsymbols\ntkrnlmp.exe\4CE7951A5ea000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Sat Nov 20 11:30:02 2010 (4CE7951A)
    CheckSum:         0055CE0C
    ImageSize:        005EA000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
Mini Kernel Dump does not contain unloaded driver list
My System SpecsSystem Spec
21 Mar 2011   #9

Windows 7 Ultimate x86 SP1
 
 

Your latest dump have 0x124 error code that related to hardware.
So I recommend you to follow this steps → Stop 0x124 - what it means and what to try

Also for troubleshooting purpose, remove F-Secure Antivirus and replace it with MSE.
Then we'll see how things go.
http://www.microsoft.com/security_essentials/

log
Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c5ae90
Debug session time: Sun Mar 20 08:21:24.055 2011 (GMT-8)
System Uptime: 0 days 0:00:05.740
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, fffffa80042448f8, 0, 0}

Probably caused by : hardware

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

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: 0000000000000000, Machine Check Exception
Arg2: fffffa80042448f8, 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`031a86f0 fffff800`02cd8d29 : fffffa80`042448d0 fffffa80`039fa680 fffffa80`00000005 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8c10 fffff800`02bb8217 : fffffa80`042448d0 fffff800`02c32658 fffffa80`039fa680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8c40 fffff800`02b1f865 : fffff800`02c943a0 00000000`00000001 fffffa80`04116fa0 fffffa80`039fa680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8c80 fffff800`02a9fa21 : fffff880`010bae00 fffff800`02b1f840 fffffa80`039fa600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8cb0 fffff800`02d32cce : 00000000`00000000 fffffa80`039fa680 00000000`00000080 fffffa80`039e6040 : nt!ExpWorkerThread+0x111
fffff880`031a8d40 fffff800`02a86fe6 : fffff880`02f63180 fffffa80`039fa680 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8d80 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`037a9540 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
---------
My System SpecsSystem Spec
16 Nov 2011   #10

Win 7 Ult x64
 
 

I have had the same problem with this board from ASUS. The setup utilized the following brand new items:
Mushkin Callisto
2x WD RE4 (Raid 1)
AMD Tri-core Rana
Corsair XMS 4GB
Seasonic 520W Bronze
Win 7 Home Prem

I have run the following software: Memtest, Prime95, SuperPi, and driver verifier. Memtest caught a couple of errors on two different sticks, so I removed them, and tried entirely different ram, processor, gfx card etc. I reduced the clock speeds to less than half. Removed AV, etc. Driver verifier caught a few random drivers here, and there.

The exact symptom is that the machine Blue screens once per reboot generally within a few hours with as of now one of 15 different error codes, and then runs stable if left on, or put into standby. I have never seen anything like it, but it has to be the motherboard.

I only post here, because I found this thread via google, curious to see if others are experiencing a similar issue. (Also over at ocz forum). So in short RMA the board until you get one that works.
My System SpecsSystem Spec
Reply

 Random BSOD's with random error messages after a new setup




Thread Tools



Similar help and support threads for2: Random BSOD's with random error messages after a new setup
Thread Forum
BSOD after random, different error messages. BSOD Help and Support
Solved Random BSOD's, various error messages. ntoskernel.exe? BSOD Help and Support
Solved Frequent BSoD, random error messages. BSOD Help and Support
Getting a BSOD at random times, at least 6 different error messages. BSOD Help and Support
BSOD multiple error messages / random BSOD Help and Support
BSOD at seeminly random times with different error messages BSOD Help and Support
Random BSOD's, many different error messages. 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 08:19 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33