BSOD all from ntkrpamp.exe!!

deutschnaftula

New Member
Reaction score
0
i am working on a computer it's an optiplex 320 with windows XP pro
I have been getting BSOD for about 2 weeks like every 2’ day and all of them or pointing to NTKRPAMP.EXE (which is a windows component)

what I have done so far

Check’t the computer for viruses but found nothing (avira,combofix,gmer,)

Tested memory with memtest86+ found no errors.

Tested hard drive with WD lifeguard but found nothing
.
A full 3 hour check with “PC Check” but again nothing.

So please if you can help me with this I would really appreciate as this is a business computer.
Here is the minidumps



thay look like this.


Probably caused by : ntkrpamp.exe ( nt!IopProcessWorkItem+0 )

STACK_TEXT:
f1349d34 804fcd80 00000096 864fae78 8056485c nt!KeBugCheckEx+0x1b
f1349d74 8053877a 00000001 f1349d01 f1349d94 nt!KeRemoveQueue+0x314
f1349dac 805cff62 864fae78 00000000 00000000 nt!ExpWorkerThread+0xcc
f1349ddc 8054612e 805386ae 80000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 

Attachments

  • Minidump.zip
    131.3 KB · Views: 403
xp pro sp3
2 sticks of memory, 512+512
integrated video

i have also uninstalled sp3 and then reinstalled it but it's not getting better,
 
The driver listed as "probably caused by" is an NT Kernel component and in no way is responsible.

To rule out a driver
1. Create a Windows System Restore Point

2. Run the Driver Verifier

Click "START" then "RUN" | type verifier | make these selections

1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -
• Special Pool
• Pool Tracking
• Force IRQL checking
• Deadlock Detection
• Security Checks (Windows 7)
• Miscellaneous Checks
4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
8. Re-boot
*** IMPORTANT - PLEASE READ:

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

- After re-start, you may not be able to log on to normal Windows
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1

- For Driver Verifier status - type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump, zip it up & attach to your next post
 
update

just as a update

the culprit was "K9 Web Protection"

i was also at another costmer who complaind about slow internet and BSOD.......uninstalled K9 and no problems anymore

thank you.
 
Back
Top