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

Need BSOD help - dump


  • Please log in to reply
6 replies to this topic

#1 Nymphs

Nymphs

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:07:23 PM

Posted 19 September 2011 - 07:48 AM

I just recently (within the past 2 weeks) reinstalled my Windows 7 OS and I'm already getting BSOD's. All help is appreciated. Thank you.

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

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff88004fcfe97, fffff880059c36d8, fffff880059c2f30}

Probably caused by : memory_corruption

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004fcfe97, The address that the exception occurred at
Arg3: fffff880059c36d8, Exception Record Address
Arg4: fffff880059c2f30, 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: 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+403
fffff880`04fcfe97 488b6c2060      mov     rbp,qword ptr [rax+60h]

EXCEPTION_RECORD:  fffff880059c36d8 -- (.exr 0xfffff880059c36d8)
ExceptionAddress: fffff88004fcfe97 (dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x0000000000000403)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000060
Attempt to read from address 0000000000000060

CONTEXT:  fffff880059c2f30 -- (.cxr 0xfffff880059c2f30)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002
rdx=fffff8a002a6ffe0 rsi=0000000000000024 rdi=fffffa8005cb2000
rip=fffff88004fcfe97 rsp=fffff880059c3910 rbp=0000000000000000
 r8=fffff8a0029f66a0  r9=0000000000000001 r10=fffff8a002a6ffd0
r11=fffffa8005983890 r12=0000000000000000 r13=0000000000000000
r14=fffffa8003c06360 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x403:
fffff880`04fcfe97 488b6c2060      mov     rbp,qword ptr [rax+60h] ds:002b:00000000`00000060=????????????????
Resetting default scope

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:  0000000000000060

READ_ADDRESS:  0000000000000060 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+403
fffff880`04fcfe97 488b6c2060      mov     rbp,qword ptr [rax+60h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

LAST_CONTROL_TRANSFER:  from fffff88004fea65d to fffff88004fcfe97

STACK_TEXT:  
fffff880`059c3910 fffff880`04fea65d : 00000000`00000000 fffff8a0`02cf9c30 fffffa80`00000000 fffffa80`03c06360 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x403
fffff880`059c3ae0 fffff880`04fea398 : fffff880`009ecf40 fffff880`04fe9d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`059c3cd0 fffff880`04fe9e96 : 00000000`00000000 fffffa80`042cb780 00000000`00000080 fffffa80`052e2410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`059c3d00 fffff800`02d18fee : 00000000`01cf1533 fffffa80`05984b60 fffffa80`03b66b30 fffffa80`05984b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`059c3d40 fffff800`02a6f5e6 : fffff880`009e8180 fffffa80`05984b60 fffff880`009f2fc0 2c307830`2c307830 : nt!PspSystemThreadStartup+0x5a
fffff880`059c3d80 00000000`00000000 : fffff880`059c4000 fffff880`059be000 fffff880`059c3680 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -db !dxgmms1
5 errors : !dxgmms1 (fffff88004fcfa0a-fffff88004fcfe9a)
fffff88004fcfa00  4c  24  60  49  63  c5  44  3b  eb  76 *69  48  8d  04  40  4c L$`Ic.D;.viH..@L
...
fffff88004fcfaa0  54  24  10  53  55  56  57  41  54  41 *51  41  56  41  57  48 T$.SUVWATAQAVAWH
...
fffff88004fcfcb0  01  1e  c0  e8  74  84  00  00  45  33 *cd  45  8b  e5  44  39 ....t...E3.E..D9
...
fffff88004fcfe10  00  44  8b  6c  24  48  eb  03  45  8b *ca  48  8b  94  24  d8 .D.l$H..E..H..$.
...
fffff88004fcfe90  02  8b  dd  3b  f5  76  73  48  8b  6c *20  60  48  8b  74  24 ...;.vsH.l `H.t$

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff880059c2f30 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,632 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:23 PM

Posted 19 September 2011 - 07:51 AM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 Nymphs

Nymphs
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:07:23 PM

Posted 19 September 2011 - 08:24 AM

==================================================

Dump File         : 091911-19609-01.dmp

Crash Time        : 19/09/2011 13:09:54

Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug Check Code    : 0x1000007e

Parameter 1       : ffffffff`c0000005

Parameter 2       : fffff880`04fcfe97

Parameter 3       : fffff880`059c36d8

Parameter 4       : fffff880`059c2f30

Caused By Driver  : dxgmms1.sys

Caused By Address : dxgmms1.sys+1de97

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : dxgmms1.sys+1de97

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\091911-19609-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7601

Dump File Size    : 275,312

==================================================



==================================================

Dump File         : 090511-15709-01.dmp

Crash Time        : 05/09/2011 18:33:46

Bug Check String  : BUGCODE_USB_DRIVER

Bug Check Code    : 0x000000fe

Parameter 1       : 00000000`00000008

Parameter 2       : 00000000`00000006

Parameter 3       : 00000000`00000005

Parameter 4       : fffffa80`04fde160

Caused By Driver  : usbhub.sys

Caused By Address : usbhub.sys+129ec

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ntoskrnl.exe+705c0

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\090511-15709-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7600

Dump File Size    : 345,288

==================================================



==================================================

Dump File         : 090511-16099-01.dmp

Crash Time        : 05/09/2011 17:49:11

Bug Check String  : BUGCODE_USB_DRIVER

Bug Check Code    : 0x000000fe

Parameter 1       : 00000000`00000008

Parameter 2       : 00000000`00000006

Parameter 3       : 00000000`00000005

Parameter 4       : fffffa80`06423160

Caused By Driver  : usbhub.sys

Caused By Address : usbhub.sys+129ec

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ntoskrnl.exe+705c0

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\090511-16099-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7600

Dump File Size    : 345,288

==================================================



==================================================

Dump File         : 090411-26520-01.dmp

Crash Time        : 04/09/2011 16:47:44

Bug Check String  : BUGCODE_USB_DRIVER

Bug Check Code    : 0x000000fe

Parameter 1       : 00000000`00000008

Parameter 2       : 00000000`00000006

Parameter 3       : 00000000`00000005

Parameter 4       : fffffa80`05b79160

Caused By Driver  : usbhub.sys

Caused By Address : usbhub.sys+129ec

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ntoskrnl.exe+705c0

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\090411-26520-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7600

Dump File Size    : 345,280

==================================================





#4 Allan

Allan

  • BC Advisor
  • 8,632 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:23 PM

Posted 19 September 2011 - 08:38 AM

1) After installing Windows did you reinstall all drivers starting with the chipset driver?
2) Please open device manager. Are there any yellow or red symbols? If so, with which device(s) are they associated?
3) You can try this - can't hurt: Open device manager and click the + next to universal serial bus controllers. Then right-click on each one then choose "uninstall". Then reboot and the system will reinstall the drivers.

#5 Nymphs

Nymphs
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:07:23 PM

Posted 19 September 2011 - 08:54 AM

1) After installing Windows did you reinstall all drivers starting with the chipset driver?
2) Please open device manager. Are there any yellow or red symbols? If so, with which device(s) are they associated?
3) You can try this - can't hurt: Open device manager and click the + next to universal serial bus controllers. Then right-click on each one then choose "uninstall". Then reboot and the system will reinstall the drivers.


Apparently all drivers are up to date. I can try #3 if you think it will help.

#6 Allan

Allan

  • BC Advisor
  • 8,632 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:03:23 PM

Posted 19 September 2011 - 09:06 AM

It cannot hurt, but I'd appreciate answers to my questions please

Edited by Allan, 19 September 2011 - 09:07 AM.


#7 Nymphs

Nymphs
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:07:23 PM

Posted 20 September 2011 - 04:57 PM

1) After installing Windows did you reinstall all drivers starting with the chipset driver?
2) Please open device manager. Are there any yellow or red symbols? If so, with which device(s) are they associated?
3) You can try this - can't hurt: Open device manager and click the + next to universal serial bus controllers. Then right-click on each one then choose "uninstall". Then reboot and the system will reinstall the drivers.


1) I installed all the drivers suggested on the DELL website for my laptop: Dell Inspiron 1564, in a non-sequential order.
2) There are none.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users