PC crashing WIN 8 and sometimes systems boots and sometimes not ...

[Asim Khan]

Salaam guys, please help me with this, system boots sometimes and sometimes not, checked on gpu and onboard vga both ... didn't help ... and keeps crashing as memory dump

Pc specs:
athlon 2 x4 640
2gb ddr3
hd 6670 ddr5

tired of memory dump crap, attaching screenshot:

 

[Asim Khan]

no replies? c;mon guys

 

[Gamer150]

run memory test

 

[wfsoomro]

If you are absolutely sure that it's not your gpu, then, I think if there is no beeping sound when it does not boot, then it isn't RAM or Processor issue. I believe it could be an issue with your mobo or maybe just maybe with your psu.

 

[Gamer150]

Just check your ram with " burn in test " software. than let us know.

 

[mehmood115]

Can you upload the minidump file in order to understand it accurately the caused of this problem. Minidump files are located in C:\Windows\Minidump. Upload it somewhere then I will check.

 

[Asim Khan]

where can i upload the file? i have disabled the memory dumping process, pc just crashed once, never again, running fine since then ... it's about a week now

 

[Asim Khan]

Using Whocrashe software, i got the following notes for how many times it crashed, any one who can help me with it?

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

Crash dumps are disabled for your computer.

On Wed 1/15/2014 12:37:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011514-13494-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E04A30, 0xFFFFF80002E08A30, 0xFFFFF80002E04A30)
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 1/15/2014 12:03:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011514-12901-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8D, 0x1, 0xFFFFF80002C8188D, 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 that cannot be identified at this time.



On Wed 1/15/2014 12:00:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011514-13587-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x16E1B, 0xD, 0x0, 0xFFFFF80002CD0B8B)
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 Wed 1/15/2014 8:57:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011514-17222-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF88004C871DA)
Bugcheck code: 0x50 (0xFFFFF88003FFF4E0, 0x0, 0xFFFFF88004C871DA, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 190.38
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 190.38
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.
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 190.38 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA



On Wed 1/15/2014 8:54:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011514-14742-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xFE (0x5, 0xFFFFFA8002A011A0, 0x10DE03F2, 0xFFFFFA80015FB650)
Error: BUGCODE_USB_DRIVER
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 error has occurred in a Universal Serial Bus (USB) driver.
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 1/14/2014 8:54:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011414-12105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF87F8FAB1497, 0x0, 0xFFFFF80002C69D41, 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 that cannot be identified at this time.



On Mon 1/13/2014 1:43:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011314-12402-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xC5 (0xFFFFF80003C029F8, 0x2, 0x0, 0xFFFFF80002BA70BF)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid 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. 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.

- - - Updated - - -
[MENTION=111187]Gamer150[/MENTION], [MENTION=32896]wfsoomro[/MENTION], [MENTION=12930]mehmood115[/MENTION] ... check the above post, these are the error of which pc crashes mostly

 

[wfsoomro]

Well interestingly the last paragraph mentions it's a driver issue. Did you try re-installing/upgrading or rolling back drivers (in case you upgraded them) and if that didn't work then try re-installing windows altogether. One thing that still bugs me that if it were a driver issue, then why would your system refuse to boot up sometimes :-S
Because at that stage windows does not load, to drivers ka to us stage pay koi kirdaar he nahin hai :-/
Could you please clear something, when you said that it doesn't boot sometimes, did you mean k display he nahin ata and bios nahin ata, ya windows load honay wali stage pay problem ati hai? Agar windows load karna shuru kardeta hai then it is not a hardware issue, it's definitely a driver issue then.

 

[mehmood115]

How to Fix BAD_POOL_HEADER Error?
In order to fix BAD_POOL_HEADER error in Windows 8, step-by-step instructions given below must be followed:

• Restart Windows 8 normally.
• If restarting the computer doesn’t resolve the issue, insert Windows 8 bootable media into optical media drive (CD/DVD Drive).
• On the displayed Windows Setup box, click Next.
• On the next page, click Repair your computer.
• On Choose an option screen, click Troubleshoot.
  
  
  
• On Troubleshoot screen, click Refresh your PC.
• On Refresh your PC screen, click Next.
• On the next page, from Choose a target operating system list, click Windows 8.
• On the next page, click Refresh to start the refresh process.
• Wait till the Windows 8 system get refreshed and restarts the system automatically.

- - - Updated - - -

Its weird that you got different error every time but I have mentioned the solution for you for BAD_POOL_ERROR if it doesn't work then let me know.

- - - Updated - - -

Driver corruption might be an issue reinstall all the drivers if you can

 

[mehmood115]

When your system sometime not booting up it telling us that you have an hardware issue and when it booted up you got the BSOD it telling us the hardware might be the RAM so change the RAM and then test.

 

[Gamer150]

If you couldn't figure out, test your memory with burn in test it test it will reveal every thing and relieve your nerves.

 

[Asim Khan]

Well interestingly the last paragraph mentions it's a driver issue. Did you try re-installing/upgrading or rolling back drivers (in case you upgraded them) and if that didn't work then try re-installing windows altogether. One thing that still bugs me that if it were a driver issue, then why would your system refuse to boot up sometimes :-S
Because at that stage windows does not load, to drivers ka to us stage pay koi kirdaar he nahin hai :-/
Could you please clear something, when you said that it doesn't boot sometimes, did you mean k display he nahin ata and bios nahin ata, ya windows load honay wali stage pay problem ati hai? Agar windows load karna shuru kardeta hai then it is not a hardware issue, it's definitely a driver issue then.

i took my system to local repair shop, he said might be vga cable problem coz there it gave display every time, i mean booted every time, then i bought the vga cable, since then boot up screen problem nai aya dobara ... i did win7 back, thought this amd machine is not compatible with win8, but problem persists, it crashes any time it wants, or works for hours ... now don't know what does it want

- - - Updated - - -

How to Fix BAD_POOL_HEADER Error?
In order to fix BAD_POOL_HEADER error in Windows 8, step-by-step instructions given below must be followed:

• Restart Windows 8 normally.
• If restarting the computer doesn’t resolve the issue, insert Windows 8 bootable media into optical media drive (CD/DVD Drive).
• On the displayed Windows Setup box, click Next.
• On the next page, click Repair your computer.
• On Choose an option screen, click Troubleshoot.
  
  
  
• On Troubleshoot screen, click Refresh your PC.
• On Refresh your PC screen, click Next.
• On the next page, from Choose a target operating system list, click Windows 8.
• On the next page, click Refresh to start the refresh process.
• Wait till the Windows 8 system get refreshed and restarts the system automatically.

- - - Updated - - -

Its weird that you got different error every time but I have mentioned the solution for you for BAD_POOL_ERROR if it doesn't work then let me know.

- - - Updated - - -

Driver corruption might be an issue reinstall all the drivers if you can

now my system boots everytime since i changed the vga cable, but still crashes, yar i have no intizam for another ram to check ram issue, all my friends are ddr2 mode people -_-

- - - Updated - - -

If you couldn't figure out, test your memory with burn in test it test it will reveal every thing and relieve your nerves.

[MENTION=12930]mehmood115[/MENTION] and [MENTION=111187]Gamer150[/MENTION] ... i highly doubt my ram too but unfortunately don't have any arrangement for ram currently, and mention the name of the software to test the ram please

- - - Updated - - -

One more thing, i never crashed while gaming, been gaming for hours, but only if it wants to in standard usage, browsing or working

 

[Gamer150]

' Burn in Test ' Download this software and test your ram with it. these kind of random may arise when a certain sector of ram is bad and it wont hold your data and cant forward it to cpu when needed.

and plz dont took it to these shops they dont know a shit.

i hope your ram is ok and........

 

[Asim Khan]

' Burn in Test ' Download this software and test your ram with it. these kind of random may arise when a certain sector of ram is bad and it wont hold your data and cant forward it to cpu when needed.

and plz dont took it to these shops they dont know a shit.

i hope your ram is ok and........

this one right? PassMark BurnInTest software - PC Reliability and Load Testing
downloaded it, ran it on ram, about 21 loops/cycles done, no error in ram ... so it is my HDD? but my HDD didn't do such problem on my previous system

 

[Gamer150]

hmmmmmmm only 21 cycles ! i doubt it......

did the software notifies 'ram test completed' or some thing like that ?

if there arent any errors than your ram is ok.

...............................................................................................................

reinstall windows problem persist ?

 

[Gamer150]

is your pc fine now! any update

 

[Asim Khan]

is your pc fine now! any update

got rid of it, but i miss the performance