BSOD errors every couple of minutes

porritt

Standard Member
Here is a few of my bsod mini dumps but im not sure how to interpret them can anyone help?
Ps. the coloured |||||||||||| lines is what ive put it to seperate the mini dump files from each other there is a total of 3 mini dumps here.




Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\110310-33250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50
Debug session time: Wed Nov 3 12:54:33.818 2010 (UTC + 0:00)
System Uptime: 0 days 0:04:11.427
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002a79984, fffff88006c22250, 0}

Probably caused by : hardware ( nt!KiSystemServiceCopyEnd+4 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002a79984, Address of the instruction which caused the bugcheck
Arg3: fffff88006c22250, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02a79984 1800 sbb byte ptr [rax],al

CONTEXT: fffff88006c22250 -- (.cxr 0xfffff88006c22250)
rax=0000000000000000 rbx=fffffa8005b71060 rcx=0000000000000000
rdx=00000000000007ff rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002a79984 rsp=fffff88006c22c20 rbp=fffff88006c22ca0
r8=fffffa80050ddbb8 r9=0000000000000000 r10=fffffffffffffffe
r11=00000000002f9d00 r12=000000001f24fcf0 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!KiSystemServiceCopyEnd+0x4:
fffff800`02a79984 1800 sbb byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: vsserv.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02a79984 1800 sbb byte ptr [rax],al

LAST_CONTROL_TRANSFER: from 000000007738009a to fffff80002a79984

STACK_TEXT:
fffff880`06c22c20 00000000`7738009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x4
00000000`1f24fcc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7738009a


FOLLOWUP_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02a79984 1800 sbb byte ptr [rax],al

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiSystemServiceCopyEnd+4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff88006c22250 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

Followup: MachineOwner
---------



||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||




Loading Dump File [C:\Windows\Minidump\110210-586265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02c9de50
Debug session time: Tue Nov 2 16:17:31.796 2010 (UTC + 0:00)
System Uptime: 0 days 0:10:26.406
Loading Kernel Symbols
...............................................................
................................................................

Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DA, {504, fffff6fc40077820, 2, ef04}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+b43b )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_PTE_MISUSE (da)
The stack trace identifies the guilty driver.
Arguments:
Arg1: 0000000000000504, Type of error.
Arg2: fffff6fc40077820
Arg3: 0000000000000002
Arg4: 000000000000ef04

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xDA

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002b28e11 to fffff80002ad0740

STACK_TEXT:
fffff880`02f939d8 fffff800`02b28e11 : 00000000`000000da 00000000`00000504 fffff6fc`40077820 00000000`00000002 : nt!KeBugCheckEx
fffff880`02f939e0 fffff800`02ae05e4 : 00000000`00000004 fffff800`02c85720 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xb43b
fffff880`02f93af0 fffff800`02ae3df5 : fffffa80`018a8040 00000000`00000008 0000ef6c`000026ea 00000000`00000001 : nt!MiEmptyPteBins+0x10d
fffff880`02f93b40 fffff800`02ae4eb4 : 00000000`00000008 00000000`00000001 fffffa80`018a8040 fffff800`02ae40cb : nt!MiAdjustPteBins+0x29
fffff880`02f93b80 fffff800`02ae5173 : 00000000`00000008 fffff880`02f93c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x40
fffff880`02f93bd0 fffff800`02d74c06 : fffffa80`018c8040 00000000`00000080 fffffa80`018a8040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`02f93d40 fffff800`02aaec26 : fffff800`02c4ae80 fffffa80`018c8040 fffffa80`018c7530 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f93d80 00000000`00000000 : fffff880`02f94000 fffff880`02f8e000 fffff880`02f93710 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+b43b
fffff800`02b28e11 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+b43b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b

BUCKET_ID: X64_0xDA_nt!_??_::FNODOBFM::_string_+b43b

Followup: MachineOwner
---------



|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||



Loading Dump File [C:\Windows\Minidump\110110-34265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c99e50
Debug session time: Mon Nov 1 15:35:38.527 2010 (UTC + 0:00)
System Uptime: 0 days 0:11:08.136
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002acb984, fffff880065ad1e0, 0}

Probably caused by : hardware ( nt!KiSystemServiceCopyEnd+4 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002acb984, Address of the instruction which caused the bugcheck
Arg3: fffff880065ad1e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02acb984 1800 sbb byte ptr [rax],al

CONTEXT: fffff880065ad1e0 -- (.cxr 0xfffff880065ad1e0)
rax=0000000000000002 rbx=fffffa8005bc5b60 rcx=fffffa80057de530
rdx=fffffa80057de4b8 rsi=00000000044ee4d8 rdi=fffff880065adbc8
rip=fffff80002acb984 rsp=fffff880065adbb0 rbp=fffff880065adca0
r8=0000000000000000 r9=0000000000000001 r10=0000000000000003
r11=fffff880065adba0 r12=0000000000000000 r13=00000000044ee560
r14=0000000000000000 r15=0000000000ca9f20
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!KiSystemServiceCopyEnd+0x4:
fffff800`02acb984 1800 sbb byte ptr [rax],al ds:002b:00000000`00000002=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: SearchIndexer.

CURRENT_IRQL: 0

MISALIGNED_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02acb984 1800 sbb byte ptr [rax],al

LAST_CONTROL_TRANSFER: from 000000007789030a to fffff80002acb984

STACK_TEXT:
fffff880`065adbb0 00000000`7789030a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x4
00000000`044ee4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7789030a


FOLLOWUP_IP:
nt!KiSystemServiceCopyEnd+4
fffff800`02acb984 1800 sbb byte ptr [rax],al

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiSystemServiceCopyEnd+4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff880065ad1e0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

Followup: MachineOwner
---------

|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||



Here are 3 different mini dump files all fairly recently i just picked some at random hope this is enough :)
 
Last edited:

Lemon13

Standard Member
Can you give some details about your system (os, brand, mainboard.....)
is there anything obvious in eventviewer?
I`ve seen this with a customer of mine, there the problem was he upgraded vista to win7, a fresh win7 install solved the problem.
the minidumps point to memory or driver problem, first do a memory check, either use the MS one or get
Memtest86+ - Advanced Memory Diagnostic Tool
if that comes out ok start a cmd box, type sfc /scannow (the installation disk has to be in the cd/dvd drive for that and you might need to install updates/sp´s again after that, depending on the state of the install disk)
 

Stiggy

Distinguished Member
Blue screens are often due to dodgy drivers or memory.

Have you updated any drivers recently? Have you tried a System Restore to a point before the problems started?
 

TheDarkMage

Standard Member
if you have updated anything just before it happened then that would be a good place to start. if not then it would point to bad mem
 

porritt

Standard Member
Thanks for the reply's First things first Ive tried all the things that lemon told me to do and the first test came up clean. Then i did the boot disk with sfc /scannow and it said it had found 2 errors and deleted them and will replace them upon start up which it did with the boot disk so that has seemed to work fine since i done that, its been about 2 -3 days ago and it hasn't happened since so it must have worked. :)

Thank you :thumbsup:
 

porritt

Standard Member
:mad: Its happened again this time i think its pointing towards a driver



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\110610-32500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a68000 PsLoadedModuleList = 0xfffff800`02ca5e50
Debug session time: Sat Nov 6 11:06:56.328 2010 (UTC + 0:00)
System Uptime: 0 days 0:05:16.937
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff8a003d131f0, fffff8a003d132a0, 50b011f}

GetPointerFromAddress: unable to read from fffff80002d100e0
Probably caused by : ntkrnlmp.exe ( nt!SeAccessCheckByType+80e )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a003d131f0, The pool entry we were looking for within the page.
Arg3: fffff8a003d132a0, The next pool entry.
Arg4: 00000000050b011f, (reserved)

Debugging Details:
------------------


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fffff8a003d131f0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002c0b6d3 to fffff80002ad8740

STACK_TEXT:
fffff880`03933908 fffff800`02c0b6d3 : 00000000`00000019 00000000`00000020 fffff8a0`03d131f0 fffff8a0`03d132a0 : nt!KeBugCheckEx
fffff880`03933910 fffff800`02aa1fd1 : fffff880`03933ab8 fffff8a0`01b0c5a0 fffff8a0`63536553 fffff880`03933aa0 : nt!ExDeferredFreePool+0x12c4
fffff880`039339c0 fffff800`02aa2283 : 00000000`00244840 00000000`00000000 00000000`0000051c fffff8a0`02000000 : nt!SeAccessCheckByType+0x80e
fffff880`03933b40 fffff800`02ad7993 : 00000000`0000051c fffffa80`05641060 00000000`0187f528 00000000`0187f6f8 : nt!NtAccessCheck+0x57
fffff880`03933bb0 00000000`7723039a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0187f5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7723039a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!SeAccessCheckByType+80e
fffff800`02aa1fd1 8bc3 mov eax,ebx

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!SeAccessCheckByType+80e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x19_20_nt!SeAccessCheckByType+80e

BUCKET_ID: X64_0x19_20_nt!SeAccessCheckByType+80e

Followup: MachineOwner
 

Lemon13

Standard Member
I recommend a fresh install, with loads of different bsod´s its hard to find a culprit. You could do a sfc /scannow again, if there are again corrupted systemfiles it might also be a flakey hdd controller/mainboard.
How long did the memtest run (best is over night)?
 

porritt

Standard Member
Ran another sfc /scannow and it said there was items that were not repaired
it said a lot of stuff about the processor not been able to be repaired like the .dll files and other things like that so i might just have to do a fresh install
 

961

Well-known Member
What o/s system are you running? (Vista?)

What hardware is used. Scanners/Printers etc?

Have you run full virus check? What virus system?

Have you tried system restore back to before the trouble?

Any alterations, dodgy downloads?
 

porritt

Standard Member
1)Windows 7 Eternity 64Bit

2)Have a printer and an external Hard drive

3)Yes i have ran a full virus scan using Bitdefender and Malwarebytes

4)System Restore wasn't enabled at the time for some reason

5)No dodgy downloads
 

rbanksy

Standard Member
Which brand of PC do you have? for example on Dell you can get diagnostic software to scan the memory and hard disk for hardware faults
 

porritt

Standard Member
Yes i have searched about (ntkrnlmp.exe) and most cases are irrelevant into whats happening to me, also i ran a memtest86+ let it do a few runs and it had no errors so the ram is ok. Also the link you provided "961" was useful in some aspects but not it others they were mainly taking about duel booting. They had similar problems but not the same there was occurring when the computer went into sleep and came out.

Also the past 5 - 6 days i haven't had a single blue screen but i got recommended by someone to run a registry scan and after all the different registry scanners on the internet i used a few and they found multiple problems with my registry but as usual you get all the BS out of the way just to get to the point were it says do you want to fix it if so then buy it now for just £50.00. So could anyone point me in the right direction of how and were i can get a registry scanner / fixer that actually fixes the issues without charging you money or asking for money, if so i would be very grateful. :lease:
 

porritt

Standard Member
:mad::mad::mad: Why is it when it hasn't had a crash in days and i say it hasn't had a crash, IT CRASHES :suicide:
This time it was to do with Firefox in the crash report (IMAGE NAME: afd.sys) Networking problem this time though or bad drivers, but i would believe it would be bad drivers because i cant find any drivers for the network adapters (Realtek RTL8139/810x Family Fast Ethernet NIC)

All the programs tell me that i need to update this driver in particular but i just can find it and the automatic windows one says its up to date :facepalm:
 

Stiggy

Distinguished Member
This time it was to do with Firefox in the crash report (IMAGE NAME: afd.sys) Networking problem this time though or bad drivers, but i would believe it would be bad drivers because i cant find any drivers for the network adapters (Realtek RTL8139/810x Family Fast Ethernet NIC)
How can you be using Firefox if you don't have a network connection? :confused:

You need to start thinking about a reinstall of Windows.
 

cabidge red

Standard Member
Try system restore to a earlier state before the problem started.
If u made an image of the hard drive a some point u could restore that as well.
 

961

Well-known Member
i got recommended by someone to run a registry scan and after all the different registry scanners on the internet i used a few and they found multiple problems with my registry but as usual you get all the BS out of the way just to get to the point were it says do you want to fix it if so then buy it now for just £50.00. So could anyone point me in the right direction of how and were i can get a registry scanner / fixer that actually fixes the issues without charging you money or asking for money, if so i would be very grateful. :lease:
The only registry scanner I'd recommend is CCleaner

Piriform - Download

It may or may not fix the issues you have but it won't charge you and it won't download a lot of other problems which is what many of these other sites do. If there isn't a problem it won't "fix" anything

After all these downloads I'd suggest a scan with malwarebytes (free) to find out if anything else has arrived

Malwarebytes

Then let's see what still needs doing
 

The latest video from AVForums

Podcast: CES 2021 Special - Sony, LG, Panasonic, Samsung, TCL and Hisense TV news and more...
Top Bottom