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

BSODs on a relatively new computer


  • Please log in to reply
5 replies to this topic

#1 noxzhu

noxzhu

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:08:19 PM

Posted 26 January 2012 - 06:59 PM

Two of the crashes are at ntoskrnl.exe+7cc10 and one at ntoskrnl.exe+7cc40.
Operating system: Windows 7 64-bit.

If there's anything you need to know, ask away and I'll try to get back to you asap! Quite anxious since this computer is relatively new :(.

Edit: The first listed crash (with tcpip) may have something to do with me doing a few regedits (installing message queueing, adding D-Word TCPNoDelay with value 1 to msmq/parameters, adding D-Word TCPAckFrequency with value 1 to tcpip; basically the generic guide for disabling the nagle algorithm)

Dump files:

==================================================
Dump File : 012612-30466-01.dmp
Crash Time : 1/26/2012 2:56:52 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa80`0f19e000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`01688067
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+78067
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012612-30466-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 011712-22261-01.dmp
Crash Time : 1/17/2012 4:17:13 PM
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+7cc10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011712-22261-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 011712-16021-01.dmp
Crash Time : 1/17/2012 3:08:21 PM
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+7cc10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011712-16021-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

Edited by noxzhu, 26 January 2012 - 07:03 PM.


BC AdBot (Login to Remove)

 


#2 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:19 PM

Posted 27 January 2012 - 02:13 AM

Since its a user's fault on registry changes, might as well set your system back by a complete reinstallation.

Tekken
 


#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,541 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:19 PM

Posted 27 January 2012 - 03:03 PM

The simple answer...if your system presented no problems prior to your edits...simply reverse them.

Louis

#4 noxzhu

noxzhu
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:08:19 PM

Posted 27 January 2012 - 08:00 PM

Only the first listed BSOD followed the system regedits, if this comes up again I'll reverse any changes, but I'm still worried about what happened in the first two.

Edited by noxzhu, 27 January 2012 - 08:04 PM.


#5 hamluis

hamluis

    Moderator


  • Moderator
  • 56,541 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:19 PM

Posted 28 January 2012 - 09:30 AM

Well...your last two don't point in any given direction.

http://en.wikipedia.org/wiki/Windows_NT_kernel

Ntoskrnl.exe and ntkrnlpa.exe...are core Windows processes. When these are seen in error messages, just substitute "scene of the crime" rather than those two items. I'm no expert at this, but I have seen a lot of BSODs reported on these forums...IMO, messages pointing to these two processes just indicate the point at which whatever went wrong...became noticed by Windows. No definitive data.

Malware items may often be involved in such errors, IMO.

When I combine these reflections with your registry edits...it's hard to guess just where the problem might lie.

The only apparent conclusion I can offer...whatever is wrong is something that can be traced within a 10-day timeframe.

Louis

#6 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:19 PM

Posted 28 January 2012 - 02:14 PM

Hi

Typically, I see Nagling disabled on the program level as opposed to system wide unless you are using this Win7 box as a server that handles lots of small packets. Is there a specific program where Nagling is a problem? If so, check if it has a built in option for disabling Nagling. I've done some game development and it is standard practice for online multiplayer games to disable Nagling automatically.

James




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users