Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Windows 7 64 bit Complete crash and restart at random


  • Please log in to reply

#1
JP6824

JP6824

    Member

  • Member
  • PipPip
  • 34 posts
My Windows 7 64 bit machine has been crashing completely, seemingly at random, and restarting while I'm online. Tried to run a full Security Essentials scan multiple times, and every time it crashed in the middle of the scan. Was finally able to get a full scan done in safe mode over the weekend, removed two "severe" threats, and everything seemed fine. But again this morning, I got another full crash and restart. I ran diagnostics, which is saying there's a hardware issue and I need to contact the manufacturer, but it doesn't say which hardware has the problem. How can they help me If I don't know what to tell them? Any ideas on how I can figure out where the problem is? Thanks...
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello JP6824.... Welcome to
GeeksToGo, :)
:unsure: :yes:

I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.
  • Please understand we are all volunteers and we are not here all the time.
  • Sometimes it may be a extended amount of time to get back to you. If it has been
    more then 3 days please shoot me a PM and I will try to get back to you quickly
    then.
  • Please do the following and supply the requested information as needed. If you
    don't understand my instructions please ask and I will try to explain them
    clearer for you.
  • Do not attempt any steps unless instructed or ask before to
    make sure they will not cause any further issues.


removed two "severe" threats, and everything seemed fine

What were the threats?

ran diagnostics, which is saying there's a hardware issue and I need to contact the manufacturer, but it doesn't say which hardware has the problem

What diagnostics program did you run?

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.

Thanks to Broni for the instructions and program



Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply







http://www.resplendence.com/downloads




  • Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
  • Double-click VEW.exe
  • Under 'Select log to query', select (as appropriate):
    • Application
    • System
  • Under 'Select type to list', select (as appropriate):
    • Error
    • Information
    • Warning
Then use the 'Date of events' or 'Number of events' as follows:

Either:
  • Click the radio button for 'Number of events'
    Type 3 in the 1 to 20 box (or any number from 1 to 20)
    Then click the Run button.
    Notepad will open with the output log.

  • Click the radio button for 'Date of events'
    In the From: boxes type today's date (presuming the crash happened today) 06 08 2011
    In the To: boxes type today's date (presuming the crash happened today) 07 08 2011
    Then click the Run button.
    Notepad will open with the output log.
Please post the Output log in your next reply
  • 0

#3
JP6824

JP6824

    Member

  • Topic Starter
  • Member
  • PipPip
  • 34 posts
"What were the threats?"

Exploit:Java/CVE-2010-0840.ex
TrojanDownloader:Java/OpenConnection.OI

"What diagnostics program did you run?"
Not sure what it's called, it's apparently part of whatever came with the machine (Windows 7 64bit Studio XPS from Dell). I didn't download it

BSOD Report:
==================================================
Dump File : 080811-19328-01.dmp
Crash Time : 8/8/2011 6:17:32 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`0348b79f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080811-19328-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,280
==================================================

==================================================
Dump File : 080611-18673-01.dmp
Crash Time : 8/6/2011 5:37:10 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c000001d
Parameter 2 : fffff800`035ab3d0
Parameter 3 : fffff880`04f5aab0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080611-18673-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,224
==================================================

==================================================
Dump File : 080511-16754-01.dmp
Crash Time : 8/5/2011 8:05:50 PM
Bug Check String : DRIVER_OVERRAN_STACK_BUFFER
Bug Check Code : 0x000000f7
Parameter 1 : 00000200`01fec838
Parameter 2 : 0000213d`30c0e574
Parameter 3 : ffffdec2`cf3f1a8b
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080511-16754-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,280
==================================================

==================================================
Dump File : 080511-21980-01.dmp
Crash Time : 8/5/2011 6:14:15 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c000001d
Parameter 2 : fffff800`037dfad6
Parameter 3 : fffff880`0a755b60
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080511-21980-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,280
==================================================

==================================================
Dump File : 080511-21262-01.dmp
Crash Time : 8/5/2011 5:54:55 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff800`055366e0
Parameter 2 : 00000000`00000008
Parameter 3 : fffff800`055366e0
Parameter 4 : 00000000`00000002
Caused By Driver : hal.dll
Caused By Address : hal.dll+1344e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080511-21262-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,280
==================================================

==================================================
Dump File : 080511-21699-01.dmp
Crash Time : 8/5/2011 5:26:10 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffffff`ad4c880f
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`0371f757
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080511-21699-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,280
==================================================

==================================================
Dump File : 072211-22604-01.dmp
Crash Time : 7/22/2011 7:56:13 AM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050031
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff800`034a34cb
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072211-22604-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,280
==================================================

==================================================
Dump File : 070911-19141-01.dmp
Crash Time : 7/9/2011 5:48:55 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`0345aae0
Parameter 3 : fffff880`03fc70b0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070911-19141-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,280
==================================================

==================================================
Dump File : 070911-20233-01.dmp
Crash Time : 7/9/2011 5:40:25 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff880`4e4fcca5
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : fffff880`4e4fcca5
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070911-20233-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,280
==================================================

==================================================
Dump File : 070911-20358-01.dmp
Crash Time : 7/9/2011 5:28:31 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff7ff`c36f3020
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`037aeb12
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70700
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16792 (win7_gdr.110408-1633)
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070911-20358-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,280


WhoCrashed
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 8/8/2011 10:16:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080811-19328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000348B79F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 8/8/2011 10:16:19 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x9AAB)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000348B79F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 8/6/2011 9:36:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-18673-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800035AB3D0, 0xFFFFF88004F5AAB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 8/6/2011 12:04:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080511-16754-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0xF7 (0x20001FEC838, 0x213D30C0E574, 0xFFFFDEC2CF3F1A8B, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 8/5/2011 10:12:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080511-21980-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800037DFAD6, 0xFFFFF8800A755B60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 8/5/2011 9:53:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080511-21262-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x50 (0xFFFFF800055366E0, 0x8, 0xFFFFF800055366E0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 8/5/2011 9:24:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080511-21699-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x50 (0xFFFFFFFFAD4C880F, 0x0, 0xFFFFF8000371F757, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 7/22/2011 11:54:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-22604-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800034A34CB)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 7/9/2011 9:47:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070911-19141-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000345AAE0, 0xFFFFF88003FC70B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 7/9/2011 9:39:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070911-20233-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0xD1 (0xFFFFF8804E4FCCA5, 0x2, 0x8, 0xFFFFF8804E4FCCA5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 7/9/2011 9:27:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070911-20358-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x50 (0xFFFFF7FFC36F3020, 0x0, 0xFFFFF800037AEB12, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\080611-20919-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

On your computer a total of 12 crash dumps have been found. Only 11 could be analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually 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.


VEW did not work for some reason. Followed your instructions, but nothing opened in Notepad with either Number or Date of events. It said the file could not be found. Hope what you have here helps. I appreciate your assistance!
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK hold on a few I need to ask about your log. Something looks suspicious with it.

I have a malware tech coming to look at this topic. We both feel you may have a active infection in your system.
Once he decides what to do I can continue but need to have this verified and resolved first.
  • 0

#5
JP6824

JP6824

    Member

  • Topic Starter
  • Member
  • PipPip
  • 34 posts
I was wondering about that, since I keep getting a Java update popup that will not go away. Don't know if it means anything, but I figured I'd mention it. I'll look forward to more, thanks again...
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I suspect that you have some malware on your computer causing issues that we are not able to solve through means we can use here in the Tech Forums. I suggest you read the 'Start Here' topic found HERE. With these self-help tools you have a high chance of fixing the problems on your own. If you are still having problems after following Step 3 of the guide, continue with Step 4 and 5 and post in the Malware Forum. If you are unable to run any programs, Please create a topic stating what you have tried so far and that you are unable to run any programs. Also, Please do NOT post the logs in this thread.

If you are still having issues after the malware expert gives you a clean bill of health, Please return to THIS thread and we will pursue other options to help you solve your current problem(s).
Add a link to this topic so that malware tech can see what steps have been taken here

When you start your topic please put in the description part SweetTech and then send him a pm with a link to your malware topic. Here is his profile where you can send him a private message. We are taking this extra step since I have asked him personally to look at your system for me. Thank you for your cooperation and when he has cleared your system feel free to return here if the issue is still not resolved. Good luck :)
  • 0

#7
JP6824

JP6824

    Member

  • Topic Starter
  • Member
  • PipPip
  • 34 posts
SweetTech was helping me, but now must be busy since I haven't had a response in over 24 hours. Thought I would get back to you with our exchange to this point. Thanks....
  • 0

#8
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
yeah be patient as we are not always here with jobs, families and real life situations. He will get back to you as soon as he logs back in.
  • 0

#9
JP6824

JP6824

    Member

  • Topic Starter
  • Member
  • PipPip
  • 34 posts
I understand. Just thought I would try to find someone who was free. Thanks again...
  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
It's best you stick with your original malware tech as he has seen all your logs and a new tech would have to go through them again taking even more time. You could always send SweetTech a pm and let him know you are ready to continue. It is possible he didn't get a email notification of your last post.
  • 0

Advertisements


#11
JP6824

JP6824

    Member

  • Topic Starter
  • Member
  • PipPip
  • 34 posts
Hello again, just finished up a thread with SweetTech, who has declared my machine free of malware. But the thing is still crashing on me. Twice today. Hope you can be of further assistance. Thanks...
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Yes we have been messaging each other on your flash and it seems you are current on that.
Can you provide me with a WhoCrashed log please.


Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply







http://www.resplendence.com/downloads
  • 0

#13
JP6824

JP6824

    Member

  • Topic Starter
  • Member
  • PipPip
  • 34 posts
Will try to get an update of the suspected driver, as per this report. Please let me know if there's anything else I should do. Thank you again...

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 8/15/2011 6:02:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081511-19297-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88003E72700, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 8/15/2011 6:02:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5F757)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88003E72700, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 8/15/2011 5:02:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081511-20280-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4673)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001440673, 0xFFFFF8800353F978, 0xFFFFF8800353F1E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 8/15/2011 10:27:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081511-18735-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880092F2D60, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 8/12/2011 9:53:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081211-21044-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x7BDD6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800187DDD6, 0xFFFFF8800AD20AA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 8/12/2011 12:00:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081111-19890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x36F057)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF8000377E057, 0xFFFFF88002BCA0D8, 0xFFFFF88002BC9940)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 8/11/2011 11:47:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081111-21309-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034E97FB, 0xFFFFF88009715E80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 8/11/2011 5:10:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081111-20982-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x6B92)
Bugcheck code: 0x50 (0xFFFFF8A0056F0601, 0x1, 0xFFFFF800037CFF98, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 8/11/2011 5:09:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081111-22573-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x4C46A)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009108938, 0xFFFFF880091081A0, 0xFFFFF880014EA689)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. NTFS_FILE_SYSTEM




On Thu 8/11/2011 4:55:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081111-21621-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFFFF93A4D8CE, 0x1, 0xFFFFF800037CFD18, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 8/11/2011 3:55:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081111-21855-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000375FFD8, 0xFFFFF88003514F40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 8/11/2011 3:04:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081111-18891-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0xFFFFEF8080ACD689, 0x2, 0x0, 0xFFFFF88001865196)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 8/10/2011 10:44:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081011-20373-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFC1, 0x1, 0xFFFFF80003BCBD70, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 8/9/2011 7:00:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080911-53976-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFCC, 0x1, 0xFFFFF8000376F419, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 8/9/2011 6:38:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080911-21138-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x50 (0xFFFFFA7FF4DBDA0C, 0x1, 0xFFFFF8000373E958, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\080611-20919-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

On your computer a total of 27 crash dumps have been found. Only 26 could be analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually 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.
  • 0

#14
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Yeah ATI driver may be out of date. If you have the newest we may need to rollback the version to a older one and see if it stops that. Sometimes the newest is not exactly the most stable.

Also could you please do the following.


Tutorial for running chkdsk in Vista\Win 7 located HERE.
  • 0

#15
JP6824

JP6824

    Member

  • Topic Starter
  • Member
  • PipPip
  • 34 posts
Updated the ATI drivers, tried to run chkdsk, but nothing happened when I restarted the machine. And it just crashed again, right after I updated the Adobe reader, and now I'm getting the Adobe update popup again. This is insane. Maybe I should just go get a Mac.
  • 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