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

New to Forum but getting multiple BSODs


  • Please log in to reply
8 replies to this topic

#1 tbone1321

tbone1321

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:24 AM

Posted 26 April 2013 - 11:20 AM

Hello there I am new to this forum so forgive me if it is not the correct place to put this but I keep getting random BSODs sometimes once a week sometimes 2-3 times a day and I don't know what is causing it so any help would be appreciated.



BC AdBot (Login to Remove)

 


#2 TwinHeadedEagle

TwinHeadedEagle

  • Security Colleague
  • 352 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Serbia
  • Local time:08:24 AM

Posted 26 April 2013 - 02:31 PM

Please download and install Who Crashed --> http://www.resplendence.com/download/whocrashedSetup.exe
 
Run the program and click on Analyze. When program finishes analyzing, click on OK. Then right click --> Select All --> right click Copy
 
Copy the content here.

#3 tbone1321

tbone1321
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:24 AM

Posted 26 April 2013 - 02:58 PM

Welcome to WhoCrashed (HOME EDITION) v 4.01


This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...




Home Edition Notice


This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



System Information (local)


computer name: TYLER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17155670016 total
VM: 2147352576, free: 1911894016





Crash Dump Analysis


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 4/26/2013 3:59:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042613-21762-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x3, 0xFFFFF880067E66D0, 0x0, 0xFFFFF880067E66D0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/24/2013 3:54:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042413-8346-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x886D8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001586D8, 0xFFFFF8800E5BBDC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 that cannot be identified at this time.



On Wed 4/24/2013 11:46:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042413-8673-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4A (0x7723138A, 0x2, 0x0, 0xFFFFF8800A4A3B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 4/22/2013 4:40:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042213-8205-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1396CF)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001596CF, 0xFFFFF88006886A40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 that cannot be identified at this time.



On Wed 4/3/2013 8:35:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040313-9687-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x21AF00)
Bugcheck code: 0x50 (0xFFFFF960002DAF00, 0x8, 0xFFFFF960002DAF00, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 that cannot be identified at this time.



On Fri 3/1/2013 2:40:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030113-9360-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x35E3BC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800039BC3BC, 0xFFFFF8800375B868, 0xFFFFF8800375B0C0)
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 that cannot be identified at this time.



On Mon 1/21/2013 2:17:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-6988-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA801170FB30, 0xFFFFFA801170FE10, 0xFFFFF8000399D510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 1/14/2013 3:29:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-7394-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80116F8B30, 0xFFFFFA80116F8E10, 0xFFFFF8000378C510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 12/5/2012 6:44:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120512-7207-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x136E62)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000216E62, 0xFFFFF8800AA81FC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 that cannot be identified at this time.



On Mon 11/19/2012 2:31:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111912-7160-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80121BA170, 0xFFFFFA80121BA450, 0xFFFFF8000379D510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 10/29/2012 1:03:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-7628-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008E1B808, 0xFFFFF88008E1B060, 0xFFFFF800034B236B)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 that cannot be identified at this time.





Conclusion


11 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.



#4 TwinHeadedEagle

TwinHeadedEagle

  • Security Colleague
  • 352 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Serbia
  • Local time:08:24 AM

Posted 27 April 2013 - 12:30 AM

Have you recently changed some hardware, anti-malware programs or installed drivers? Do you suspect on malware?

Download SIW --> http://download.instalki.pl/programy/Windows/Narzedzia/testowanie_i_diagnostyka/siw-setup.exe
 
Install program and open it. Click on Sensors and take screenshot...

#5 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:24 PM

Posted 27 April 2013 - 02:28 AM

Please go to C:\Windows\Minidump folder. Do you see any dmp logs from the folder? If yes, then read the instruction below. If not, configure kernel memory dump debugging information under startup and recovery.

> Right-click My Computer and choose Properties.

> Go to Advanced System Settings - Advance Tab.

> Under Startup and Recovery, click Settings...

> Look for 'write debugging information' and use Kernel memory dump

> Checkmark overwrite any existing file

If there are latest created minidumps under C:\Windows\Minidump folder, please post the latest dmp logs (atleast 5) by :

> Highlight (holding ctrl key) and choosing the dmp logs by hitting enter or left mouse click.

> Right-click and choose send to desktop.

> When on desktop, highlight all dmp logs and right-click and send to compressed zipped folder.

> Upload and share the link by registering here https://www.box.com/
* minidumps log sample 010613 - 16676 -01.dmp -> 01 is for month - 06 for day - 13 is for year.

 

Try downloading Speccy and then install the program.  To post and publish a snapshot of your PC.
. In the Menu bar, click File -> Publish Snapshot
. Click Yes > then Copy to Clipboard
. On your next reply, right-click on a empty space and click Paste on reply box then click Post.


Tekken
 


#6 tbone1321

tbone1321
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:24 AM

Posted 27 April 2013 - 12:57 PM

Ok thanks I will try that Monday I am away from work today!



#7 tbone1321

tbone1321
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:24 AM

Posted 29 April 2013 - 08:51 AM

Thank you everyone for the help below are the links if I did something wrong please let me know.

 

Speccy link

http://speccy.piriform.com/results/KFj7WxggMN2qKLzlBrpcmun

 

minidump link

https://www.box.com/s/30z7m42lec5z5yycvaic

 

sensor picture link

https://www.box.com/s/bzcwpwi7adust41u8cs9



#8 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:12:54 PM

Posted 29 April 2013 - 12:09 PM

Hi tbone 1321

 

It seems that you installed a graphic driver update from MS site. BSOD is often caused by faulty display driver. Please uninstall your current driver and install latest driver for GTX 560 from Nvidia site.

 

http://www.nvidia.in/Download/index.aspx?lang=en-in



#9 tbone1321

tbone1321
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:02:24 AM

Posted 29 April 2013 - 02:49 PM

Awesome thanks for the help I did that so I guess we play the waiting game and see lol.

 

is there a rep system here or anything?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users