Solution
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
the...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Well have you changed anything in regards to settings? I would turn all your settings back to their defaults. Something wasn't right because you had all those pagefiles so whatever it is you had changed you need to return to default.
When was the last time you did a clean install of Windows 7?
Personally I'd re-install, add my drivers and see how the machine performs. If all is ok start adding your third party apps you like to run but test after installing each one.
When was the last time you did a clean install of Windows 7?
Personally I'd re-install, add my drivers and see how the machine performs. If all is ok start adding your third party apps you like to run but test after installing each one.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff84351502314, 10, fffff84351502314, 2}
Could not read faulting driver name
Probably caused by : NETIO.SYS ( NETIO!NetiopIoWorkItemRoutine+3c )
Followup: MachineOwner
this bugcheck can be caused by numerous things including hardware. As we have already tested a few things let's try the driver verifier although if you turn it on and get a bsod at boot you'll have boot into safe mode to turn it off. We just need to see if we can trap the driver which is possibly corrupting the system. Use the guide below and post any resulting dump files:
How do I fix a Blue Screen in Windows using Driver Verifier?
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2000, fffff80012bb8098, 0, 4f4e4558}
*** WARNING: Unable to verify timestamp for bflwfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys
Probably caused by : bflwfx64.sys ( bflwfx64+8098 )
Followup: MachineOwner
well it's pointing to the Killer Wireless driver which is slightly out of date. Try updating to the latest version. If this issue continues it may be a possibility that something is wrong with the component itself.
bflwfx64.sys Fri Jun 19 20:53:10 2015: Bigfoot Networks Bandwidth Control Wireless Driver
Link Removed
You'll need to turn off your Anti-virus to install the above driver correctly.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Wireless/network driver it's just part of the same driver. Actually if you bsod again you could try breaking the wireless driver by renaming it to .old instead of .sys. Make sure you back the driver up (make a copy) before doing so.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2000, fffff801fa4080b0, 0, 4f4e4558}
*** WARNING: Unable to verify timestamp for bwcW10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for bwcW10x64.sys
Probably caused by : bwcW10x64.sys ( bwcW10x64+80b0 )
Followup: MachineOwner
well this time it's caught a slightly different driver although it's still part of the Killer Network suite. If I'm correct it relates to the Killer Bandwidth control driver.
Has this bsod been present since you first purchased the motherboard?
The motherboard is relatively new correct?
Have you tried the 'standard' Killer drivers which basically means the software suite isn't included?
Link Removed
Similar threads
- Solved
- Replies
- 16
- Views
- 4K
- Solved
- Replies
- 12
- Views
- 3K
- Solved
- Replies
- 1
- Views
- 2K
- Replies
- 1
- Views
- 1K
- Replies
- 2
- Views
- 3K