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

Recent Computer Quirks


  • Please log in to reply
38 replies to this topic

#1 djrobbva

djrobbva

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Virginia
  • Local time:01:35 PM

Posted 24 January 2010 - 08:48 PM

Hello to all just wanted to describe some issues that im having with my presario 6000. Last week started getting the bsod with 0x0000007a or 0x0000004f. Now the new BSOD is 0x000007b. Have run combofix, spybot and malware bytes. NO program finds any problems. I do remember seeing something on the blue screen about win32k.sys, when I search for this file i look to have about 50 or so some dating back to 2001 and as recent as 2009. When I boot the computer with last known good config it will load up fine. If I try to load in safe mode it will not load. Any help with resolving this issue would be greatly appreciated. Thanks in Advanced...... :thumbsup:

BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:10:35 AM

Posted 24 January 2010 - 08:57 PM

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#3 djrobbva

djrobbva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Virginia
  • Local time:01:35 PM

Posted 24 January 2010 - 09:33 PM

Dump File : Mini012110-01.dmp
Crash Time : 1/21/2010 6:41:00 AM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 0x00000003
Parameter 2 : 0x86e12d78
Parameter 3 : 0x86e12eec
Parameter 4 : 0x8060567e
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6067a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini012110-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini012010-02.dmp
Crash Time : 1/20/2010 8:34:02 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xe1f6ed2c
Parameter 2 : 0xc000000e
Parameter 3 : 0xbf91d424
Parameter 4 : 0x301ce860
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+11d424
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5863 (xpsp_sp3_gdr.090814-1258)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini012010-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini012010-01.dmp
Crash Time : 1/20/2010 5:57:53 AM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 0x00000003
Parameter 2 : 0x86d12da0
Parameter 3 : 0x86d12f14
Parameter 4 : 0x8060567e
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6067a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini012010-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini011810-02.dmp
Crash Time : 1/18/2010 8:24:58 PM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0xc000000e
Parameter 2 : 0xc000000e
Parameter 3 : 0x00000000
Parameter 4 : 0x02272000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6067a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini011810-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini011810-01.dmp
Crash Time : 1/18/2010 8:57:24 AM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 0x00000003
Parameter 2 : 0x86dd6da0
Parameter 3 : 0x86dd6f14
Parameter 4 : 0x8060567e
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6067a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini011810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini011610-02.dmp
Crash Time : 1/16/2010 4:00:19 PM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0xc000000e
Parameter 2 : 0xc000000e
Parameter 3 : 0x00000000
Parameter 4 : 0x0095b000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6067a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini011610-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini011610-01.dmp
Crash Time : 1/16/2010 8:04:25 AM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0xc000000e
Parameter 2 : 0xc000000e
Parameter 3 : 0x00000000
Parameter 4 : 0x0054a000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6067a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini011610-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini011510-01.dmp
Crash Time : 1/15/2010 9:54:37 AM
Bug Check String : KERNEL_STACK_INPAGE_ERROR
Bug Check Code : 0x00000077
Parameter 1 : 0xc000000e
Parameter 2 : 0xc000000e
Parameter 3 : 0x00000000
Parameter 4 : 0x00980000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6067a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5857 (xpsp_sp3_gdr.090804-1435)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini011510-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini081307-01.dmp
Crash Time : 8/13/2007 4:50:14 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc03dde68
Parameter 2 : 0xc000000e
Parameter 3 : 0xf779a642
Parameter 4 : 0x22c78860
Caused By Driver : ftdisk.sys
Caused By Address : ftdisk.sys+a642
File Description : FT Disk Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.0 (XPClient.010817-1148)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini081307-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini111806-01.dmp
Crash Time : 11/18/2006 8:39:37 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x000000e8
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x806ffa16
Caused By Driver : hal.dll
Caused By Address : hal.dll+2a16
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini111806-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini091306-01.dmp
Crash Time : 9/13/2006 7:25:48 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x000000e8
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x806ffa16
Caused By Driver : hal.dll
Caused By Address : hal.dll+2a16
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini091306-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================



Here is my BSOD.txt as you requested. I believe I have done this properly

#4 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:10:35 AM

Posted 24 January 2010 - 09:38 PM

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#5 djrobbva

djrobbva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Virginia
  • Local time:01:35 PM

Posted 24 January 2010 - 10:22 PM

Have tried to boot with one stick of ram each time. Both sticks resulted in the same thing. still getting the bsod 0x0000007b screen.

#6 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:10:35 AM

Posted 24 January 2010 - 10:28 PM

Do you have on-board video, or separate video card?

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#7 djrobbva

djrobbva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Virginia
  • Local time:01:35 PM

Posted 25 January 2010 - 08:44 AM

Thanx Broni for your help so far. Im not sure about the video. Funny you mention this because i do consistently get a message on start up that "nwiz.exe as encountered blah blay..." I have tried to find drivers to resolve this issue but no luck. I seem to think though that my ram stix may be bad. Since ram is cheap thinking about getting new ones just to eliminate this as the possible problem. I also have not run memtest yet because another issue im having is that larger downloads freeze about halfway through. This is a real pain.... :thumbsup:

Edited by djrobbva, 25 January 2010 - 08:44 AM.


#8 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:10:35 AM

Posted 25 January 2010 - 11:42 AM

If manual check (running the computer on one RAM stick at a time) is giving you same BSODs, there is no reason to run memtest.

I asked about video card, because those errors could be caused also by video card RAM.

You can tell, if you have on-board video, or separate video card by looking at the back of your computer.
If the monitor is connected somewhere in Area 1, you have on-board video.
If the monitor is connected somewhere in Area 2, you have real video card.

Posted Image

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#9 djrobbva

djrobbva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Virginia
  • Local time:01:35 PM

Posted 25 January 2010 - 09:04 PM

Broni I do have on board video. Do you think that my nwiz.exe error i get at start up may be the culprit.

#10 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:10:35 AM

Posted 25 January 2010 - 09:18 PM

You didn't say anything about nwiz.exe error before.
Reinstalling video driver would a good next step.
Keep in mind, that your video chip may be actually going bad.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#11 djrobbva

djrobbva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Virginia
  • Local time:01:35 PM

Posted 26 January 2010 - 08:35 AM

I have been unsuccesfull in finding the drivers for the onboard video. When I go to Nvidia Im told that no update is needed. Do you know of a link that I may be able to use to reinstall the drivers that are necessary. If the video chip is going bad, does this constitute a new motherboard or can you replace just the video chip. Once again I want to thank you for taking your time to help me out with these current issues. Up to now the PC is still functioning but I usually must boot up with last known good config. I have tried to load up in Safe mode, but it will get hung up on the Admin, loading personal settings page.

#12 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:10:35 AM

Posted 26 January 2010 - 11:53 AM

If the video chip is going bad, does this constitute a new motherboard or can you replace just the video chip

If that's the case, you can simply buy real video card, which will replace on-board video, but...
...let's try to reinstall driver first.
There are many models of presario 6000: http://h20180.www2.hp.com/apps/Lookup?h_la...p;submit=Go+%BB
Which one is yours?

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#13 rosiesdad

rosiesdad

  • Members
  • 220 posts
  • OFFLINE
  •  
  • Local time:01:35 PM

Posted 26 January 2010 - 01:36 PM

Upon google, of nwiz.exe I found this

http://www.file.net/process/nwiz.exe.html

Also in same google, "Important: Some malware camouflage themselves as nwiz.exe, particularly if they are located in c:\windows or c:\windows\system32 folder. Thus check the nwiz.exe process on your pc whether it is pest. We recommend Security Task Manager for verifying your computer's security. It is one of the Top Download Picks of 2005 of The Washington Post and PC World. "

So include malware scans just in case.

Edited by rosiesdad, 26 January 2010 - 01:38 PM.


#14 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:05:35 PM

Posted 26 January 2010 - 03:41 PM

Download Driver Sweeper from here: http://www.guru3d.com/category/driversweeper/ and remove your nVidia drivers and reinstall fresh from here: www.nvidia.com. I would also make sure your chipset drivers are updated along with your USB ones as well. My wife's computer did this till I updated the chipset drivers and flashed the BIOS to a recent one.

#15 djrobbva

djrobbva
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Virginia
  • Local time:01:35 PM

Posted 26 January 2010 - 08:55 PM

Updated the nvidia drivers nwiz.exe error is now gone. upon restart i did get bsod kernel data inpage error, 0x0000007a, also makes note of a file win32k.sys. I have seen this error before could this file be an area of investigation? Seem to be making some progress as i have noticed pc performance is getting better. :thumbsup:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users