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

BSoD problem still existing


  • Please log in to reply
15 replies to this topic

#1 Steinwertm

Steinwertm

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:home
  • Local time:03:56 AM

Posted 01 June 2010 - 04:17 PM

Hey all I really need some help this problem is getting so annoying I had a problem with a BSoD for my Custom build Computer here are the specs for it

Running
Windows 7 Home premium (64 bit)
AMD Atholon™ II X2 255 Processore 3.10 GHz
4.00 GB of Ram (one gig per stick 4 slots, already memtested each one individually)
Asus M4A785T-M motherboard
Biostar Radeon HD 4650 1g DDR2 video card
500 GB Hard drive

Already manually checked my Ram and went through the Malware forums which came up clean. This is the link to my previous forums the first is the Malware Forum
http://www.bleepingcomputer.com/forums/t/316727/redirected-custom-build-cpu-bsod-crashing/ http://www.bleepingcomputer.com/forums/t/316484/custom-build-blue-screen/

these are the the most current BSoD and Bugchecks since after we confirmed it was not malware

==================================================
Dump File : 060110-27175-01.dmp
Crash Time : 6/1/2010 1:55:09 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffa80`f08c1e2b
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`028844ff
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060110-27175-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052710-19328-01.dmp
Crash Time : 5/27/2010 3:54:23 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffae0`05d32cc8
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`0298a757
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052710-19328-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052610-25318-01.dmp
Crash Time : 5/26/2010 2:37:13 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffffff`ffffff89
Parameter 2 : 00000000`00000001
Parameter 3 : fffff960`00154de7
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052610-25318-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================


Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02800000 PsLoadedModuleList = 0xfffff800`02a3de50
Debug session time: Tue Jun 1 09:54:30.701 2010 (GMT-7)
System Uptime: 4 days 11:42:52.200
Loading Kernel Symbols
...............................................................
..................................................Page 11ad23 not present in the dump file. Type ".hh dbgerr004" for details
.........Page 1110db not present in the dump file. Type ".hh dbgerr004" for details
.....
...............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa80f08c1e2b, 0, fffff800028844ff, 5}

Page 11ad23 not present in the dump file. Type ".hh dbgerr004" for details
Page 11ad23 not present in the dump file. Type ".hh dbgerr004" for details
Page 1110db not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
Page 11ad23 not present in the dump file. Type ".hh dbgerr004" for details
Page 1110db not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+4df )

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

0: 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: fffffa80f08c1e2b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800028844ff, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

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

Page 11ad23 not present in the dump file. Type ".hh dbgerr004" for details
Page 11ad23 not present in the dump file. Type ".hh dbgerr004" for details
Page 1110db not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
Page 11ad23 not present in the dump file. Type ".hh dbgerr004" for details
Page 1110db not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details

READ_ADDRESS: fffffa80f08c1e2b

FAULTING_IP:
nt!MiAgeWorkingSet+4df
fffff800`028844ff 410fb6471b movzx eax,byte ptr [r15+1Bh]

MM_INTERNAL_CODE: 5

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: AvastSvc.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880031397a0 -- (.trap 0xfffff880031397a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffff6800001ad80
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028844ff rsp=fffff88003139930 rbp=0000000000000000
r8=0000000000000001 r9=fffffa8005c0aec8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!MiAgeWorkingSet+0x4df:
fffff800`028844ff 410fb6471b movzx eax,byte ptr [r15+1Bh] ds:00000000`0000001b=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800028ef801 to fffff80002870600

STACK_TEXT:
fffff880`03139638 fffff800`028ef801 : 00000000`00000050 fffffa80`f08c1e2b 00000000`00000000 fffff880`031397a0 : nt!KeBugCheckEx
fffff880`03139640 fffff800`0286e6ee : 00000000`00000000 91600050`2eb4b025 00000000`00001000 fffff800`029a4bfe : nt! ?? ::FNODOBFM::`string'+0x40ecb
fffff880`031397a0 fffff800`028844ff : 00000003`00000000 91500000`44329025 00000000`00000000 00000000`00000915 : nt!KiPageFault+0x16e
fffff880`03139930 fffff800`028f299e : fffffa80`05c0aec8 fffff880`00000001 00000000`00000001 fffff880`03139bb0 : nt!MiAgeWorkingSet+0x4df
fffff880`03139ae0 fffff800`02884de2 : 00000000`0000d510 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x49716
fffff880`03139b80 fffff800`0288506f : 00000000`00000008 fffff880`03139c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03139bd0 fffff800`02b15a86 : fffffa80`03a05680 00000000`00000080 fffffa80`039e8040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03139d40 fffff800`0284eb06 : fffff800`029eae80 fffffa80`03a05680 fffff800`029f8c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03139d80 00000000`00000000 : fffff880`0313a000 fffff880`03134000 fffff880`03139710 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiAgeWorkingSet+4df
fffff800`028844ff 410fb6471b movzx eax,byte ptr [r15+1Bh]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiAgeWorkingSet+4df

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+4df

BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+4df

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




Thanks All

BC AdBot (Login to Remove)

 


#2 sarunk

sarunk

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:05:56 AM

Posted 01 June 2010 - 05:21 PM

A per the error code it think the issue might be with the display adaptor. Please try to check the driver for display adaptor in device manager. Try to install the latest driver for display adaptor from device manufactures website. If that does not fix the problem then try to install inbox drivers from the operating system.

#3 sarunk

sarunk

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:05:56 AM

Posted 01 June 2010 - 05:23 PM

I am sorry i forgot to post few information. If the computer is booting up and randomly while working with the computer if it gives blue screen error then get into device manager and check the display adaptor driver.

If the computer does not boot at all then try to get into "Last known Good Configuration". If the computer boots up then check the device manager.

#4 Steinwertm

Steinwertm
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:home
  • Local time:03:56 AM

Posted 01 June 2010 - 07:19 PM

I went and updated the Driver for the display adapter. then i attempted to play a game and the BSoD came up here is the BSod view and debug report

==================================================
Dump File : 060110-28142-01.dmp
Crash Time : 6/1/2010 5:11:45 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8c0`0663b820
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`06556821
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060110-28142-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================

Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0285b000 PsLoadedModuleList = 0xfffff800`02a98e50
Debug session time: Tue Jun 1 17:10:28.950 2010 (GMT-7)
System Uptime: 0 days 3:15:57.343
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8c00663b820, 0, fffff88006556821, 5}

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Page 11aed9 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Probably caused by : atikmdag.sys ( atikmdag+353821 )

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

0: 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: fffff8c00663b820, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88006556821, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

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

PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

READ_ADDRESS: fffff8c00663b820 Paged pool

FAULTING_IP:
atikmdag+353821
fffff880`06556821 ff5020 call qword ptr [rax+20h]

MM_INTERNAL_CODE: 5

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4bbbe425

MODULE_NAME: atikmdag

FAULTING_MODULE: fffff88006203000 atikmdag

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: PlantsVsZombie

CURRENT_IRQL: 0

TRAP_FRAME: fffff88001f982d0 -- (.trap 0xfffff88001f982d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8c00663b800 rbx=0000000000000000 rcx=fffffa80055a2d90
rdx=0000000000000020 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006556821 rsp=fffff88001f98460 rbp=0000000000000000
r8=fffff88001f984d0 r9=0000000000000640 r10=fffffa80055a2d90
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
atikmdag+0x353821:
fffff880`06556821 ff5020 call qword ptr [rax+20h] ds:fffff8c0`0663b820=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000294a801 to fffff800028cb600

STACK_TEXT:
fffff880`01f98168 fffff800`0294a801 : 00000000`00000050 fffff8c0`0663b820 00000000`00000000 fffff880`01f982d0 : nt!KeBugCheckEx
fffff880`01f98170 fffff800`028c96ee : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`048e0280 : nt! ?? ::FNODOBFM::`string'+0x40ecb
fffff880`01f982d0 fffff880`06556821 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`01f98460 fffff880`06555e00 : fffffa80`055a2d90 00000000`00000000 fffff880`0660e580 fffff800`02a45e80 : atikmdag+0x353821
fffff880`01f984a0 fffff880`05a0562e : fffff880`01f987c0 fffffa80`0000ffff 00000000`00000000 fffff880`01f987c0 : atikmdag+0x352e00
fffff880`01f98500 fffff880`0408fe34 : fffffa80`0463c000 fffffa80`0463c000 fffff880`01f987c0 00000000`00000000 : atikmpag+0x562e
fffff880`01f98530 fffff880`040c18b3 : fffffa80`04276b60 fffff8a0`02036000 fffff8a0`07fde2d0 fffff880`01f98930 : dxgkrnl!DXGADAPTER::DdiDescribeAllocation+0x50
fffff880`01f98560 fffff880`040c0d73 : fffff8a0`40000900 fffff8a0`00000000 fffff880`01f988c0 fffff880`01f988f0 : dxgkrnl!DXGCONTEXT::Present+0x537
fffff880`01f98880 fffff960`0021b510 : fffffa80`04276b60 00000000`7efdb000 00000000`7efdb000 00000000`00000020 : dxgkrnl!DxgkPresent+0x543
fffff880`01f98bf0 fffff800`028ca853 : fffffa80`04276b60 00000000`00000000 fffffa80`00000000 fffffa80`055bdca0 : win32k!NtGdiDdDDIPresent+0x18
fffff880`01f98c20 00000000`74dc13ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74dc13ca


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+353821
fffff880`06556821 ff5020 call qword ptr [rax+20h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: atikmdag+353821

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x50_atikmdag+353821

BUCKET_ID: X64_0x50_atikmdag+353821

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

#5 coxchris

coxchris

  • Members
  • 1,151 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Atwater
  • Local time:02:56 AM

Posted 01 June 2010 - 09:34 PM

Try a check disk scan usually bad blocks on the hard drive can cause this stop code

To run a check disk scan

Start>Search>CMD>
chkdsk C: /f

You will need to run as administrator if you get denied access to the system.

AA in Computer Networking Technology

BS in Information Technology 

Comptia A+, Project+, L+

Renewable:  N+,S+

CIW Web Design Specialist, JavaScript Specialist,  Database Design Specialist 

LPIC-1, SUSE 


#6 Steinwertm

Steinwertm
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:home
  • Local time:03:56 AM

Posted 02 June 2010 - 01:22 AM

I ran the Chkdsk came back clean. I'm wondering, i have an external hard drive and sometimes I'll be running programs straight off of it, could it be the external that is causing the BSod. also i didnt update the in-box drivers from the OS wasn't sure what those were.

#7 sarunk

sarunk

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:05:56 AM

Posted 02 June 2010 - 02:00 AM

Ok now lets again narrow down the issue.

Please try to disable the display adaptor from device manager so that we can make sure it is not at all a problem with the display card or its drivers. Now again check whether the BOSD occurs. If it happens again after disabling the display card then we can try other steps.

The possibilities of root cause are more in BSOD. Recently i found that the XMS 3 memory which normaly runs at 1.5v actually needs to be set to 1.6v for theMainboard. Try changing it lets check if that works.

If that does not work then put in the windows 7 disk in the drive and overright the OS again. You will get two options upgrade or custom installation. Please choose upgrade so that it will only recover the corrupted files in computer. If you choose custom then all the software in the computer will be removed and you may need to reinstall it again.

#8 Steinwertm

Steinwertm
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:home
  • Local time:03:56 AM

Posted 02 June 2010 - 03:52 AM

ok just disabled the display adaptor, ill let you know if i get a BSoD. also how would i set the XMS 3 Memory to 1.6v?

#9 Steinwertm

Steinwertm
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:home
  • Local time:03:56 AM

Posted 02 June 2010 - 04:18 PM

k i think we can rule out the Display Adapter just came home from school and it had blue screened here are the codes

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: 0000000000002000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF88004263E25
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\060210-19359-01.dmp
C:\Users\SteinwertM\AppData\Local\Temp\WER-37253-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104...mp;clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt



==================================================
Dump File : 060210-19359-01.dmp
Crash Time : 6/2/2010 2:12:16 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00002000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`04263e25
Caused By Driver : usbehci.sys
Caused By Address : usbehci.sys+7e25
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060210-19359-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================



Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at start of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0280b000 PsLoadedModuleList = 0xfffff800`02a48e50
Debug session time: Wed Jun 2 12:08:09.554 2010 (GMT-7)
System Uptime: 0 days 13:16:07.052
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols

Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {2000, 2, 1, fffff88004263e25}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000002000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004263e25, address which referenced memory

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


WRITE_ADDRESS: 0000000000002000

CURRENT_IRQL: 2

FAULTING_IP:
usbehci!EHCI_DisableInterrupts+11
fffff880`04263e25 0000 add byte ptr [rax],al

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88002f1ba50 -- (.trap 0xfffff88002f1ba50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000002000 rbx=0000000000000000 rcx=fffffa8004ee56a0
rdx=0000000010000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004263e25 rsp=fffff88002f1bbe0 rbp=0000000000000000
r8=000000004f444648 r9=0000000000000000 r10=0000000000025cd8
r11=fffffa80044ff930 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
usbehci!EHCI_DisableInterrupts+0x11:
fffff880`04263e25 0000 add byte ptr [rax],al ds:00000000`00002000=??
Resetting default scope

MISALIGNED_IP:
usbehci!EHCI_DisableInterrupts+11
fffff880`04263e25 0000 add byte ptr [rax],al

LAST_CONTROL_TRANSFER: from fffff8000287ab69 to fffff8000287b600

STACK_TEXT:
fffff880`02f1b908 fffff800`0287ab69 : 00000000`0000000a 00000000`00002000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b910 fffff800`028797e0 : 00000000`00000001 00000000`00000008 fffff880`00e9d764 fffffa80`047a4fb0 : nt!KiBugCheckDispatch+0x69
fffff880`02f1ba50 fffff880`04263e25 : 00000000`00000008 00000000`00000000 00000000`00000001 fffffa80`047a4b80 : nt!KiPageFault+0x260
fffff880`02f1bbe0 00000000`00000008 : 00000000`00000000 00000000`00000001 fffffa80`047a4b80 00000000`00002000 : usbehci!EHCI_DisableInterrupts+0x11
fffff880`02f1bbe8 00000000`00000000 : 00000000`00000001 fffffa80`047a4b80 00000000`00002000 00000000`0000003f : 0x8


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !usbehci
4 errors : !usbehci (fffff88004263dc4-fffff88004263df4)
fffff88004263dc0 48 8b cf 41 *74 5f 69 45 45 4c 89 7c 24 20 ff 15 H..At_iEEL.|$ ..
fffff88004263dd0 ac 56 00 00 *e4 8b 9f b8 00 00 00 45 89 5c 24 08 .V.........E.\$.
fffff88004263de0 f0 44 09 3c *75 8b c6 48 8b 9c 24 a0 00 00 00 48 .D.<u..H..$....H
fffff88004263df0 83 c4 50 41 *f3 41 5e 41 5d 41 5c 5f 5e 5d c3 cc ..PA.A^A]A\_^]..

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption

Edited by Steinwertm, 02 June 2010 - 04:19 PM.


#10 Sweatdog

Sweatdog

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:06:56 AM

Posted 02 June 2010 - 04:43 PM

I am new to the tech forums and hardware/software troubleshooting in general, but I did have the same problem you are now. I am guessing you installed/upgraded to Windows 7 very recently? I was getting constant, and seemingly random BSOD's when I clean installed Win7 two days ago on my new BIOSTAR mobo. They all referenced the display adapter (x050 error codes) as Sarunk suggested. I also happen to have a RADEON 4xxx series card (Sapphire 4850 512MB) and the 10.5 catalyst driver update did not solve the problem for me either.

While trying to flash my BIOS as a possible solution, I got a BSOD :huh: . I cried alittle before I even attempted to reboot. Of course I was NOT able to reset BIOS with the manual jumper pins or with a CMOS battery reset. Luckily Newegg.com, in all their awesomeness, gave me a full refund including postage. My point is be very careful with this random BSOD if you do attempt to flash your BIOS. Do it in safe mode under MINIMAL system stress if you do.

In the end all I did was take out my BIOSTAR TA790XE mobo and put in my slightly older GIGABYTE GA-MA-770-DS3 mobo, and literally all BSOD's have vanished, and I didnt have to alter a single driver for any component. I cant tell you why exactly other than obvious compatibility on some level, but its something to consider.

Edited by Sweatdog, 02 June 2010 - 04:47 PM.


#11 Steinwertm

Steinwertm
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:home
  • Local time:03:56 AM

Posted 02 June 2010 - 07:20 PM

Im thinking if it is my video card. i have an older one i just gave to my brother. perhaps i should just give him this one and try that old one out. But when i disabled the card it still BSed on me. this is really annoying LOL, also I already tried flashing my Bios a while before I decided to reinstalled windows it didn't help.

Edited by Steinwertm, 02 June 2010 - 07:21 PM.


#12 hamluis

hamluis

    Moderator


  • Moderator
  • 56,541 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:56 AM

Posted 02 June 2010 - 08:36 PM

Did you run Memtest86+ with various combinations of your RAM modules?

Kind of pointless to test them individually...if you run them together and have problems, IMO.

Louis

#13 sarunk

sarunk

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:05:56 AM

Posted 02 June 2010 - 10:10 PM

How old the computer is?. Try to update the chip set drivers and check whether BIOS is upto data. If not then flash BIOS. Is there any way you can upload the minidump file. So that we can research and check it.

In the mean while you can also disable all the non microsoft services and then check the status. Click on start and type "Msconfig" in startsearch and press "Enter". It will open a windows "System Configuration utility". Put check mark on "Hide all microsoft services" and it will display all non microsoft services so disable it. Apply the changes and restart the computer and check the status.

Please remove all the external hardware devices except keyboard and mouse, Some times it might happen due to external device.

#14 Steinwertm

Steinwertm
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:home
  • Local time:03:56 AM

Posted 03 June 2010 - 03:12 AM

i built the piece in April, worked fine for a month then started doing this stuff. I ran Memtest 86+ on it with all the ram sticks in and individually but i didn't do any combination. I just disabled my network driver but still blue screened. Im pretty sure the chips set driver is up to date, same with the bios. how would i load the minidump files? i have them all still. i've also already unplugged all the external stuff. well except my speakers. ill try turning off the non Microsoft services. here is the latest codes

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF88004319DCB
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1




==================================================
Dump File : 060310-15849-01.dmp
Crash Time : 6/3/2010 12:51:42 AM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050031
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff880`04319dcb
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+7dcb
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060310-15849-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at start of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0284c000 PsLoadedModuleList = 0xfffff800`02a89e50
Debug session time: Thu Jun 3 00:50:46.080 2010 (GMT-7)
System Uptime: 0 days 7:38:09.578
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols

Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff88004319dcb}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88004319dcb

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


BUGCHECK_STR: 0x7f_8

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800028bbb69 to fffff800028bc600

STACK_TEXT:
fffff800`03b94d28 fffff800`028bbb69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`03b94d30 fffff800`028ba032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`03b94e70 fffff880`04319dcb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`0000d024 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiSendToExecutionQueue+0x8d7


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !dxgmms1
4 errors : !dxgmms1 (fffff88004319dc4-fffff88004319df4)
fffff88004319dc0 dd ee ff ff *75 01 bc 24 d0 00 00 00 40 0f b6 c7 ....u..$....@...
fffff88004319dd0 44 0f 22 c0 *e9 12 40 0f b6 c7 44 0f 22 c0 48 8b D."...@...D.".H.
fffff88004319de0 cd e8 d2 7a *0d 00 8b d8 8b c3 48 8b 9c 24 18 01 ...z......H..$..
fffff88004319df0 00 00 48 81 *c7 c0 00 00 00 41 5f 41 5e 41 5d 41 ..H......A_A^A]A

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------




Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF88003DF2DB9
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\060310-15334-01.dmp
C:\Users\SteinwertM\AppData\Local\Temp\WER-23821-0.sysdata.xml


Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.
==================================================
Dump File : 060310-15334-01.dmp
Crash Time : 6/3/2010 1:07:40 AM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050031
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff880`03df2db9
Caused By Driver : atikmdag.sys
Caused By Address : atikmdag.sys+39cdb9
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\060310-15334-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================


Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available



WinDebugg
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02867000 PsLoadedModuleList = 0xfffff800`02aa4e50
Debug session time: Thu Jun 3 01:06:39.702 2010 (GMT-7)
System Uptime: 0 days 0:15:14.075
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff88003df2db9}

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
Probably caused by : atikmdag.sys ( atikmdag+39cdb9 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88003df2db9

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

PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x7f_8

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028d6b69 to fffff800028d7600

STACK_TEXT:
fffff800`03ba2d28 fffff800`028d6b69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`03ba2d30 fffff800`028d5032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`03ba2e70 fffff880`03df2db9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`01f7245b 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x39cdb9


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+39cdb9
fffff880`03df2db9 c3 ret

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: atikmdag+39cdb9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4bbbe425

FAILURE_BUCKET_ID: X64_0x7f_8_atikmdag+39cdb9

BUCKET_ID: X64_0x7f_8_atikmdag+39cdb9

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

0: kd> lmvm atikmdag
start end module name
fffff880`03a56000 fffff880`04100000 atikmdag (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Tue Apr 06 18:47:17 2010 (4BBBE425)
CheckSum: 0065DD35
ImageSize: 006AA000
File version: 8.1.1.1016
Product version: 8.1.1.1016
File flags: 8 (Mask 3F) Private
File OS: 40004 NT Win32
File type: 3.4 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: ATI Technologies Inc.
ProductName: ATI Radeon Family
InternalName: atikmdag.sys
OriginalFilename: atikmdag.sys
ProductVersion: 8.01.01.1016
FileVersion: 8.01.01.1016
FileDescription: ATI Radeon Kernel Mode Driver
LegalCopyright: Copyright © 1998-2006 ATI Technologies Inc.

#15 sarunk

sarunk

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:05:56 AM

Posted 03 June 2010 - 06:48 PM

You informed that you have four GB of Ram in the computer. Try to use only 1GB of RAM and you can check the status. There are some sites in which you can upload the mindump file and link it here, SO that we can analyse it.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users