Windows 7 is crashing...i don't know what to do anymore

zigzag3143 said:

Ant

from microsoft?

yes, it's the RTM version.

Can't find anything conclusive on ntkrpamp.exe which is what the bug check says is the most likely cause.

From what I have read this could be your anti virus program causing this type of problem or possibly bad ram or an incompatable driver is being used.

491e000 94925700 st330 Wed Oct 26 10:19:47 2005 (435F9083)
94926000 94929f00 lpwdm Wed Oct 26 10:19:46 2005 (435F9082)
9492a000 9492d180 stbus Wed Oct 26 10:19:47 2005 (435F9083)
9492e000 94937d80 steth Mon Oct 24 07:28:12 2005 (435CC54C)

the first 2 drivers are certainly from my USB modem that i have to connect to the internet (probably the rest of the drivers that are dated 2005 are also used by the USB modem).

luckily in couple of days i'll change my IPS so i'll uninstall the USB modem. how i'll be sure that i've uninstalled all the drivers because in the device manager i only have 1 device listed the speedtouch 330. if i uninstall this will remove automatically the rest of the drivers?

chev65 said:

Can't find anything conclusive on ntkrpamp.exe which is what the bug check says is the most likely cause.

From what I have read this could be your anti virus program causing this type of problem or possibly bad ram or an incompatable driver is being used.

the antivirus i use is nod32 smart security.i didn't have any problem with win xp ( my previous OS) so if it was the ram i should have problems in win xp too, and i didn't had. hope it's the driver problem.

chev65 said:

Can't find anything conclusive on ntkrpamp.exe which is what the bug check says is the most likely cause.

From what I have read this could be your anti virus program causing this type of problem or possibly bad ram or an incompatable driver is being used.

ntkrpamp is otherwise known as "Windows".

Here is what else I came up with on that error.

0x50 - Probable Cause "ntkrpamp.exe" - Normally caused by Defective Memory (L2 Cache, RAM, Video RAM) or Incompatible Software including Anti-Virus software.

0x1A - Probable Cause "ntkrpamp.exe" - Very similar error to 0x50 - The Minidump indicates a process called "SBCSSvc.exe" which is associated with something called CounterSpy i think from a Google search.


True it's a Windows system file.

ntkrpamp.exe is a process associated with Microsoft Windows Operating System from Microsoft Corporation. This process is required for essential applications to work properly and ntkrpamp.exe should not be disabled.

Still the fact that this file is associated with a bugcheck indicates that it may be caused by the reasons I already listed.

chev65 said:

ntkrpamp.exe is a process associated with Microsoft Windows Operating System from Microsoft Corporation. This process is required for essential applications to work properly and ntkrpamp.exe should not be disabled.

It's the kernel itself mate... NT KeRnel PAE Multi-Processor

"Disabling" it will indeed make it difficult for "essential applications to work properly"

On a more serious note, at least half of all BSODs occur in the ntoskrnl/ntkrnlmp/ntkrpamp module - it's the one which does the vast majority of the work. However, only in a vanishingly small percentage of cases is that module actually responsible for the crash. It simply gets fed bad data and it chokes.

@ANT: Please consider updating your drivers as Zigzag said. Your crashes are caused by something in the network stack, either the NIC driver or something that's latched itself into that path - antivirus, 3rd-party firewall... that sort of thing.

Here's a somewhat reconstructed version of the stack from the same minidump. Note the NDIS.sys reference... networking.

0: kd> kL = 8078ad8c 8078ad8c 0
ChildEBP RetAddr
WARNING: Frame IP not in any known module. Following frames may be wrong.
8078ad88 82949e00 0x0
8078adb0 828f7245 nt!WmipDoFindRegEntryByDevice+0x2b
8078adcc 88488495 nt!KiDispatchException+0x7f
8078ade0 884edbc1 ndis!ndisDereferenceDriver+0x1b
8078ae08 828a404d ndis!ndisMTimerDpcX+0xe4
8078ae4c 828a3ff1 nt!KiProcessTimerDpcTable+0x50
8078af38 8287dfca nt!KiProcessExpiredTimerList+0x101
00000000 00000000 nt!Kei386EoiHelper+0x192

H2SO4 said:

chev65 said:

ntkrpamp.exe is a process associated with Microsoft Windows Operating System from Microsoft Corporation. This process is required for essential applications to work properly and ntkrpamp.exe should not be disabled.

It's the kernel itself mate... NT KeRnel PAE Multi-Processor

"Disabling" it will indeed make it difficult for "essential applications to work properly"

On a more serious note, at least half of all BSODs occur in the ntoskrnl/ntkrnlmp/ntkrpamp module - it's the one which does the vast majority of the work. However, only in a vanishingly small percentage of cases is that module actually responsible for the crash. It simply gets fed bad data and it chokes.

Which is exactly why I said it was inconclusive. Dismantling my responce isn't helping with the problem mate.

I already mentioned twice that it appeared to be related to a driver or anti virus problem. Have a good one.

chev65 said:

Which is exactly why I said it was inconclusive. Dismantling my responce isn't helping with the problem mate.

I already mentioned twice that it appeared to be related to a driver or anti virus problem. Have a good one.

Don't be upset please. I'm not "dismantling your response". I wanted to explain why research into ntkrpamp was unnecessary.

yes guys no need to fight now :)

your answers helped me a lot. hope the driver update or remove of the hardware itself will solve my problems.

thank you very much for the help.