Would appreciate help with this

Zalthoria

Well-Known Member
#1
Hey I'm runnning win 7 64 bit and got some BSOD errors lately. A quick search around shows it could be a driver issue but im not sure what to do about it. Please help!
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#2
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffac0160ce108, 2, 0, fffff88002c5ce65}

*** WARNING: Unable to verify timestamp for e22w7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys
Probably caused by : e22w7x64.sys ( e22w7x64+6e65 )

Followup: MachineOwner
Hi,
the above dump file is blaming your Killer network drivers:

e22w7x64.sys Wed Mar 18 17:10:51 2015: Killer e2200 PCI-E Gigabit Ethernet Controller please update: ( a new driver version was released today)
Killer Networking - Driver Downloads

If after installing the above the bsod continues I'd remove Norton. Norton circa 2002 was a great application but nowadays it wraps it's tentacles into almost every part of the system. Use the removal tool found here:
Uninstall your Norton product using Norton Removal Tool

Post any new dump files.
 


Zalthoria

Well-Known Member
#3
seems like the killer network is a huge problem :/ when i upgraded to win 10 my Ram usage would balloon because of it and in the end i decided to go back down to win 7
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#4
It runs fine on my system although turning off security apps is a must otherwise it won't install. Anyhoo thanks for updating your thread.. :)
 


Zalthoria

Well-Known Member
#5
Ive up dated but today i crashed again. this time it was 0x50. ive a feeling it might've something to do with killer network again.
 


Attachments

Zalthoria

Well-Known Member
#6
i think i should mention i followed this Memory leak in Windows 8.1 with Killer E2200 and Windows Network Data Usage Monitoring to fix my non paged pool from ballooning. i did that on windows 10 and have since then done a full reformat of my system but i think that changes to registry persists? or am i wrong about that.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#7
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffac012899a30, 0, fffff88005813ee7, 5}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+1d8ee7 )

Followup: MachineOwner
Hi,
the above bugcheck can be caused by:
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.
Reference
As you can see it's blaming a Nvidia gpu driver as the cause and I can also see this reflected through the dump file so it's unlikely down to anything else.
Please uninstall the gpu driver currently installed using the Display driver Uninstaller:
Display Driver Uninstaller (DDU) V15.5.0.0 Released. - Wagnardmobile Forum
This will remove anything left over from previous installs.

Install the latest whql driver (355.98)
Drivers | GeForce

As there is a possibility that your video ram may be at fault (simply because of the type of bugcheck) please run this application to test the Vram:
HOME PAGE OF MISHA CHERKES

Please post the results and any new dump files.

Edit:
I forgot to mention, regarding your question above about registry changes? If you performed a clean install after making those changes to the registry then the clean install will have returned everything back to default values.
 


Zalthoria

Well-Known Member
#8
Followed your steps but crashed again today.
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#9
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F7, {f8c001768169, f88001768169, ffff077ffe897e96, 0}

Probably caused by : tcpip.sys ( tcpip!_report_gsfailure+26 )

Followup: MachineOwner
Hi,
the above is network related and the Bugcheck can be caused by:
Cause
A driver overran a stack-based buffer (or local variable) in a way that would have overwritten the function's return address and jumped back to an arbitrary address when the function returned.
This is the classic "buffer overrun" hacking attack. The system has been brought down to prevent a malicious user from gaining complete control of it.
Code:
SECURITY_COOKIE:  Expected 0000f88001768169 found 0000f8c001768169
I also see the process running at the time of bsod was uTorrent.exe.
Try updating or re-installing:
Windows Downloads -

dtlitescsibus.sys Fri Mar 27 02:05:54 2015: Daemon Tools known bsod issues with windows. If the bsod continues consider removing to test.

NTIOLib_X64.sys Mon Mar 17 10:24:03 2014: MSI Afterburner known bsod issues with Windows. If the bsod continues consider removing to test.

Post any new dump files
 


Zalthoria

Well-Known Member
#10
There was another BSOD between the last post and your reply. ill just attach it whilst i follow your steps
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#11
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000a8afd, fffff8800c763d50, 0}

Probably caused by : win32k.sys ( win32k!xxxWindowHitTest+51 )

Followup: MachineOwner
Hi,
follow my instructions above.
Code:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
If after making the above changes you still get a bsod please test your RAM
Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
You must test for at least 12 hours unless it becomes obvious there is a problem straight away (you'll see errors outlined in red.
Memtest86+ - Advanced Memory Diagnostic Tool
 


Last edited:

Zalthoria

Well-Known Member
#12
Yet another Crash. Done everything except memtest86+. When i try to boot to my usb drive(with memtest installed) it says no boot files found
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#13
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff680202de6f8, 0, fffff80002ec5bdb, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )

Followup: MachineOwner
Done everything except memtest86+
You need to run Memtest86 as explained above. Have you tried running Memtest86 off disk? Also are you sure you installed it correctly on the thumb drive?
You need the download arrowed:
memtest86.jpg
 


Last edited:

Zalthoria

Well-Known Member
#14
yeap i installed that exact version. Unfortunately i do not have access to cds at the moment.
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#15
You can test the RAM another way. This involves removing the RAM apart from one stick. Use the machine and see if it blue screens, if it does the take the stick out and try another. Your looking for a stick which doesn't bsod meaning that it isn't faulty.
 


Zalthoria

Well-Known Member
#16
i think I will try to get memtest running. removing a ram stick n testing one by one is gonna be a terribly long and obtrusive process. so i will try to avoid that.
But as of this point it looks like a ram issue?
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#17
But as of this point it looks like a ram issue?
Yes. Read my earlier posts especially post #7
 


Zalthoria

Well-Known Member
#18
Okay ive managed to get memtest working. Will report back jn aprox 12 hrs
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#19
That's great! Good luck with the test.
 


Zalthoria

Well-Known Member
#20
Currently 8 hours in, 4 passes completed and no issues reported. I might head to bed soon and that might mean the test might run till something like 16 - 20 hrs. Is that okay?
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.