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

i am having a problem with my PC crashing with Bsod's


  • Please log in to reply
10 replies to this topic

#1 Reddyblaster

Reddyblaster

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:25 AM

Posted 15 May 2015 - 02:51 AM

i had recently installed a new GPU

since then my PC has gone balls

THis my PC Specs

  Processor: AMD A4-4000 APU with Radeon™ HD Graphics     (2 CPUs), ~3.0GHz
             Memory: 8192MB RAM
Available OS Memory: 8150MB RAM
          Page File: 2799MB used, 13543MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
GPU: NVidia GT610 2gb asus version

 

 



BC AdBot (Login to Remove)

 


#2 Reddyblaster

Reddyblaster
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:25 AM

Posted 15 May 2015 - 02:58 AM

ok i just installed whocrashed

and it says i was crashed by ntoskrnl.exe



#3 Reddyblaster

Reddyblaster
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:25 AM

Posted 15 May 2015 - 03:01 AM

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 5/15/2015 4:35:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051515-19218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0xA (0xFFFFE00052105F10, 0x2, 0x0, 0xFFFFF80271259577)
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 that cannot be identified at this time. 



On Fri 5/15/2015 4:35:01 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0xA (0xFFFFE00052105F10, 0x2, 0x0, 0xFFFFF80271259577)
Error: IRQL_NOT_LESS_OR_EQUAL
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 that cannot be identified at this time. 



On Thu 5/14/2015 8:41:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051415-25937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0xA (0xFFFFE000015592A8, 0x2, 0x1, 0xFFFFF80206CC13B3)
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 that cannot be identified at this time. 



On Thu 5/14/2015 7:41:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051415-20578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFCF7ED30, 0x510000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Thu 5/14/2015 4:48:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051415-21703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x1A (0x41793, 0xFFFFF6800013DD30, 0x1B, 0x1A)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Thu 5/14/2015 4:44:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051415-18625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x1A (0x41792, 0xFFFFF680003BAD30, 0x180000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 5/13/2015 11:38:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051315-21671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x1A (0x41792, 0xFFFFF6800001FD30, 0x530000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 5/13/2015 5:06:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051315-18640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x109 (0xA3A01F5A1233C770, 0x0, 0xCD32B3B95C93AFE7, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Tue 5/12/2015 12:09:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051215-18015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x1A (0x41201, 0xFFFFF6801CF38DB0, 0x93B01801674F2847, 0xFFFFE0005D9DDE30)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Sun 5/10/2015 1:13:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051015-20390-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x31EEC) 
Bugcheck code: 0x24 (0xB500190645, 0xFFFFD000245205F8, 0xFFFFD0002451FE00, 0xFFFFF8019A9C513B)
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

16 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 


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 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 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:55 PM

Posted 15 May 2015 - 09:05 AM

What operating system are you running?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#5 Reddyblaster

Reddyblaster
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:25 AM

Posted 15 May 2015 - 11:25 PM

i am running win 8.1



#6 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:55 PM

Posted 16 May 2015 - 10:16 AM

 
 
 
 
Please run sfc /scannow
 
The sfc /scannow command scans all protected system files and replaces corrupted and incorrect versions with correct Microsoft versions.
 
To run sfc /scannow in Windows 8 you will need to open the Elevated Command Prompt.  The easiest way to do this is to press the Windows key windowskey_zps092d5c75.png and the X key.   A menu will open with the option Command Prompt (Admin), click on this.
 
You will see a window similar to the one below.
 
elevatedcommandpromptw7_zpseba8c499.png
 
When the Elevated Command Prompt opens type in sfc /scannow (please note the space between sfc and /scannow), then press Enter.
 
If the scan finds no integrity  problems in the first portion of the scan it should stop, to be sure that the scan has stopped wait five minutes, then type in exit and press Enter to stop the scan.
 
If it does find integrity problems the scan will continue.  This will take a while, please have patience and allow it finish.  
 
When the scan is finished please post the log of this scan.
 
To find sfc /scannow log, reopen the Elevated Command Prompt using the Windows key windowskey_zps092d5c75.png and the X key method outlined in the instructions above. 
 
When the Elevated Command Prompt opens copy and paste the following in the Command Prompt, then press Enter.  
 
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
 
This will place a new icon on the desktop titled sfcdetails.  Click on this to open the log, copy it and paste it in your topic.

Edited by dc3, 16 May 2015 - 10:17 AM.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#7 Reddyblaster

Reddyblaster
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:25 AM

Posted 16 May 2015 - 11:24 PM

ok i tried it said WIndows resource Protection could not perform the requested opertaion 



#8 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:55 PM

Posted 17 May 2015 - 10:35 AM

Are you using an administrator user account?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#9 Reddyblaster

Reddyblaster
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:25 AM

Posted 18 May 2015 - 07:21 AM

DC3 thanks for helping me out till here

See, i Just wiped my pc 

and i when i tried reinstalling itshut down on me during the process.

I am guessing that i have a bad dvd

so i am going to try and re download windows from their site 

If it was a hard ware issue what would u have thought , which component would have gone bad 

 

 

Thanks :)

 

And yes i was using an admin account


Edited by Reddyblaster, 18 May 2015 - 07:23 AM.


#10 Reddyblaster

Reddyblaster
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:25 AM

Posted 18 May 2015 - 09:20 AM

ok i tried to reinstall 

it installed properly

after that when it booted it crashed 

again and again 

what to do ?????????????????????



#11 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:55 PM

Posted 18 May 2015 - 10:04 AM

If the installation was successful it looks like you have a hardware problem.

 

If you can, please do the following.

 

Please download and install Speccy to provide us with information about your computer.  Clicking on this link will automatically initiate the download. 
 
When Speccy opens you will see a screen similar to the one below.
 
speccy9_zps2d9cdedc.png
 
Click on File which is outlined in red in the screen above, and then click on Publish Snapshot.
 
The following screen will appear, click on Yes.
 
speccy7_zpsfa02105f.png
 
The following screen will appear, click on Copy to Clipboard.
 
speccy3_zps1791b093.png
 
In your next post right click inside the Reply to Topic box, then click on Paste.  This will load a link to the Speccy log.
 
==========
 

Please download MiniToolBox, save it to your desktop and run it.
 
Checkmark only the following checkboxes:
 
• List last 10 Event Viewer log
• List Installed Programs
• List Users, Partitions and Memory size.
• List Minidump Files
 
Click on Go to start the scan.  Once it is finished highlight the text, copy it and paste it in your next post.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users