Home > Bsod > BSOD - Probably Caused By Ntkrpamp.exe

BSOD - Probably Caused By Ntkrpamp.exe

So far (the crashes are random and often irregular, so I'm not 100% sure), I have not had the BSOD on a clean install before installing the Windows Updates, which makes Login now. The ex owner did the upgrade. I'm unsure about the Creative drivers - and they've been a real PITA for a long time. check over here

The BSODs were happening before I installed the Creative Audio drivers - do you still want me to remove them? This cannot be protected by try-except, it must be protected by a Probe. With the Creative drivers, I've seen several problems with them over the last couple of years - so I feel it's reasonable to attempt to replace them "just in case" they Please help... try here

Is the Driver Verifier running every time I start Windows now? 02-15-2012, 06:18 PM #15 usasma TSF Team EmeritusMicrosoft MVP Join Date: Apr 2009 Location: Southeastern CT, To rule out a driver 1. Why not 2008 R2?was wondering this as well. 0 Anaheim OP mcbenton71 Jul 2, 2014 at 2:29 UTC That was my second suspicion after I determined it wasn't Select last option - "Select driver names from a list" 5.

Cheers, Charlie 02-17-2012, 03:12 PM #18 usasma TSF Team EmeritusMicrosoft MVP Join Date: Apr 2009 Location: Southeastern CT, USA Posts: 7,483 OS: Win7 I think it's just Click on the Provider heading - sorts list by Provider 6. Late for doctor's appt right now.... Thanks for your help, it saved me a reinstall.

It's known to crash with the following bugcheck. f77ec5a8 804ef163 85a96020 85cb3008 85cb3008 eamon+0x3be1 f77ec5b8 80581fe2 863b14f0 85bb10f4 f77ec750 nt!IopfCallDriver+0x31 f77ec698 805bdf06 863b1508 00000000 85bb1050 nt!IopParseDevice+0xa12 f77ec710 805ba58e 00000000 f77ec750 00000040 nt!ObpLookupObjectName+0x53c f77ec764 80574f33 00000000 00000000 00000000 nt!ObOpenObjectByName+0xea f77ec7e0 Arg4: 0d500417, (reserved) Debugging Details: ------------------ GetUlongFromAddress: unable to read from 80564cb0 BUGCHECK_STR: 0x19_20 POOL_ADDRESS: e2bc736a CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from 8054a583 to 804f9f13 STACK_TEXT: 9a4a8cc0 8054a583 00000019 00000020 Microsoft Audit Inventorying 480 PCs, 50 Physical and 25 virtual servers for Microsoft licensed products.

BSOD = that's not the problem, and we'll have to remove something else. __________________ John Carrona, Microsoft MVP - Windows Expert - Consumer Driver Reference Table ` ` BSOD Index I think next I'm going to run memtest86+. Join our site today to ask your question. Join the community Back I agree Test your smarts. 88% of IT pros got this right.

  1. if you change it to something smaller, 2-4GB for a page file, you could free up more memory and the BSOD events could stop happening. 0 Anaheim OP
  2. TechSpot is a registered trademark.
  3. Arguments: Arg1: 00000020, a pool block header size is corrupt.
  4. Arg4: 00000000, (reserved) Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 8217d874 Unable to read MiSystemVaType memory at 8215d420 9c3dbad8 FAULTING_IP: nt!CmpCheckKey+61b 821c22bf 394724 cmp dword ptr [edi+24h],eax MM_INTERNAL_CODE: 0
  5. Why not 2008 R2? 0 Pure Capsaicin OP Helpful Post Little Green Man Jul 2, 2014 at 2:25 UTC Eric1929 wrote: I could be wrong, and please forgive
  6. Advertisement yankees8223 Thread Starter Joined: Sep 12, 2008 Messages: 15 Hello.

Style Default Style Contact Us Help Home Top RSS Terms and Rules Copyright © TechGuy, Inc. second thing to try: please run www.memtest86.comand see that you have faulty ram or not. 3 or 4 passes without error will clear your RAM of any wrongdoing. All rights reserved. Password Site Map Posting Help Register Rules Today's Posts Search Site Map Home Forum Rules Members List Contact Us Community Links Pictures & Albums Members List Search Forums Show Threads

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump More info on dump file options here: Overview of memory dump file check my blog GET STARTED Question has a verified solution. BugCheck 10000050, {daddb0a8, 0, 805badb7, 0} Could not read faulting driver name Probably caused by : ntkrpamp.exe ( nt!ObpCloseHandleTableEntry+13 ) Followup: MachineOwner --------- 1: kd> !analyze -v ERROR: FindPlugIns 8007007b ******************************************************************************* BSODs have been occuring since installing Windows 7, the system was fine two months ago using Vista, although not used as frequently as in the last two months.

Cheers, Charlie 02-15-2012, 04:26 PM #12 usasma TSF Team EmeritusMicrosoft MVP Join Date: Apr 2009 Location: Southeastern CT, USA Posts: 7,483 OS: Win7 Quote: They are the Thread Status: Not open for further replies. Cheers, Charlie K Attached Files Windows7_Vista-jcgriff2.zip (515.4 KB, 480 views) 02-11-2012, 01:30 PM #5 usasma TSF Team EmeritusMicrosoft MVP Join Date: Apr 2009 Location: Southeastern CT, USA this content Also, out of curiosity, if the server is relatively new, why was the decision made to use 2008 Enterprise 32 bit?

I have no idea how to go about fixing this or whether its software or hardware related. so the recommendation is again, to update your drivers, and also update the NOD software if possible. Also, on booting it seems to hang for 30 sec or so after I input my password.

Check ALL boxes where "Microsoft" IS NOT the Provider 7.

Join the community of 500,000 technology professionals and ask your questions. That way there's a higher likelyhood that the installer will replace those drivers (and, presumably, fix the problem) Another option is a backup, wipe, and "clean install" of Windows. All Rights Reserved. Any assistance much appreciated.

so it's best to take some preventive actions so that we can avoid such issues or overcome such problems more easily. Hi, I have repeated BSODs on a clean install of Windows 7 (32 BIT) with all Windows Updates (but nothing Thread Tools Search this Thread 02-03-2012, 07:17 PM #1 Short URL to this thread: https://techguy.org/970968 Log in with Facebook Log in with Twitter Log in with Google Your name or email address: Do you already have an account? have a peek at these guys I don't need it in there for the time being.

After about 30 sec, I get the arrow w/ hour glass then it boots to windows just fine.