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 0x0000001e Help?


  • Please log in to reply
6 replies to this topic

#1 syhn

syhn

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:12 PM

Posted 23 June 2010 - 05:02 AM

Hey guys,

So until recently my computer has been experiencing a BSoD error that occured when I started playing Gunbound again (ref. Softnyx.com). I thought it was a game incompatibility but then I remembered that I just got the same BSoD just a few days before I actually installed it. I don't exactly remember why I got the BSoD in the first place, but I believe that it has something to do with a game going full screen (as I'm currently triple-screening with DisplayFusion). So I'm here wondering if anybody can analyze my dump file and tell me what's up.

[codebox]
Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`03098e50
Debug session time: Wed Jun 23 02:29:30.367 2010 (UTC - 7:00)
System Uptime: 0 days 2:02:45.255
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for dadder.sys
Probably caused by : dadder.sys ( dadder+712 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+3436643837326361
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002ec4c2e to fffff80002ecced0

STACK_TEXT:
fffff800`00b9bc98 fffff800`02ec4c2e : 00000000`00000000 00000000`00000000 fffff800`00b9c4a0 fffff800`02ef9e28 : nt!KeBugCheck
fffff800`00b9bca0 fffff800`02ef2bed : fffff800`030d9c24 fffff800`03012a3c fffff800`02e5b000 fffff800`00b9c400 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bcd0 fffff800`02efa250 : fffff800`0301ab5c fffff800`00b9bd48 fffff800`00b9c400 fffff800`02e5b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9bd00 fffff800`02efb82e : fffff800`00b9c400 fffff800`00b9c4a0 00000000`00000001 00000000`00000002 : nt!RtlDispatchException+0x410
fffff800`00b9c3e0 fffff800`02f297c2 : fffffa80`0643a000 00000000`00000000 00000000`00000000 fffff800`02e156e5 : nt!RtlRaiseStatus+0x4e
fffff800`00b9c980 fffff880`04498712 : fffffa80`082daef0 fffff800`00000000 00000000`00000008 fffff800`02e14300 : nt! ?? ::FNODOBFM::`string'+0xf63c
fffff800`00b9ca00 fffff800`02ecf516 : fffffa80`065c2a5b fffff800`02e16c77 fffffa80`06431930 00000000`00000000 : dadder+0x712
fffff800`00b9ca40 fffff880`040135d9 : fffffa80`0609f050 fffffa80`05d59b00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff800`00b9cb20 fffff880`04013ab7 : fffffa80`075cac02 fffffa80`065c28b0 00000000`ffffffff fffffa80`0609fea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`00b9cc00 fffff880`0401164f : fffffa80`0609fea8 fffffa80`0609f1a0 fffffa80`060a0040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00b9cc60 fffff880`04002f89 : fffffa80`0609f050 00000000`00000000 fffffa80`0609fe02 fffffa80`0609fea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00b9cca0 fffff800`02ed85dc : fffff800`03045e80 fffffa80`0609fea8 fffffa80`0609fec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9ccd0 fffff800`02ed56fa : fffff800`03045e80 fffff800`03053c40 00000000`00000000 fffff880`04002db0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
dadder+712
fffff880`04498712 8a0558170000 mov al,byte ptr [dadder+0x1e70 (fffff880`04499e70)]

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: dadder+712

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dadder

IMAGE_NAME: dadder.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b28a020

FAILURE_BUCKET_ID: X64_0x1E_0_dadder+712

BUCKET_ID: X64_0x1E_0_dadder+712

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

[/codebox]

Computer Specs:
Windows 7 Ultimate 64-bit
Nvidia GeForce 9500GT + 8500GT
Intel Core 2 Quad Q6600 2.40GHz clocked at 3.02GHz
4GB Memory
Asus P5K-E WiFi/AP

And just as a follow-up on what I know about computers, I did a basic manual scan to check if I had anything that was out of the blue, updated/deleted drivers and checked if all my hardware was working correctly.

Thanks in advance for any help,
Syhn

Edited by syhn, 23 June 2010 - 05:03 AM.


BC AdBot (Login to Remove)

 


#2 doctorphibes

doctorphibes

  • Members
  • 81 posts
  • OFFLINE
  •  
  • Local time:09:12 PM

Posted 24 June 2010 - 10:54 AM

Hi,
Are you using a release candidate version of 7? Was this your first boot in the dual boot mode?
If you can boot into safe mode, try Last known good config first. If that doesn't work you might try this (assuming you can boot into safe mode):

First of all, remove all unnecessary hardware devices from the computer, try entering Windows safe mode to test whether it is a third-party software/hardware incompatibility issue. If the issue is caused by the driver updates, you might go to Device Manager, right click your hardware device in the list and select Properties; then click Driver tab and click Roll Back Driver button. In addition, you might download and run Windows 7 Upgrade Advisor to check the reason for the issue.


If you still get the BSOD error while booting the computer, please understand that Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services).



The system goes to a blue screen because there is some exception(s) happening in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some error(s) occur in the kernel, it will kill the box to prevent more severe damage happening. Then we get a blue screen or the system reboots (it depends on what the system settings are).



To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what you can do in a forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

Hope it helps,
doc

Edited by doctorphibes, 24 June 2010 - 10:59 AM.

“I am enough of the artist to draw freely upon my imagination. Imagination is more important than knowledge. Knowledge is limited. Imagination encircles the world.” Albert Einstein

#3 coxchris

coxchris

  • Members
  • 1,151 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Atwater
  • Local time:06:12 PM

Posted 24 June 2010 - 11:16 AM

See if this helps



Download Blue Screen Viewer (http://www.nirsoft.net/utils/bluescreenview.zip)
extract the zip file
run the program
when it done scanning
go to file>saved selected items it will save them in a txt file and copy and paste all the information in your next post.
It will put the same information into a list by the affected system file that causing the bsod

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 


#4 syhn

syhn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:12 PM

Posted 25 June 2010 - 03:53 AM

Thanks for the reply guys.

Anyhow, in response to the first post: I'm running the final retail version of Windows 7. I'm able to do everything normally, windows side (booting, browsing, typical computer operations, etc.) The only thing I have trouble with is that whenever I execute a certain game that forces me to play in full screen mode (which is also disabling my Desktop Manager functions/Transparent Aero Windows enabling) I get the BSoD. So far, this applies to GunBound Season 2 and sometimes Steam games if I had it run on full screen mode (but only sometimes, like every other day).

As for my Dual-boot, I do have a dual-boot screen that starts up, but my other boot isn't functional nor can I completely remove it or format it because I have files I use on the drive containing the second boot. The second boot was previously a Windows Vista boot, but it got corrupted somehow and I just left it there. I don't plan on doing anything about it until I get a new hard Drive and transfer my important files over.

Second post: I'm not sure if I got the right info saved but this is it:
[codebox]==================================================
Dump File : 062310-52494-01.dmp
Crash Time : 6/23/2010 2:32:18 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71ed0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\062310-52494-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
[/codebox]

Again, thanks guys.

#5 syhn

syhn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:12 PM

Posted 26 June 2010 - 03:37 AM

A small update: I've had a friend who had some experience with diagnosing computers and looking into things and he mentioned that it could be my mouse driver. I don't really see how a mouse can be causing my BSoD but can anybody confirm? My mouse is a Razor DeathAdder 1800dpi. He said that it could be something that has to do with a dadder.sys file that was also mentioned in the crash dump.

#6 doctorphibes

doctorphibes

  • Members
  • 81 posts
  • OFFLINE
  •  
  • Local time:09:12 PM

Posted 26 June 2010 - 07:42 AM

I mentioned the same thing in one of my other posts about this same problem a couple of days ago (a different post about the same problem < view : #1815583, if you look under all my posts it should be the one before this one). The post was just a rant about how wide spread this problem really is and the many claims that people say they've used to solve it. switching out a wireless mouse for a PS2, uninstalling Bit Defender, etc. Maybe if someone that has both can look into the them and see if they have a common file like the one you just mentioned. When you think about it, it's really not that far of a stretch. Especially in the context of Windows glitches. Are any of you using wireless keyboard/mouse + Bit Defender set ups? I switched my wireless mouse out for a USB long ago, but for reasons of functionality. I used BD 2009 but wasn't very impressed with 2010 so I switched to another suite. Come to think of it, I was using BD 2009 when I switched the mouse out. So before people summarily dismiss the notion it might merit some looking into dumps from both to see if they have a common file, driver,etc. Ya just never know what you'll see lookin' out a Window.
Good luck all.

Edited by doctorphibes, 26 June 2010 - 07:46 AM.

“I am enough of the artist to draw freely upon my imagination. Imagination is more important than knowledge. Knowledge is limited. Imagination encircles the world.” Albert Einstein

#7 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:01:12 AM

Posted 27 June 2010 - 09:11 AM

Is it just that one BSOD? If so then its nothing to work about. However, I would recommend making sure all your drivers and software are updated.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users