Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD 30secs to 30 minutes after start-up.

17 Jan 2013   #1
CJBudders99

Windows 7 Home Edition 64bit
 
 
BSOD 30secs to 30 minutes after start-up.

Hey, i'm not the wisest with computers. I'm over the moon i figured out how to use the SF tool that grabs mini dumps from my BSOD's.. following instructions of course but i worked it.

anyways, my system has been suffering from BSOD for a while now and dont know what to so that is what brings me here.

they happen at certain times and i can be doing anything.

i know it migh tnot seem like there is much info from me but i'm confused to why they happen irregularly and at different times, my computer has not been powered on for more than an hour for the past year because of it.

i've tried to switch ram around and tried another 2 hard drives and reinstall windows on each hard drive, used one stick of ram to all 4. changing ide cables from hard drive to motherboard, still nothing. hoping a pro can help me or someone with a bit more sense about the subject.

i'm using
windows 7 home edition 64bit
amd dual core
seagate 80gb hd
nvidia geforce 8400 cs
2 x 1gb ram ddr2
2 x 512mb ram ddr2

please if you could help you will be my hero for life!
many thanks.


My System SpecsSystem Spec
.
17 Jan 2013   #2
CJBudders99

Windows 7 Home Edition 64bit
 
 

Sorry, I did not realise that the SF program was still running until i got another pop up for me to click okay, here is the complete file now.
My System SpecsSystem Spec
18 Jan 2013   #3
CJBudders99

Windows 7 Home Edition 64bit
 
 

hi to anyone viewing this, i found some software to find the problem and analyze my minidump files and this is what it showed in the results.

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 CPU 4400 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3219640320 total
VM: 2147352576, free: 2016268288




Crash Dump Analysis

</B>

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 18/01/2013 01:18:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-14757-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8004E29A10, 0xFFFFFA8004E29B90, 0xC180006)
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 Fri 18/01/2013 01:18:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndisuio.sys (ndisuio+0xB3D7)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8004E29A10, 0xFFFFFA8004E29B90, 0xC180006)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndisuio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS User mode I/O driver
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 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 18/01/2013 01:10:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-14820-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8002DBA580, 0xFFFFFA8002DBA700, 0xC180021)
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 Thu 17/01/2013 11:21:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-15225-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80046E82D0, 0xFFFFFA80046E8450, 0xC180001)
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 Thu 17/01/2013 11:19:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-16083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8003A3F280, 0xFFFFFA8003A3F400, 0xC18000A)
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 Thu 17/01/2013 11:09:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-13244-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8002629AC0, 0xFFFFFA8002629C40, 0xC180016)
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 Thu 17/01/2013 10:54:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-16520-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8002868180, 0xFFFFFA8002868300, 0xC180001)
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 16/01/2013 22:56:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-12027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80051EF180, 0xFFFFFA80051EF300, 0xC180004)
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.



...
notice in each minidump, its the same problem?

now i just need to find out how to fix it, any comments about it or people with knowledge of fixing this please?
My System SpecsSystem Spec
.

Reply

 BSOD 30secs to 30 minutes after start-up.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Bsod after 10 minutes that i start my pc.
Hi guys, i'm sorry for my english. When i start my pc, or when i use it after i was suspended, i see the damn bsod. I hope this post respects the rules of this forum. Thank you for your time.
BSOD Help and Support
BSOD a few minutes after start up
Problem has been persistent for the past week. I log on and the computer slowly spirals into a state of lag before completely freezing up and then hitting me with the BSOD! As of yet this hasn't happened when running in safe mode which leads me to believe there might be a driver conflict? I...
BSOD Help and Support
BSOD 9f around 10 minutes after start-up consistently.
Evening. Rig BSOD's about 10 minutes after startup. I did a clean installation of windows 7 today to no avail. The setup was working fine for 1.5 years until about 2 months ago when the video card driver (nvidia gtx 480 x2 in sli) started crashing, hard. Sometimes the driver would...
BSOD Help and Support
BSOD 5 minutes after computer start
Hello, I have very annoying problem with BSOD showing up circa 5 minutes after starting the computer: It happens only after the first start (sometimes also after the first restart) - I have been doing something for 5 minutes and suddenly - boom! - BSOD. Computer restarts and then it works...
BSOD Help and Support
BSOD few minutes after start
Windows 7 Home 64 bit 2010 original software on laptop I keep getting the BSOD in normal mode after a few minutes of starting my laptop. It is giving me the error PAGE_FAULT_IN_NONPAGE and it is saying that it is caused by driver "ntoskrnl.exe" I have attached the dump and system report. It...
BSOD Help and Support
BSOD happens about 40-50 minutes after start-up
I have recently been experiencing a BSOD everytime i startup (in normal or safe-mode) around 40-50 minutes after startup. It seems to just shut down every program then go to BSOD while is able to create a dump file but never automatically restart. I've also used spy-bot and Malwarebyte to find...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 23:38.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App