Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Bluescreen and broken digital signature


  • Please log in to reply

#1
bingdaddy

bingdaddy

    Member

  • Member
  • PipPip
  • 24 posts
I have a Toshiba Satellite Laptop running Windows Vista, and I have been experiencing alot of random bluescreen errors and restarts lately.

I ran an AVG virus scan and it came back with a "broken digital signature error" citing an Intel Chipset Software Installation Utility.

I further ran WhoCrashed and came up with this report:

Analysis
________________________________________

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 7/12/2010 1:38:39 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xC01846A8, 0x0, 0x0, 0x8208F199)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini071210-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 7/11/2010 6:40:43 AM your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x1A (0x403, 0xC0020290, 0x7367386F, 0xC1020290)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\Mini071110-01.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 7/10/2010 10:56:46 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8223D396, 0xBF01EB6C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini071010-03.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 7/10/2010 10:15:46 PM your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x1000007E (0xC0000005, 0x8C773313, 0x803C4B84, 0x803C4880)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini071010-02.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 7/10/2010 4:04:48 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x50 (0xEB7B641B, 0x0, 0x820398D0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\Mini071010-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 7/9/2010 5:42:14 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0x436B1C8C, 0x2, 0x1, 0x820E1CB8)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini070910-02.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 7/9/2010 2:56:03 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41790, 0xC08020B0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\Mini070910-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 7/7/2010 10:17:44 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xC032DEE8, 0x0, 0x0, 0x82096199)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini070710-02.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 7/7/2010 9:20:13 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\Mini070710-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 7/6/2010 8:33:32 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x30, 0xACAD06C8, 0xA4F8C000, 0xB28E3B66)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\Mini070610-02.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 7/6/2010 6:06:35 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x82206A8D, 0xB6E06944, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini070610-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 7/1/2010 10:38:04 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xFFFF9DC1, 0x0, 0x942FD37B, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\Mini070110-02.dmp
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. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 7/1/2010 5:23:39 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904AA, 0xA7AFC3FC, 0xA7AFC0F8, 0x87C16382)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\Mini070110-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft« Windows« Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 6/30/2010 2:21:04 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8206C2A7, 0xA5FE782C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini063010-01.dmp
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. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.


________________________________________
Conclusion
________________________________________

14 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


Can you tell me where the error truly lies and how I may fix it?
  • 0

Advertisements


#2
Broni

Broni

    Krakˇw my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Please, explain this:

I ran an AVG virus scan and it came back with a "broken digital signature error" citing an Intel Chipset Software Installation Utility.

AVG refused to run with the above error, or....
  • 0

#3
bingdaddy

bingdaddy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 24 posts
AVG completed the scan normally and the log showed one detection, which is the broken digital signature.

I have attached a PDF file that has the list of "WhoCrashed?" errors and on the last page (scroll way down) is a screenshot of the AVG log identifying the broken digital signature.

Could this faulty signature be causing the bluescreen dumps?

Attached Files


  • 0

#4
Broni

Broni

    Krakˇw my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts

Could this faulty signature be causing the bluescreen dumps?

Possible. At first, seeing your errors, I was thinking, RAM issue, but it'd be a good idea to reinstall chipset driver and see, if AVG will report same thing, or not.
Go to Toshiba site, download and install chipset driver (Intel Chipset Software Installation Utility).
  • 0

#5
bingdaddy

bingdaddy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 24 posts
I downloaded the Chipset software and installed, and still am having the same issue.

I ran the AVG scan and WhatCrashed analysis, and they came up with the same error.

I few days ago I ran a Toshiba system diagnostics that came with the laptop and the RAM checked out ok. Do you trust this or is there another test you would like me to try?
  • 0

#6
Broni

Broni

    Krakˇw my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
What kind of RAM test did you run?
If you have more than one RAM stick installed, I'd try to start and run the laptop for a while on one RAM stick at a time and see, if same errors happen.
I'm not sure about that Toshiba test...

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+-....iso.zip file.
3. Inside, you'll find memtest86+-....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+-....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.
  • 0

#7
bingdaddy

bingdaddy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 24 posts
I do have two sticks of RAM. I pulled one early yesterday and have run it for 24 hours without error. I have swapped them and I am now running to see if this stick fails. (I have a feeling that it will)

The two sticks that I have are 1gb each. Would it be ok just to pickup a 2gb stick and replace the bad 1gb? (I don't have the budget right now for two new 2gb sticks) Or, do they both need to be replaced at the same time?
  • 0

#8
Broni

Broni

    Krakˇw my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Let's see, what will happen with 2nd stick.
2GB of RAM is perfectly enough for Vista.
...and, as you can see, from troubleshooting point of view, it's always better to have 2x1GB sticks, than just one 2GB stick.
  • 0

#9
bingdaddy

bingdaddy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 24 posts
Actually, I was thinking about just picking up one 2GB stick and adding it to the one good 1GB stick for a total of 3GB. Will that work?

I have not had a chance to run this 2nd stick through the paces, just yet. I'll get you an update soon.
  • 0

#10
Broni

Broni

    Krakˇw my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts

I was thinking about just picking up one 2GB stick and adding it to the one good 1GB stick for a total of 3GB. Will that work?

Sure thing. As long, as you have 2 sticks, that's good for troubleshooting.
  • 0

#11
bingdaddy

bingdaddy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 24 posts
I have run the system with just one stick of RAM at a time with no errors. Then I tried running each stick, separately in different slots, with no errors.

So, I put both sticks back in and the machine ran just fine for 48 hours! I thought it was back to normal, but this morning it has failed on me three times already!

Any other thoughts or ideas?

The latest error log and WhoCrashed log is this:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 94519F1E
BCP3: 8A2838BC
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini072210-01.dmp
C:\Users\Jeff\AppData\Local\Temp\WER-140120-0.sysdata.xml
C:\Users\Jeff\AppData\Local\Temp\WERCC53.tmp.version.txt

Read our privacy statement:
http://go.microsoft....63&clcid=0x0409



WhoCrashed Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 7/22/2010 3:19:48 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x94519F1E, 0x8A2838BC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini072210-01.dmp
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. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
  • 0

#12
Broni

Broni

    Krakˇw my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
I suggest that you start a new topic in the Malware Removal and Spyware Removal area.

Before you start a new topic click on this link --> Malware and Spyware Cleaning Guide, Please read before starting a new topic. This will give you a few preparations to make, as well as instruction for posting your OTListIt2 log.

If you are still having problems after being given a clean bill of health from the malware expert, then please return to THIS thread and we will pursue other options to help you solve your current problem(s).
  • 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