Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Get tired of BSOD


  • Please log in to reply

#1
D_HooK

D_HooK

    New Member

  • Member
  • Pip
  • 8 posts
hi everybody i'm here to ask for help because i'm going to kill my computer :)
so my problem is that i recently format my computer because a lot of bsod
after installing windows and some softwares,i started to install call of duty 4 but i had a blue screen :s. i reboot but again during the install of cod a blue screen appears :s
here is the whocrashed report:

On Sat 14/03/2009 21:30:20 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x90000B0, 0x2, 0x1, 0x805178BA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 14/03/2009 15:04:20 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x780, 0xC034BF08, 0x815D1150, 0xFCC2BCDA)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 14/03/2009 14:57:36 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x780, 0xC0343F08, 0x81829858, 0xF1D4E4CC)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.


so please if someone can help me because i think that i will have more problems :s :s :s
(sorry but i don't speak english very well !!)
  • 0

Advertisements


#2
D_HooK

D_HooK

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
news:

On Sun 15/03/2009 10:35:44 your computer crashed
This was likely caused by the following module: ipnat.sys
Bugcheck code: 0x100000D1 (0x10FF1120, 0x2, 0x0, 0xB5D7F6CF)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ipnat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IP Network Address Translator
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

i desinstalled the pilot of my ethernet card and everything goes right so i think that the problem comes from there
  • 0

#3
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
You may have RAM problem.
Run memtest: http://www.techspot....topic62524.html
  • 0

#4
D_HooK

D_HooK

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
everything is fine i check with memtest,ccleaner...i have updated the ethernet card's pilot and i have no more problems until now :)
  • 0

#5
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Did you try to run your machine with one RAM stick at a time?
  • 0

#6
D_HooK

D_HooK

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
no not yet but the computer works fine now i don't know if there was a probem with the pilot of the ethernet card or other thing
  • 0

#7
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Hmmm....another computer miracle self-fix?....lol
  • 0

#8
D_HooK

D_HooK

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
i was dreaming i think :s 3 more bsod today :

On Mon 16/03/2009 18:21:56 your computer crashed
This was likely caused by the following module: ftdisk.sys
Bugcheck code: 0x10000050 (0xB5944518, 0x1, 0xE2B4DCCA, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ftdisk.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FT Disk Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 16/03/2009 18:20:42 your computer crashed
This was likely caused by the following module: rtnicxp.sys
Bugcheck code: 0x100000D1 (0x40000800, 0x2, 0x0, 0x40000800)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\rtnicxp.sys
product: Realtek 10/100/1000 NIC Family all in one NDIS Driver
company: Realtek Semiconductor Corporation
description: Realtek 10/100/1000 NDIS 5.1 Driver



On Mon 16/03/2009 17:39:57 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000000A (0x7E042FE8, 0x2, 0x1, 0x804E7FE0)
Error: Unknown
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

i don't know how to locate the problem,i don't think that it comes from the ram because i just bought them

Edited by D_HooK, 16 March 2009 - 02:12 PM.

  • 0

#9
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

Again, at least two of them indicate RAM problem (including Ram on your motherboard, L2 cache and video card RAM).
Did you try to run your machine with one RAM stick at a time?
Do you have separate video card, or on-board video?
Are you sure, your computer is clean of malware?
  • 0

#10
D_HooK

D_HooK

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
my video card is seperated,i run a full scan everyday for malwares and use kaspersky for anti-virus.
well i guess im gonna work with one ram stick for a moment to be sure that the problem don't comes from that
  • 0

#11
D_HooK

D_HooK

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
On Tue 17/03/2009 19:46:26 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8056D729, 0xB5BDC84C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 17/03/2009 19:39:16 your computer crashed
This was likely caused by the following module: sptd.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x804E5CDD, 0xB5688A88, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\sptd.sys



On Tue 17/03/2009 19:07:35 your computer crashed
This was likely caused by the following module: pciidex.sys
Bugcheck code: 0x100000C5 (0x0, 0x2, 0x1, 0x80551AE2)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\pciidex.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: PCI IDE Bus Driver Extension
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 17/03/2009 08:57:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xB597C9F8, 0xB597C9F8, 0xC002B8A)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

:s :s :s
  • 0

#12
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Do you use Daemon Tools?
If so, try to uninstall it for the moment. See, if the problem persist.

If yes, remove video card, and to run the computer with on-board video, for a while.
  • 0

#13
D_HooK

D_HooK

    New Member

  • Topic Starter
  • Member
  • Pip
  • 8 posts
i use alcohol not deamon tools.
so i guess im going to try first using one ram stick then i will remove the video card
  • 0

#14
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Just make sure, you try one solution at a time.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP