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 - "Probably caused by : Rt64win7.sys ( Rt64win7+1dd7e )"

07 Mar 2017   #1
MidwestAtty

Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
BSOD - "Probably caused by : Rt64win7.sys ( Rt64win7+1dd7e )"

All,

I have been experiencing BSODs overnight, while logged off. I installed WINDBG, and got the following crash dump. Also, I downloaded all of the symbol files, and pointed WINDBG to the location, but I am getting symbol file errors, as shown.

After WINDBG noted that it was likely Rt64win7.sys causing the problem, I installed a new set of drivers from Realtek. No dice. Thanks for any help!

************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\symbols
Symbol search path is: C:\symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23572.amd64fre.win7sp1_ldr.161011-0600
Machine Name:
Kernel base = 0xfffff800`03219000 PsLoadedModuleList = 0xfffff800`0345b730
Debug session time: Tue Mar 7 05:06:33.936 2017 (UTC - 5:00)
System Uptime: 0 days 19:25:23.447
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
Probably caused by : Rt64win7.sys ( Rt64win7+1dd7e )


My System SpecsSystem Spec
.
07 Mar 2017   #2
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

Hello and welcome MidwestAtty now can you please follow this
Now before we can help we do need to know what is in your machine so please do this System Info - See Your System Specs
or either enter the specs of your system in your forum profile the specs will appear when we click on that little box bottom left of the post screen it is for me the preferable option as it is easy. As you may appreciate it is very hard when you donít know what one is working with for example a diesel or petrol engine.
*(pretyped to save time)

and then follow these please
Dump Files - Configure Windows to Create on BSOD
&
Blue Screen of Death (BSOD) Posting Instructions

Now from first look that error / dump is related to an Ethernet connection namely the Realtek device but until we have more info on the dumps and the machine it is hard to say for definite.
My System SpecsSystem Spec
08 Mar 2017   #3
MidwestAtty

Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Okay - I think I've loaded the system specs correctly. In addition, I have attached the .ZIP file to this post.


Attached Files
File Type: zip AAK-JW17-Wed_03_08_2017__85511_52.zip (1.39 MB, 5 views)
My System SpecsSystem Spec
.

08 Mar 2017   #4
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

Ok that is something to work on now and this Bugcheck below is pointing to a hard ware issue

Code:
BugCheck 1E, {0, 0, 0, 0}
Now I have to ask is this a new machine (or refurbished) , have you made any hard ware changes to it lately and what if you have before we start testing the components.

Now amongst the dump files in the event viewer stuff I found a reference to McAfee now are you using that security or was it a bundled in software with the machine?? If you are not using it then please remove it using the McAfee removal tool. If you are using McAfee then (as personally I find it a piece of rubbish) would disable it or better uninstall it and use something else. There are plenty of free AV's unless you ant to go for a paid for version of one.
https://service.mcafee.com/webcenter...%3Dvb68m7yq6_4
My System SpecsSystem Spec
09 Mar 2017   #5
MidwestAtty

Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

I absolutely agree re: McAfee and rubbish. I am removing it now using their tool. After reboot, I will also be using Ccleaner to vacuum the registry more deeply.

This is a "brand new" system - I got it within the last 30 days, directly from Dell. No hardware changes or upgrades, etc.
My System SpecsSystem Spec
09 Mar 2017   #6
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

Ok MidwestAtty now before you go much further have you installed much other software on the machine? and seeing this is a new machine that MuckAfee was probably bundled with the Dell stuff - something that I wish they would stop doing but won't because it is revenue raising for MuckAfee and also helps Dell keep the cost of their machines down through some sort of sponsorship deal.

Plus before doing much else to the machine I would also contact the seller and/or Dell because such an issue should not be present on a new machine.
My System SpecsSystem Spec
10 Mar 2017   #7
MidwestAtty

Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

ICIT2LOL,

First, I ran the McAfee removal tool, then Ccleaner, so it should be all gone.

I (or my firm) has added the following to my machine:

1. TABS3, Praticemaster - Legal billing suite - very stable, generally)
2. AdiIrc - seems decent, well-rated - AdiIRC - Free IRC Client
3. MS Office 2016 - complete
4. CCleaner
5. Norton Endpoint - I'm not a fan, as it's a hog.
6. Spotify

If I cannot get this resolved in a few days, I plan to contact Dell.
My System SpecsSystem Spec
10 Mar 2017   #8
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

Ok now from that list of added stuff I think maybe the Norton may be a cause issue and I am not a fan of it at all anyway, and why on earth would they put Spotify on the machines??

The AdiIrc I see from that link is some form of internet/chat software and is a free program which I think is most unusual for a company to use.
I work for a government department and it is something they would never allow as they not allow CCleaner but I suppose it is free enterprise eh?

Now by that I am really questioning if those softwares are interfering with the system as you might never know what may have been bundled with them.

If you ant to look in the registry for any McAfee entries it is very simple and I am assuming you know how to get there you just need to look in the HKEY's LOCAL_MACHINE 7 CURRENT_USER > Software and scroll down the listing to see if there are any McAfee entries. see pic for example


Attached Thumbnails
BSOD - "Probably caused by : Rt64win7.sys ( Rt64win7+1dd7e )"-reg-entries.png  
My System SpecsSystem Spec
11 Mar 2017   #9
MidwestAtty

Microsoft Windows 7 Professional 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

ICIT2LOL,

I have full admin rights on my machine, so the ADI and the Spotify are my installs. And yes, the Norton sucks, but that's the firm's choice, not mine.

When I get back in to work on Monday, I will check for any more McAfee.

Thank you!
My System SpecsSystem Spec
11 Mar 2017   #10
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

Quote   Quote: Originally Posted by MidwestAtty View Post
ICIT2LOL,

I have full admin rights on my machine, so the ADI and the Spotify are my installs. And yes, the Norton sucks, but that's the firm's choice, not mine.

When I get back in to work on Monday, I will check for any more McAfee.

Thank you!
Ok no worries then I thought maybe those softwares had some unwanted effects to the system.

The McAfee entries if nay juts right click on them and delete the whole thing and it is always a good idea to back the registry up before one does anything in there - I do after clean installs and changing stuff in there.
Registry - Backup and Restore

Now as you have admin rights this little ditty might be of use to you
Just a little something that will make your machine a little faster and more efficient is this Optimize Windows 7
It is my bible when installing an OS on my machines and also when I am fixing friends and family machines too.
Now if you go through it slowly you will find lots of tweaks and they are all really thoroughly done by the authour Brink a fellow who is in my mind brilliant and if you need to ask questions he is just the most obliging person around.
The other thing is that you may lose some of the "bling" such as transparency (you don't have to I find it unnecessary) and all the tweaks are reversible.
If you do get stuck just post back in that tutorial and you will get help. Another bonus using this tutorial is that it helps you find your way around your machine and Windows 7!
Just one tip I would say you start with is do this Registry - Backup and Restore do this and it will save you a lot of grief if you are ever doing things in the registry and even if you don't it is a good back up to have if your system ever gets corrupted.
(pretyped to save time)
My System SpecsSystem Spec
Reply

 BSOD - "Probably caused by : Rt64win7.sys ( Rt64win7+1dd7e )"




Thread Tools




Similar help and support threads
Thread Forum
BSOD caused by "dxgkrn.sys" and "ntoskrnl.exe".
For the past two days I've been getting BSOD while playing games (been testing it on cs:go and it crashes every time after about 8min) or/and while the computer is idle. This mostly occurs while a game is open and sometimes the blue screen doesn't even come up, the pc simply restarts (which I...
BSOD Help and Support
BSOD caused by ntoskrnl.exe, also random Chrome crashes ("Oh snap")
Hello, I've just returned from my holidays and my computer startet to behave rather weird. First things I noticed was random "oh snap"-errors in Google Chrome. I updated Flash Player, tried a new Chrome profile and even reinstalled Chrome but nothing helped. Tonight I had the first...
BSOD Help and Support
BSOD after a recent BIOS update. Rt64win7.sys related
I recently got a BSOD a few minutes after I updated my BIOS. After a quick Google search it might not be related. Most results pointing to a Realtek related problem. But I am not too sure about this so I've decided to ask someone confirm. I followed the option 1 in uploading information in this...
BSOD Help and Support
BSOD Rt64win7.sys Error d1
I've been having this issue for awhile. Bluescreens at least 1-2 times daily. I'm not a novice with computers but I cannot find a solution, I've done complete reinstalls of drivers. Removed wireless card/s, but to no avail. I hope you'll all be able to help me! Regards Gunstorm.
BSOD Help and Support
RT64win7.sys BSOD crashes when PC idle
I have a PC on my network that has blue screened a few times. This has recently started happening. I appreciate any help in resolving this. Thank you
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 22:47.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App