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

24 Oct 2010   #1
LiPoUrR

Windows 7
 
 
Bsod

Guys i have problem with bsod... i am using windows 7 x64... i tried to format and than instal os again but it didnt help...


My System SpecsSystem Spec
.
24 Oct 2010   #2
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Hi; sorry you are having problem. I looked at your foour dumps. All indicate at hardware problem, three indicate memory corruption, and one is error code 124.

Please read this information on your error code 124: [2-Int] Stop 0x124 - what it means and what to try

Quote:
Error code 124, WHEA_UNCORRECTABLE_ERROR. Usual causes: Hardware, Incompatibility, May be driver corruption.

Error code 4E (2X), PFN_LIST_CORRUPT. Usual causes: Device driver, ?memory.

Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
Code:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0285d000 PsLoadedModuleList = 0xfffff800`02a9ae50
Debug session time: Sun Oct 24 06:17:32.053 2010 (GMT-4)
System Uptime: 0 days 0:00:06.895
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, fffffa80035ed038, 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: fffffa80035ed038, 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_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fce6b0 fffff800`02b17a89 : fffffa80`035ed010 fffffa80`024e2040 00000000`00000010 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fcebd0 fffff800`029f9667 : fffffa80`035ed010 fffff800`02a725f8 fffffa80`024e2040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fcec00 fffff800`02961c45 : fffff800`02ad4360 fffffa80`034e74d8 fffffa80`034e74d0 fffffa80`024e2040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fcec40 fffff800`028da961 : fffff880`0103ee00 fffff800`02961c20 fffffa80`024e2040 31904c92`4b9e80af : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fcec70 fffff800`02b71c06 : 6551a862`c4c923a4 fffffa80`024e2040 00000000`00000080 fffffa80`02453890 : nt!ExpWorkerThread+0x111
fffff880`02fced00 fffff800`028abc26 : fffff880`009e9180 fffffa80`024e2040 fffff880`009f3f40 f64d68bb`c94aa23d : nt!PspSystemThreadStartup+0x5a
fffff880`02fced40 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`0378b550 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_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

Kernel base = 0xfffff800`0285d000 PsLoadedModuleList = 0xfffff800`02a9ae50
Debug session time: Sun Oct 24 08:27:22.533 2010 (GMT-4)
System Uptime: 0 days 2:09:57.375
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, a1d0b, 3, a148a}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000a1d0b, page frame number
Arg3: 0000000000000003, current page state
Arg4: 00000000000a148a, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000295d38c to fffff800028cd740

STACK_TEXT:  
fffff880`060d3f58 fffff800`0295d38c : 00000000`0000004e 00000000`00000099 00000000`000a1d0b 00000000`00000003 : nt!KeBugCheckEx
fffff880`060d3f60 fffff800`0293f9f7 : 00000000`00000000 fffff680`000393f8 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`060d3fa0 fffff800`028a1c23 : fffffa80`02c186e0 fffff700`00001e62 0000007f`fffffff8 fffff8a0`040dfd98 : nt! ?? ::FNODOBFM::`string'+0x3223e
fffff880`060d4030 fffff800`028a068a : fffffa80`02c186e0 fffffa80`00000099 fffff880`00000aaa fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`060d48e0 fffff800`02bb2dcf : fffff8a0`0a5cb060 fffff880`060d4be0 00000000`00000000 fffffa80`02d24730 : nt!MmCleanProcessAddressSpace+0x96
fffff880`060d4930 fffff800`02b8b635 : 00000000`c0000005 00000000`00000001 00000000`7ef6e000 fffffa80`026a5b60 : nt!PspExitThread+0x92f
fffff880`060d49f0 fffff800`028aa1db : fffffa80`02d24730 fffff800`028aa101 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`060d4a20 fffff800`028aa620 : 00000000`00007530 fffff880`060d4aa0 fffff800`02b8b74c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`060d4aa0 fffff800`028cca37 : 00000000`00000001 fffffa80`02d24730 ffffffff`dc3cba00 00000000`7ef6e000 : nt!KiInitiateUserApc+0x70
fffff880`060d4be0 00000000`744d2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`050dedb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x744d2dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`0295d38c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

Kernel base = 0xfffff800`0285d000 PsLoadedModuleList = 0xfffff800`02a9ae50
Debug session time: Tue Oct 19 05:41:55.827 2010 (GMT-4)
System Uptime: 0 days 1:25:53.668
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c00c1350, 1, fffff96000768e40, 0}


Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!BitBltBitmap+228 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c00c1350, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff96000768e40, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b050e0
 fffff900c00c1350 

FAULTING_IP: 
cdd!BitBltBitmap+228
fffff960`00768e40 4801bd30130000  add     qword ptr [rbp+1330h],rdi

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  iw4sp.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006d9f5d0 -- (.trap 0xfffff88006d9f5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000b rbx=0000000000000000 rcx=fffff900c2a4bd30
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000768e40 rsp=fffff88006d9f760 rbp=fffff900c00c0020
 r8=fffff88006d9fcf8  r9=fffff88006d9fd00 r10=00000000000000ff
r11=fffff88006d9fce8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cdd!BitBltBitmap+0x228:
fffff960`00768e40 4801bd30130000  add     qword ptr [rbp+1330h],rdi ss:0018:fffff900`c00c1350=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000294df14 to fffff800028cd740

STACK_TEXT:  
fffff880`06d9f468 fffff800`0294df14 : 00000000`00000050 fffff900`c00c1350 00000000`00000001 fffff880`06d9f5d0 : nt!KeBugCheckEx
fffff880`06d9f470 fffff800`028cb82e : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`06d9f5d0 fffff960`00768e40 : 00000000`00000000 fffff900`c00c0020 fffff880`06d9fcf8 fffff880`06d9f818 : nt!KiPageFault+0x16e
fffff880`06d9f760 fffff960`0076a12b : 00000000`00000000 fffff900`c00ce9a8 fffff900`c22c2308 00000000`00000000 : cdd!BitBltBitmap+0x228
fffff880`06d9fcf0 fffff960`0076b138 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!DrvBitBlt+0x17b
fffff880`06d9ff10 fffff960`0033c6e3 : 00000000`00000000 fffff8a0`09690b70 fffff8a0`09690b70 00000000`00000001 : cdd!DrvCopyBits+0x44
fffff880`06d9ff80 fffff960`00281b24 : 00000000`00000000 00000000`00000000 00000000`0000cccc 00000000`00000000 : win32k!OffCopyBits+0xc7
fffff880`06d9ffe0 fffff960`00281fb8 : fffff900`c00ce9a8 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SpBitBlt+0x418
fffff880`06da03d0 fffff960`002d3f6c : 00000000`00000000 fffff900`c0088830 fffff900`c0000de0 fffff900`c0088830 : win32k!SpCopyBits+0x44
fffff880`06da0440 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!NtGdiBitBltInternal+0xc94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd!BitBltBitmap+228
fffff960`00768e40 4801bd30130000  add     qword ptr [rbp+1330h],rdi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cdd!BitBltBitmap+228

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4bf4408a

FAILURE_BUCKET_ID:  X64_0x50_cdd!BitBltBitmap+228

BUCKET_ID:  X64_0x50_cdd!BitBltBitmap+228

Followup: MachineOwner
---------
I find an almost guaranteed BSOD maker on your system:
Quote:
Code:
ASACPI.sys Sun Mar 27 22:30:36 2005
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).
I also find this out of date driver on your system. Outdated drivers can and do cause memory corruption and BSOD's. Update this driver.

Rt64win7.sys Thu Feb 26 04:04:13 2009 - Rt64win7.sys - Latest PCIe GBE (GigaBit Ethernet) drivers here: Realtek

Update these two drivers and reboot. Let's see how your system runs. If you get another BSOD, upload it, and we will test hardware. Please let us know how your system is running.
My System SpecsSystem Spec
24 Oct 2010   #3
LiPoUrR

Windows 7
 
 

thanks for your help man

my mother board is asus p5kpl am se and u gave me drivers for P7P55D LE... should i download these u gave me or for my motherboard?

Edit:i've downloaded drivers for my motherboard, i'll see if it worked thanks for help m8
My System SpecsSystem Spec
.

24 Oct 2010   #4
CarlTR6

Windows 7 Ultimate 32 bit
 
 

You made the right choice. And you are welcome.
My System SpecsSystem Spec
25 Oct 2010   #5
LiPoUrR

Windows 7
 
 

So far so good no bsods for now
My System SpecsSystem Spec
25 Oct 2010   #6
CarlTR6

Windows 7 Ultimate 32 bit
 
 

That is the news we like to hear!! Good work. Post back in a couple of days and update us. Hopefully, the moderators can mark this thread as solved. Fingers crossed!
My System SpecsSystem Spec
Reply

 Bsod




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 21:21.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App