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, need help!


  • Please log in to reply
6 replies to this topic

#1 asdd

asdd

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:04:21 PM

Posted 20 May 2012 - 11:28 AM

i have been having some bsod's lately, i had four total since i started playing d3 last week, 2 of them i think i fixed by updating my video card and usb 3.0, but one of them happened again last night
the dump files are attached
i asked this over at the seven forums, and the person helping me insists its my kaspersky, which im sure it is not because i have kaspersky av installed on all my computers without a hitch.

and here are the codes i got from bluescreenview:
ntoskrnl.exe is one of them

dxgmms1.sys is another

asmtxhci.sys

then i get the same ntoskrnl.exe again yesterday

i also ran whocrashed and this is what i got:

On Sun 5/20/2012 6:38:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-15397-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0xC050000, 0xFFFFFA800C948010)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 5/18/2012 4:16:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-16161-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x21100)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004A21100, 0xFFFFF88006DFD698, 0xFFFFF88006DFCEF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 5/16/2012 11:56:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051612-16177-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800019A468, 0x9F6000016F97C867, 0xFFFFF6800C19A468)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 5/9/2012 3:48:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-13665-01.dmp
This was probably caused by the following module: asmtxhci.sys (asmtxhci+0x1E28A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800431A28A, 0xFFFFF88002DB69D8, 0xFFFFF88002DB6230)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\asmtxhci.sys
product: ASMedia USB 3.0 Host Drivers
company: ASMedia Technology Inc
description: ASMEDIA XHCI Host Controller Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: asmtxhci.sys (ASMEDIA XHCI Host Controller Driver, ASMedia Technology Inc).
Google query: asmtxhci.sys ASMedia Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M


like i said i updated the usb3.0, which i think fixed the last one, and i updated some old drivers for the other ones, but the latest one says its a driver issue, so no idea

Attached Files


Edited by asdd, 20 May 2012 - 11:52 AM.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

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

Posted 20 May 2012 - 11:57 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 asdd

asdd
  • Topic Starter

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:04:21 PM

Posted 20 May 2012 - 12:49 PM

==================================================
Dump File : 052012-16582-01.dmp
Crash Time : 5/20/2012 1:34:07 PM
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`000000f6
Parameter 2 : 53535353`00000140
Parameter 3 : fffffa80`0d025060
Parameter 4 : fffff880`06bf0eb8
Caused By Driver : Lycosa.sys
Caused By Address : Lycosa.sys+1eb8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052012-16582-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,328
==================================================

==================================================
Dump File : 052012-16005-01.dmp
Crash Time : 5/20/2012 1:12:05 PM
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`000000f6
Parameter 2 : 01010101`0000013c
Parameter 3 : fffffa80`0cf6d6f0
Parameter 4 : fffff880`07fb0eb8
Caused By Driver : Lycosa.sys
Caused By Address : Lycosa.sys+1eb8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052012-16005-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,384
==================================================

==================================================
Dump File : 052012-22994-01.dmp
Crash Time : 5/20/2012 1:10:18 PM
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`000000f6
Parameter 2 : a9a9a9a9`00000140
Parameter 3 : fffffa80`0cf9f650
Parameter 4 : fffff880`07f95eb8
Caused By Driver : Lycosa.sys
Caused By Address : Lycosa.sys+1eb8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052012-22994-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,384
==================================================

==================================================
Dump File : 052012-21434-01.dmp
Crash Time : 5/20/2012 1:07:07 PM
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`000000f6
Parameter 2 : b3b3b3b3`0000013c
Parameter 3 : fffffa80`0cf16b30
Parameter 4 : fffff880`07fb0eb8
Caused By Driver : Lycosa.sys
Caused By Address : Lycosa.sys+1eb8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052012-21434-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 288,256
==================================================

==================================================
Dump File : 052012-15397-01.dmp
Crash Time : 5/20/2012 2:39:36 AM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`0c050000
Parameter 4 : fffffa80`0c948010
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052012-15397-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,384
==================================================

==================================================
Dump File : 051812-16161-01.dmp
Crash Time : 5/18/2012 12:17:53 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`04a21100
Parameter 3 : fffff880`06dfd698
Parameter 4 : fffff880`06dfcef0
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+1e803
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : dxgmms1.sys+21100
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051812-16161-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,416
==================================================

==================================================
Dump File : 051612-16177-01.dmp
Crash Time : 5/16/2012 7:57:10 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00000403
Parameter 2 : fffff680`0019a468
Parameter 3 : 9f600001`6f97c867
Parameter 4 : fffff680`0c19a468
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051612-16177-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 308,768
==================================================

==================================================
Dump File : 050812-13665-01.dmp
Crash Time : 5/8/2012 11:49:48 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`0431a28a
Parameter 3 : fffff880`02db69d8
Parameter 4 : fffff880`02db6230
Caused By Driver : asmtxhci.sys
Caused By Address : asmtxhci.sys+47754
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : asmtxhci.sys+1e28a
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050812-13665-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 275,792
==================================================



i was just running driver verifier to see what drivers are faulty and it told me that the lycosa driver is causing problems so i deleted it. when i try to reinstall, i get another bsod, what can i do with my driver?
also, i did the sfc /scannow and it came back with no errors

#4 Allan

Allan

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

Posted 20 May 2012 - 02:11 PM

http://www.sevenforums.com/crashes-debugging/89384-blue-screen.html

#5 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:21 AM

Posted 20 May 2012 - 09:56 PM

Lycosa.sys Wed Sep 08 13:01:26 2010


Razer Tarantula Keyboard Driver ... http://www.razersupport.com

Edited by AustrAlien, 20 May 2012 - 09:56 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#6 asdd

asdd
  • Topic Starter

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:04:21 PM

Posted 20 May 2012 - 10:12 PM

So what do i update it to, the may 2011 that they have? Also how can i check to make sure the driver updated after i install it

#7 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:21 AM

Posted 21 May 2012 - 02:27 AM

So what do i update it to, the may 2011 that they have?

Yes, it appears that the May 2011 update is the latest available.

... how can i check to make sure the driver updated after i install it

I suppose there are a couple of ways, looking at the details (and making a note of them!) before updating, and then again after updating.
  • Check out the date/version of the file Lycosa.sys.
  • Go to Device Manager > Keyboard and check out the version of the keyboard driver.
The other way, would be to see if it fixed the BSOD problem (run Driver Verifier again ... but do not forget to turn it off when you have finished with it!). If the system no longer BSODs under DV, I guess it would be safe to assume that the driver was updated satisfactorily.

Edited by AustrAlien, 21 May 2012 - 02:28 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users