Random Win 7 home premium 64bit restart with err and minidump attached

[robert02]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1048

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000008
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880016905BB
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\082012-27331-01.dmp
C:\Users\Robert\AppData\Local\Temp\WER-80262-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[FredeGail]

Hello Robert02 and welcome to Sevenforums.

To be able to help you, we'd need you to attach a full report. This includes, sysinfo's, nfo etc. To get these files, use our thread below.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

BSOD Analyse

On dump: SFC /SCANNOW :: We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350e100
 0000000000000008 
CURRENT_IRQL:  2
FAULTING_IP: 
[COLOR=Green]ndis!NdisAllocateCloneNetBufferList+1ab
fffff880`016a45bb 498b5e08        mov     rbx,qword ptr [r14+8]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  YahooMessenger
TRAP_FRAME:  fffff88003346b20 -- (.trap 0xfffff88003346b20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004349890 rbx=0000000000000000 rcx=fffffa8004349940
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016a45bb rsp=fffff88003346cb0 rbp=fffffa8004349760
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8004ec3100
r11=00000000000f7f00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
ndis!NdisAllocateCloneNetBufferList+0x1ab:
fffff880`016a45bb 498b5e08        mov     rbx,qword ptr [r14+8] ds:86a0:00000000`00000008=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800032de769 to fffff800032df1c0
STACK_TEXT:  
fffff880`033469d8 fffff800`032de769 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`033469e0 fffff800`032dd3e0 : fffffa80`07caa6f0 fffffa80`0d655b10 fffffa80`0cf8cb4c fffffa80`04349890 : nt!KiBugCheckDispatch+0x69
fffff880`03346b20 fffff880`016a45bb : 00000002`00000000 00000000`00000004 00000000`00000000 fffff800`03377ca7 : nt!KiPageFault+0x260
fffff880`03346cb0 fffff880`01796b22 : 00000004`00000007 00000000`00000002 fffff880`03346e50 fffffa80`04375ec0 : ndis!NdisAllocateCloneNetBufferList+0x1ab
fffff880`03346dc0 fffff880`017c43df : fffffa80`04375ec0 fffffa80`04375ec0 00000000`00000000 00000000`00000000 : NETIO!NetioAllocateAndReferenceCloneNetBufferList+0x32
fffff880`03346df0 fffff880`017c7f40 : 00000000`00000000 00000000`00000000 00000000`000f7f00 fffffa80`069f3880 : NETIO!StreamDataTruncateAfterDataLength+0x4f
fffff880`03346e60 fffff880`017c96b4 : fffffa80`04375ec0 00000000`00000000 fffffa80`04375ec0 00000000`00000000 : NETIO!StreamPermitDataHelper+0x40
fffff880`03346e90 fffff800`032e98ec : fffff880`03317180 fffffa80`0777b380 fffffa80`0777b380 00000000`00000000 : NETIO!StreamPermitRemoveDataDpc+0x84
fffff880`03346f00 fffff800`032e2305 : fefffffe`fffffdff fffffa80`078c4b50 00000000`00000000 fffff880`017c9630 : nt!KiRetireDpcList+0x1bc
fffff880`03346fb0 fffff800`032e211c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`07b63f80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND:  kb
FOLLOWUP_IP: 
NETIO!NetioAllocateAndReferenceCloneNetBufferList+32
fffff880`01796b22 488bd8          mov     rbx,rax
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  NETIO!NetioAllocateAndReferenceCloneNetBufferList+32
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME:  NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381
FAILURE_BUCKET_ID:  X64_0xD1_NETIO!NetioAllocateAndReferenceCloneNetBufferList+32
BUCKET_ID:  X64_0xD1_NETIO!NetioAllocateAndReferenceCloneNetBufferList+32
Followup: MachineOwner[/COLOR]

Best Regards,
Frederik.

 

[robert02]

Thank you very much Frederik!
I will try to post more info about my system in the following days.
What you've pasted there is one of my dump file decoded? "PROCESS_NAME: YahooMessenger"
Something I haven't mentioned is that I get the blue screen as well.
I ran the sfc /scannow and it went 100% with no errors.
I will post another reply once I update my system infos.
I had no more problems for about 2 days, but I still have to investigate this as I consider it instable now.

Cheers,
Robert

 

[FredeGail]

Hello Robert!

The "PROCESS_NAME:" is just telling where the system crashed when it crashed. So, if you were in YahooMessenger at that time, It'll tell YahooMessenger, but that doesn't mean that's the culprit.

Next thing: Combining your crash dumps and the general view of BSODs culprits, I'd suggest you to have a look at your memory, the sticks. Through decades people have been using the bootable tool called Memtest86+ and it's basically very unique in these manners.
:info: Be sure to check your warranty rules and regulations before opening your case.

* Memtest86+ is USB-ready, and can be booted directly from it. Download the flashdrive wizard.
* To ensure that either your sticks OR your motherboard slots are broken, it's necessary to do the below procedure-
* Pull out all sticks except ONE, scan it.
* If no errors, pull the scanned stick into another slot.
* Proceed like this until you've scanned all sticks individually, and all the slots.​

​

Best Regards,
Frederik.