BSOD Every 5 Minutes

tomw92

tomw92

tomw92

Associate
Joined
14 Sep 2008
Posts
202
Location
Keeping 'er Country!
Hi all,

Having major problems with a BSOD!

No particular time it happens, could be playing a game or browsing the net. It has only started happening in the past couple of days, I haven't changed any hardware and no software has been installed.

Upgraded my graphics last month but thats about it.

I've uploaded a pic of a bluescreen view.

http://img534.imageshack.us/img534/5505/capturebmn.png

Hopefully someone can help me sort this out.

Thanks,

Tom

EDIT: Further reading on the bluescreenview shows that all the BSODs are from ntoskrnl.exe+7f1c0 or from ntoskrnl.exe+7f190 address.
 
Last edited:
On Thu 26/07/2012 15:04:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072612-7098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000308A266, 0xFFFFF880086B8F30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 26/07/2012 15:04:14 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: 0x3B (0xC0000005, 0xFFFFF8000308A266, 0xFFFFF880086B8F30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 26/07/2012 13:33:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072612-7956-01.dmp
This was probably caused by the following module: afd.sys (afd+0x42228)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode program 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 26/07/2012 12:46:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072612-10732-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001692FFC)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 26/07/2012 12:43:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072612-8049-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033D2CDC, 0xFFFFF880055DE010, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 26/07/2012 12:41:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072612-7394-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 which cannot be identified at this time.


On Wed 25/07/2012 11:41:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072512-7113-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003357AE9, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 which cannot be identified at this time.


On Tue 24/07/2012 22:32:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072412-8018-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x3, 0xFFFFF900C2624740, 0xFFFFF900C2624740, 0xEFFFF900C2624740)
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 which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

8 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.
 
Nothing is overclocked. Temps look fine, all fans are spinning good with no dust (cleaned a couple of weeks ago).
 
Just another update.

Finally caved and did a re-format. Lets just say it didn't help one bit. Crashed three times this morning.

I'm totally confused now!
 
tomw92 said:
Just another update.

Finally caved and did a re-format. Lets just say it didn't help one bit. Crashed three times this morning.

I'm totally confused now!
Click to expand...

Most of your bsod's have this code: ntoskrnl.exe (nt+0x7F1C0).
This points primarily to memory errors, can also be caused by gfx card memory problems.

You mentioned you have run memtest, just how long did you run it and how many passes? I'd suggest running it for a few hours if you haven't already. If you also have a spare gfx card or have onboard graphics I'd remove the existing and use either of those.

Edit: I'd also suggesting uploading the crash dump files as many here can analyse them for you.
 
Im sorry to hijack thread but im having similar issues: On Wed 01/08/2012 20:14:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-24616-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF680003BDC18, 0x0, 0x0, 0xFFFFF80002069B2B)
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 which cannot be identified at this time.


On Wed 01/08/2012 20:14:29 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 (0xFFFFF680003BDC18, 0x0, 0x0, 0xFFFFF80002069B2B)
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 which cannot be identified at this time.

Any solutions I update all drivers, not sure if its a hardware issue. It basically killed my old GPU(lasted 6 months). dont want it to kill my current one as I've had it for nearly 2 months.
thx
 
When you reinstallef did you install the same graphics driver? If so Yeh only same thing is the hardware. So could be the HDD or .fx memory
 
Random BSOD crashes like this are pretty much guaranteed to be memory. Just because it passes memtest don't rule it out.

My wife's PC was doing much the same, crashing with BSOD completely at random. Memtest passed without a problem. I spent ages reformatting, changing drivers, etc. etc.

Nothing helped.

Took the memory out and bunged some of mine in as a last resort and would you believe it all the problems stopped. RMA'd the original stuff and since it's been replaced the PC's never had a problem.

So memtest isn't 100% guaranteed to be correct.
 
You must log in or register to reply here.
Back
Top Bottom