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

Crashing Computer


  • Please log in to reply
66 replies to this topic

#1 InDreams

InDreams

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:07:45 PM

Posted 05 June 2012 - 12:21 AM

Computer Error Screen

Custonm built desktop computer purchased December, 2007 formerly running Windows XP Professional and recently upgraded (??) to Windows 7 Professional new install has been crashing on a regular basis for months, especially when video is playing, even more especially when video is playing full screen. However, it also crashes fairly regularly w/o any video playing and for no apparent reason.

Usually there is a BSOD with white writing on it for a split second before the screen goes dark and the computer then reboots automatically. When it first boots and when it reboots, a box with the following message always appeared when using Windows XP Professional:

smax4pnp.exe – Entry Point Not Found
The procedure entry point GetOpMode could not be located in the dynamic link library SMWDMIF.dll

That message no longer appears under Windows 7 Professional.

One time in the process of crashing, the blue screen with white writing “froze” and I was able to copy what was on the screen:

A problem has been detected and Windows has been shut down to prevent damage to your computer.

IRQL_NOT_Less_OR_Equal

If this is the first time you’ve seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this sis a new installation, ask your hardware or software manufacturer for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software, disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup options, and then select Safe Mode.

Technical information:

***STOP: 0x0000000A
(0x00000000, 0x000000FF, 0x00000000, 0x806E5EAO)

End of Screen Image

Here is an excerpt of a very recent Crash Dump Analysis

System Information (local)

computer name: KIM-PC-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon™ 64 X2 Dual Core Processor 6000+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3756515328 total
VM: 2147352576, free: 1961705472


Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 5/22/2012 9:04:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052212-27643-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415EB)
Bugcheck code: 0xD1 (0x1D, 0xFF, 0x1, 0xFFFFFFFF847225A1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Tue 5/22/2012 9:04:36 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvstor.sys (nvstor+0x100A7)
Bugcheck code: 0xD1 (0x1D, 0xFF, 0x1, 0xFFFFFFFF847225A1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvstor.sys
product: NVIDIA nForce™ SATA Driver
company: NVIDIA Corporation
description: NVIDIA® nForce™ Sata Performance Driver
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.
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: nvstor.sys (NVIDIA® nForce™ Sata Performance Driver, NVIDIA Corporation).
Google query: nvstor.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Thu 5/17/2012 10:18:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051712-30669-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Thu 5/17/2012 4:09:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051712-33275-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Wed 5/16/2012 7:54:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051612-33821-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Wed 5/16/2012 5:18:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051612-109809-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Wed 5/16/2012 4:46:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051612-36613-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4165B)
Bugcheck code: 0xA (0xF18, 0x2, 0x0, 0xFFFFFFFF82B4A035)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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.



I upgraded from Windows XP Professional to Windows 7 Professional in the hopes that doing so would take care of the problem. It apparently did not. Any thoughts on what might be causing the problems described above and how to eliminate them would be much appreciated.

thanks,

InDreams

BC AdBot (Login to Remove)

 


#2 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:45 PM

Posted 05 June 2012 - 12:24 AM

Link to previous topic in MRL forum with gringo_pr: http://www.bleepingcomputer.com/forums/topic454547.html

Let's collect some more information: I'll have a look at it and help you try to resolve the problem.

:step1: Please follow the instructions: BSOD Posting Instructions: Windows 7 - Vista

(Note: When you run BSOD_Windows7_Vista_v2.64_jcgriff2_.exe, it will also run autoruns.exe ... and both need to be in the same location!)
... with one exception in the following line:
  • "4. Zip up the entire output folder + PERFMON and attach the zip file to your next post."
The BC forums will allow a total attachment size of only 512 kb (and what you need to attach will exceed this limit). Please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file. I will have a look at the contained information and see if I can shed some light on your BSOD issue.

See the suggestions in the following links for recommendations on file sharing websites:
  • http://lifehacker.com/388284/best-online-file-sharing-services
  • http://www.hongkiat.com/blog/15-great-free-online-file-sharing-alternatives/
  • http://www.smashingapps.com/2008/08/28/5-best-free-file-hosting-services-to-store-your-files.html

:step2: Please Publish a Snapshot using Speccy, and post a link to it in this thread.
  • It is a convenient and accurate way of providing us with details of your computer specifications.

:step3: Please download MiniToolBox, save it to your desktop and run it.
  • Checkmark the following checkboxes:
    • List Installed Programs
  • Click Go.
    When the scan is finished, a text file will open in a Notepad window.
  • Copy the entire contents of the Notepad window, and paste in your reply.
    (Result.txt will be saved in the same directory the tool is run.)

Edited by AustrAlien, 05 June 2012 - 12:25 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#3 InDreams

InDreams
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:07:45 PM

Posted 05 June 2012 - 01:02 AM

my computer is very much in a crashing frame of mind, so I will get on this right awaye, between crashes

btw -- my computer automatically boots to http://www.searchnu.com/406 when I start it -- I think that started after I had installed Windows 7 Professional -- I have no idea why it boots there

more soon,I hope...

#4 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:45 PM

Posted 05 June 2012 - 02:00 AM

Received via PM:

MiniToolBox by Farbar Version: 04-06-2012
Ran by KIM-PC (administrator) on 04-06-2012 at 23:45:39
Microsoft Windows 7 Professional Service Pack 1 (X86)
Boot Mode: Normal
***************************************************************************

=========================== Installed Programs ============================

Adobe Flash Player 11 ActiveX (Version: 11.2.202.235)
Adobe Reader X (10.1.3) (Version: 10.1.3)
AVG 2012 (Version: 12.0.2176)
AVG 2012 (Version: 12.0.2425)
AVG 2012 (Version: 2012.0.2176)
CPUID HWMonitor 1.17
Definition Update for Microsoft Office 2010 (KB982726) 32-Bit Edition
Google Chrome (Version: 19.0.1084.52)
Google Drive (Version: 1.1.3019.542)
Google Update Helper (Version: 1.3.21.111)
HP Product Detection (Version: 11.14.0001)
iLivid (Version: 1.92)
Microsoft .NET Framework 4 Client Profile (Version: 4.0.30319)
Microsoft Office 2010 Service Pack 1 (SP1)
Microsoft Office Access MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Access Setup Metadata MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Excel MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Home and Business 2010 (Version: 14.0.6029.1000)
Microsoft Office OneNote MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Outlook MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office PowerPoint MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Proof (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Proof (French) 2010 (Version: 14.0.6029.1000)
Microsoft Office Proof (Spanish) 2010 (Version: 14.0.6029.1000)
Microsoft Office Proofing (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Publisher MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Shared MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Shared Setup Metadata MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Office Single Image 2010 (Version: 14.0.6029.1000)
Microsoft Office Word MUI (English) 2010 (Version: 14.0.6029.1000)
Microsoft Silverlight (Version: 5.1.10411.0)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148 (Version: 9.0.30729.4148)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 (Version: 9.0.30729.6161)
Mozilla Firefox 12.0 (x86 en-US) (Version: 12.0)
Mozilla Maintenance Service (Version: 12.0)
Searchqu Toolbar (Version: 4.1.0.2685)
Speccy (Version: 1.16)
TeamViewer 5 (Version: 5.1.10408 )
Time and Chaos
Update for Microsoft .NET Framework 4 Client Profile (KB2468871) (Version: 1)
Update for Microsoft .NET Framework 4 Client Profile (KB2533523) (Version: 1)
Update for Microsoft .NET Framework 4 Client Profile (KB2600217) (Version: 1)
Update for Microsoft Office 2010 (KB2553065)
Update for Microsoft Office 2010 (KB2553181) 32-Bit Edition
Update for Microsoft Office 2010 (KB2553267) 32-Bit Edition
Update for Microsoft Office 2010 (KB2553270) 32-Bit Edition
Update for Microsoft Office 2010 (KB2553310) 32-Bit Edition
Update for Microsoft Office 2010 (KB2553385) 32-Bit Edition
Update for Microsoft Office 2010 (KB2566458)
Update for Microsoft Office 2010 (KB2596964) 32-Bit Edition
Update for Microsoft Office 2010 (KB2597091) 32-Bit Edition
Update for Microsoft OneNote 2010 (KB2553290) 32-Bit Edition
Update for Microsoft OneNote 2010 (KB2589345) 32-Bit Edition
Update for Microsoft Outlook 2010 (KB2553248) 32-Bit Edition
Update for Microsoft Outlook Social Connector 2010 (KB2553406) 32-Bit Edition
WhoCrashed 3.04

**** End of log ****
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#5 InDreams

InDreams
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:07:45 PM

Posted 26 June 2012 - 01:37 AM

Hi,

I'm back from a trip and my computer is still crashing every few minuted or so.

Here is the most recent Crash dump Analysis:

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 6/26/2012 6:17:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-27050-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4165B)
Bugcheck code: 0xD1 (0x28000000, 0xFF, 0x1, 0xFFFFFFFF87CC4D21)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Tue 6/26/2012 6:17:42 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!HalReturnToFirmware+0x469)
Bugcheck code: 0xD1 (0x28000000, 0xFF, 0x1, 0xFFFFFFFF87CC4D21)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
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: hal.sys .
Google query: hal.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Tue 6/26/2012 5:10:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-32604-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Tue 6/26/2012 1:31:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-44538-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4165B)
Bugcheck code: 0xD1 (0x20FFD080, 0xFF, 0x8, 0x20FFD080)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Tue 6/26/2012 12:43:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-29452-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4165B)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0xFFFFFFFF85C5D0E8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Tue 6/26/2012 12:04:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-50169-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x41D9B)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntkrnlpa.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 Mon 6/25/2012 11:46:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-49717-01.dmp
This was probably caused by the following module: amdk8.sys (amdk8+0x1BB6)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF828BA043, 0xFFFFFFFF82966B1D, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\amdk8.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device 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 6/25/2012 10:19:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-37050-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)
Bugcheck code: 0x50 (0xFFFFFFFF965C7000, 0x1, 0xFFFFFFFF8284F853, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Mon 6/25/2012 6:27:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-28750-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Mon 6/25/2012 6:01:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-47642-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Thu 6/7/2012 4:12:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-20919-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Thu 6/7/2012 4:00:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-30950-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xF8A39)
Bugcheck code: 0xD1 (0x290F5C00, 0xA, 0x8, 0x290F5C00)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 185.93
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 185.93
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 185.93 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Thu 6/7/2012 3:42:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-49483-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Thu 6/7/2012 3:09:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-91322-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




On Thu 6/7/2012 2:18:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-27612-01.dmp
This was probably caused by the following module: hal.sys (hal+0x331A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP




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



Conclusion
On your computer a total of 51 crash dumps have been found. Only 50 could be analyzed. Only 15 are included in this report. 2 third party drivers have 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 185.93 , NVIDIA Corporation)

hal.sys

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.

Before I left I think you said I should check the RAM. How do I do that?

Many thanks for your help,

InDreams

#6 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:45 PM

Posted 26 June 2012 - 04:39 AM

btw -- my computer automatically boots to http://www.searchnu.com/406 when I start it -- I think that started after I had installed Windows 7 Professional -- I have no idea why it boots there

Gringo will take care of that when we have resolved the BSOD issue.

Edit: The report generated by Who Crashed and that of BlueScreenView (which you may have seen being used on the forums) is often of little use in analysing crash dumps and the actual minidump files are necessary to extract the most information from a crash dump. The minidump files are collected by the jcgriff2 application, so I would really like you to run that and provide me with the output. Failing that, a small number of minidumps would be a good start.

Are you able to complete Step :step1: in my first post, and get me the information collected by the jcgriff2 application? If so, please do that.

If you are not able to do the above, then please zip up and attach some of the recent minidumps to your reply so I can have a closer look:
  • Navigate to C:\Windows\Minidump <<< folder
  • Click on the most recent minidump file.
  • Hold down the <Ctrl> key, and click on the 6 next-most recent minidump files to also select them.
  • Release the <Ctrl> key.
  • Now, right-click on one of the selected files > Send to ... > Compressed (zipped) Folder.
    The zip file will be located in the same place (the Minidump folder).
  • Attach the zip file to your next reply.
    When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message.

We need to thoroughly test the memory (RAM) in your system. The BSOD problem has seemed to persist from the original XP installation, through to the clean installation of Windows 7, indicating a likely persistent hardware problem. RAM is the most likely suspect, so we should test and eliminate that as a fist step. I realise that you have attempted to test the RAM on a previous occasion, but from what I recall that testing was not sufficient to be conclusive to any degree at all. I ask that you run memtest86+ for at least the full 24 hours ... unless you see an error before the 24 hours is up, in which case stop the test immediately.

Test the memory (RAM).

Memory needs to be tested outside of Windows, so memtest86+ is run from a bootable CD.

:step1: To make a bootable CD with memtest86+:
  • Extract the downloaded zip file:
    • Right-click on the zip file and choose Extract all. (Windows XP ... other Windows versions may have different wording.)
      The contents of the zip file (the .ISO image file) will be extracted to a folder in the same location as your zip file.
  • Burn the .ISO image to CD: If you do not already have a suitable burning program for writing .ISO images to disc ...
    • Download and install ImgBurn.
    • Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
    • Place a new (blank) CD disc in the drive tray.
    • Choose Write image file to disc.
    • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
    • Place a check-mark in the box beside Verify.
  • Click Posted Image
  • When the CD has been burned and verified as successful, it will be bootable.

:step2: Boot from the newly created CD.
  • You may need to configure BIOS or the Boot Menu to boot first from the CD.
  • memtest86+ will begin running automatically: You need do nothing else at this time.
  • Allow memtest86+ to run un-interrupted.
See the screenshots in this informative link: Diagnose with Memtest86+

There MUST be NO errors what-so-ever:
  • If you see an error, stop the test.
  • Then proceed to test each stick of RAM separately to sort the good from the bad.
A minimum test for some confidence in the result, should be 7 full passes (each "pass" is a series of different types of tests), with NO errors.
  • Allow memtest86+ to run for 24 hours for maximum confidence in the test result.
memtest86+ will continue running until you stop it:
  • Press the <ESCAPE> key to re-boot the computer, removing the memtest86+ CD.
Reference: Overclockers forums Memtest86+ Guide/How To's
http://www.overclockers.com/forums/showthread.php?t=409152

BTW: I have become quite ill over the past few weeks and I may have trouble continuing to assist with your problem. If that is the case I will request that another staff member continue to assist in my absence. In the meantime, I will continue to do what I can for you.

Edited by AustrAlien, 26 June 2012 - 04:49 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#7 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:03:45 AM

Posted 26 June 2012 - 04:50 AM

I would recommend that the Malware Team take a closer look at this this issue, because the BSOD's could be result of what changed the search engine to searchnu.com there could be some malware on the machine such as a rootkit, but I will let AustrAlien analyze the BSOD's.

#8 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:45 PM

Posted 26 June 2012 - 04:59 AM

@ cryptodan: This topic has history that you are probably not aware of.

The topic has just been wrested from the grasp of gringo_pr in the MRL forum, who did check it for malware .... even though it was essentially a clean installation of Win7. Obviously the system was not entirely "clean" ... but it is "close enough" to clean, so as not to be a suspect in the BSOD issue, which apparently carries over from the previous XP installation (although we can't be 100% certain it is the same issue).
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#9 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:03:45 AM

Posted 26 June 2012 - 06:37 PM

Can you link me to the malware topic, because I checked the users topic history and saw no reference to the malware topic.

#10 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:45 PM

Posted 26 June 2012 - 07:00 PM

Can you link me to the malware topic, because I checked the users topic history and saw no reference to the malware topic.

Sure, it is there no problem:

Computer Crashing
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#11 InDreams

InDreams
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:07:45 PM

Posted 30 June 2012 - 10:25 AM

I'm trying to run BSOD_Windows7_Vista_v2.64_jcgriff2_.exe, which I have downloaded. It is now "hiding" behind the ribbon at the bottom of my screen.

How do I remove the ribbon so I can run BSOD_Windows7_Vista_v2.64_jcgriff2_.exe?

Many thanks

#12 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:45 PM

Posted 30 June 2012 - 11:51 AM

It sounds as though you have downloaded the file(s) to your Desktop?

From the linked instructions:

1. Download these 2 files; save to Documents
· A. SysInternals AutoRuns - Microsoft TechNet
· B. jcgriff2 BSOD File Collection app


Are you able to download them directly to your Documents folder?
  • If not, then you need to move both files to the Documents folder before you actually run the jcgriff2 application.

Re: hiding behind the Taskbar (ribbon)
Perhaps the easiest way to actually find and grab the file(s) to move it would be to open/use Windows Explorer and go to the Desktop folder that way:
  • Desktop = C:\Users\<username>\Desktop
  • Documents = C:\Users\<username>\Documents

Edited by AustrAlien, 30 June 2012 - 11:53 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#13 InDreams

InDreams
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:07:45 PM

Posted 30 June 2012 - 12:53 PM

I have downloaded the results of the jcgriff2 scan. It's a zip file containing 3,184K of data. Can I just email the zip file to you? It's too large to attach to a response.

Thanks

#14 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:45 PM

Posted 30 June 2012 - 12:58 PM

Yes, the zip file will be too large to attach to a post at BleepingComputer.com:

The BC forums will allow a total attachment size of only 512 kb (and what you need to attach will exceed this limit). Please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file. I will have a look at the contained information and see if I can shed some light on your BSOD issue.

See the suggestions in the following links for recommendations on file sharing websites:

  • http://lifehacker.com/388284/best-online-file-sharing-services
  • http://www.hongkiat.com/blog/15-great-free-online-file-sharing-alternatives/
  • http://www.smashingapps.com/2008/08/28/5-best-free-file-hosting-services-to-store-your-files.html

Using a file sharing site is not all that difficult. Skydrive is popular these days and works well. Box is another I would recommend.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#15 InDreams

InDreams
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:07:45 PM

Posted 30 June 2012 - 01:29 PM

here is the link

<a href=http://www.filedropper.com/windows7vistajcgriff2><img src=http://www.filedropper.com/download_button.png width=127 height=145 border=0/></a><br /><div style=font-size:9px;font-family:Arial, Helvetica, sans-serif;width:127px;font-color:#44a854;> <a href=http://www.filedropper.com >file storage</a></div>




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users