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 with USB STICK STORAGE


  • Please log in to reply
8 replies to this topic

#1 0_shark_0

0_shark_0

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Local time:08:59 AM

Posted 31 January 2014 - 07:58 PM

Hello,

 

My system crash when I plug an USB Stick storage. I tried different Ports and Sticks, always crash.

 

Please find below analysis of whocrashed and my config

 

http://speccy.piriform.com/results/JdaCfBuZYmWVa88MYpBwJgw

 

System Information (local)

computer name: HICHAM-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Latitude E6520, Dell Inc., 0T5KFM
CPU: GenuineIntel Intel® Core™ i7-2720QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8465170432 total
VM: 2147352576, free: 1917427712

 

 

 

 

 

Crash Dump Analysis

 

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 31/01/2014 23:51:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013114-19500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4A (0x771E180A, 0x2, 0x0, 0xFFFFF8800BBAAB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 31/01/2014 23:51:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4A (0x771E180A, 0x2, 0x0, 0xFFFFF8800BBAAB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 31/01/2014 23:39:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013114-30607-01.dmp
This was probably caused by the following module: gddcd64.sys (gddcd64+0x205C)
Bugcheck code: 0xC9 (0x24D, 0xFFFFF880055A205C, 0xFFFFF9801287E440, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\gddcd64.sys
product: G Data Security Software
company: G Data Software AG
description: G Data Device Control DevFilter Driver
Bug check description: This is the bug check code for all Driver Verifier
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: gddcd64.sys (G Data Device Control DevFilter Driver, G Data Software AG).
Google query: G Data Software AG DRIVER_VERIFIER_IOMANAGER_VIOLATION



On Fri 31/01/2014 21:26:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013114-24991-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4A (0x77CA180A, 0x2, 0x0, 0xFFFFF8800686EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 31/01/2014 20:59:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013114-26005-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4A (0x77A5180A, 0x2, 0x0, 0xFFFFF8800AF01B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 31/01/2014 20:52:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013114-27393-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4A (0x7769180A, 0x2, 0x0, 0xFFFFF8800BB4EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 26/10/2013 21:41:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102613-26707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003313500, 0xFFFF, 0x0)
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 that cannot be identified at this time.

 

 


Edited by 0_shark_0, 31 January 2014 - 08:04 PM.


BC AdBot (Login to Remove)

 


#2 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:06:59 PM

Posted 31 January 2014 - 08:40 PM

please attach 2 .dmp file for analysis.

 

meanwhile reinstall/ uninstall/ update gData.



#3 0_shark_0

0_shark_0
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Local time:08:59 AM

Posted 31 January 2014 - 08:51 PM

Thanks for the reply

 

here's the link for the dump files

 

http://cjoint.com/?3BbcW24qzJ8

 

http://cjoint.com/?DBbcYSCU25G

 

I'll reinstall Gdata

 

 



#4 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:06:59 PM

Posted 31 January 2014 - 09:23 PM

I can't download those files, they just render into html...

 

please zip them, hit the 'more reply options' bottom right of your reply editor (next to the post button) and attach.



#5 0_shark_0

0_shark_0
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Local time:08:59 AM

Posted 31 January 2014 - 10:04 PM

Hi

 

It's done



#6 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:06:59 PM

Posted 31 January 2014 - 11:09 PM

before we go on... does the problem still occur?



#7 0_shark_0

0_shark_0
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Local time:08:59 AM

Posted 01 February 2014 - 06:55 AM

Hello

 

After uninstalling G-DATA completely and installing Kaspersky the problem disappear.

 

I thinks the BSOD was caused by G-DATA.

 

Now i tried the usb's stick on different port, and no crash.

 

What do you think, G-DATA caused this.

 

Thanks a lot 



#8 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:06:59 PM

Posted 01 February 2014 - 07:15 PM

It's not uncommon for antivirus products to cause this issue...

 

Happy your machine works again :busy:



#9 0_shark_0

0_shark_0
  • Topic Starter

  • Members
  • 70 posts
  • OFFLINE
  •  
  • Local time:08:59 AM

Posted 01 February 2014 - 07:30 PM

Thanks a lot for your help.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users