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

BSOD


  • Please log in to reply
7 replies to this topic

#1 jamesw

jamesw

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:01:54 PM

Posted 14 December 2012 - 05:14 PM

BSOD,keyboard and mouse freeze.

BC AdBot (Login to Remove)

 


#2 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:04:54 PM

Posted 14 December 2012 - 05:27 PM

What is the make and model number of your computer?
  • If a laptop, look at the label on the bottom.
What was "new" just before the BSODs started (i.e. new hardware, software, malware, error messages)?

Is this problem intermittent or constant?

Are you able to boot into normal Windows?

Regards,
Brooks



 


#3 jamesw

jamesw
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:01:54 PM

Posted 14 December 2012 - 05:33 PM

custom built,this problem has been going on for a few months but seems to be getting worse.I can boot to windows but it takes 3 reboots before the computer is stable.I am posting from the computer now

#4 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:04:54 PM

Posted 14 December 2012 - 05:43 PM

Hello

These problems are often not simple so gathering as much information about your computer will be important.

1. ) Please download the following two files to your Documents folder.
2. ) Navigate to your Documents folder.
  • Right click on BSOD_Windows7_Vista_v2.64_jcgriff2_.exe and select, Run as administrator.
  • This will run autoruns as well and will create a new folder, Windows7_Vista_jcgriff2, within your Documents.
3. ) Run a System Health Report
  • Click START -> type perfmon /report , then click perfmon /report at top of column. .
  • After data collection, click File -> save as perfmon.html in your newly created "Documents\Windows7_Vista_jcgriff2" folder.
4. ) Zip up the Windows7_Vista_jcgriff2 folder.
  • Right click on the folder and select Send to --> Compressed (zipped) folder.
5. ) Please upload the zipped folder to a File Sharing website of your choosing because Bleeping Computer has a 512 K only upload limit and this file will be much larger.

In addition:

To help us get a better look at your computer's hardware, please download and install Speccy by Piriform. (mirror site)
  • During installation, uncheck "Install the free Google Toolbar along with Speccy."
  • Run Speccy and from the top menu, select File --> Publish Snapshot. Click "Yes" to proceed.
  • Click, Copy to Clipboard and paste this address into your next post.

Regards,
Brooks



 


#5 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:54 PM

Posted 14 December 2012 - 05:43 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#6 jamesw

jamesw
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:01:54 PM

Posted 14 December 2012 - 05:50 PM

==================================================
Dump File : 121412-33734-01.dmp
Crash Time : 12/14/2012 1:56:44 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00041287
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5ed45
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : 32-bit
Crash Address : ntoskrnl.exe+5ed45
Stack Address 1 : ntoskrnl.exe+38a68
Stack Address 2 : ntoskrnl.exe+721a6
Stack Address 3 : ntoskrnl.exe+24eed
Computer Name :
Full Path : F:\Windows\Minidump\121412-33734-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 151,440
==================================================

==================================================
Dump File : 120612-33718-01.dmp
Crash Time : 12/6/2012 10:04:03 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00005003
Parameter 2 : 0x88000000
Parameter 3 : 0x00000687
Parameter 4 : 0x00689d2e
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+d2490
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : 32-bit
Crash Address : ntoskrnl.exe+d2490
Stack Address 1 : ntoskrnl.exe+76422
Stack Address 2 : ntoskrnl.exe+6d77c
Stack Address 3 : ntoskrnl.exe+6204b
Computer Name :
Full Path : F:\Windows\Minidump\120612-33718-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 149,192
==================================================

==================================================
Dump File : 120612-31000-01.dmp
Crash Time : 12/6/2012 9:58:53 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x00008062
Parameter 2 : 0x00000005
Parameter 3 : 0x00000000
Parameter 4 : 0x90442272
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+2c272
File Description : NVIDIA Windows Kernel Mode Driver, Version 290.36
Product Name : NVIDIA Windows Kernel Mode Driver, Version 290.36
Company : NVIDIA Corporation
File Version : 8.17.12.9036
Processor : 32-bit
Crash Address : ntoskrnl.exe+38c5b
Stack Address 1 : nvlddmkm.sys+2c272
Stack Address 2 : dxgkrnl.sys+1b14
Stack Address 3 : dxgkrnl.sys+11d59
Computer Name :
Full Path : F:\Windows\Minidump\120612-31000-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 149,192
==================================================

==================================================
Dump File : 101812-34625-01.dmp
Crash Time : 10/18/2012 9:08:52 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000003
Parameter 2 : 0x83933208
Parameter 3 : 0x83933208
Parameter 4 : 0x87fb6b98
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+3900
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Crash Address : ntoskrnl.exe+11866e
Stack Address 1 : ntoskrnl.exe+6972a
Stack Address 2 : ntoskrnl.exe+86986
Stack Address 3 : fltmgr.sys+6fcb
Computer Name :
Full Path : F:\Windows\Minidump\101812-34625-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 151,024
==================================================

==================================================
Dump File : 101712-32500-01.dmp
Crash Time : 10/17/2012 4:48:52 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00005003
Parameter 2 : 0xc0402000
Parameter 3 : 0x000004c7
Parameter 4 : 0x74fd3001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+d2490
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : 32-bit
Crash Address : ntoskrnl.exe+d2490
Stack Address 1 : ntoskrnl.exe+76422
Stack Address 2 : ntoskrnl.exe+9b129
Stack Address 3 : ntoskrnl.exe+6d9c6
Computer Name :
Full Path : F:\Windows\Minidump\101712-32500-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 148,840
==================================================

==================================================
Dump File : 010102-32796-01.dmp
Crash Time : 1/1/2002 12:12:23 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000003
Parameter 2 : 0x8562d360
Parameter 3 : 0x8562d370
Parameter 4 : 0x8562d370
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+11866e
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : 32-bit
Crash Address : ntoskrnl.exe+11866e
Stack Address 1 : ntoskrnl.exe+222c24
Stack Address 2 : ntoskrnl.exe+25700e
Stack Address 3 : ntoskrnl.exe+209bce
Computer Name :
Full Path : F:\Windows\Minidump\010102-32796-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7601
Dump File Size : 149,192
==================================================

#7 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:54 PM

Posted 14 December 2012 - 05:53 PM

Let's start by checking the ram

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

#8 jamesw

jamesw
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:01:54 PM

Posted 14 December 2012 - 06:12 PM

Artrooks,Im running BSOD file collecting program now
Allan, I will run memtest later on tonight
Thanks to both of you




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users