IRQL_NOT_LESS_EQUAL, ntoskrnl.exe, BSOD, Win 7, after fresh Win7 install

Toggle sidebar Toggle sidebar
H

Hobogaragesale

Distinguished
Jul 5, 2010
16
0
18,510
System specs:
Win7 pro x64
p8z77 V-pro Bios 2104
16 gb corsair CML16GX3M4X1600C8
i7 3770k
gtx 1080

I recently purchased a gtx 1080 and wanted to do a clean windows install. I had absolutely 0 stability problems and haven't seen a BSOD in years prior to re-installing windows yesterday. I'll include my minidump files down below.

Since re-installing Win 7 pro, I've had pretty frequent BSODs and system lock-ups. I'm almost 100% sure it is not hardware related (I had the card installed and working fine for a week prior to this re-install).

I am about 99% sure it is driver related. I think the problem has to do with either network drivers or usb drivers. BSOD viewer flags the ntoskrnl.exe as the culprit.

I installed win7, installed my MB LAN driver (from manufacturers website), let windows update do its thing then went about installing a few drivers from my motherboard manufacturers website:
The Chipset driver
AS media SATA driver
USB 3.0 driver

I then updated the LAN driver because the intel driver update utility told me to (from version 17300 to 22 something). I had frequent disconnects and reconnects so I uninstalled the 22version and reinstalled the version from my motherboard manufacturers website.

Notable information:
I did a more lazy Win7 and driver install/windows update before this install the day before and I had all sorts of windows update errors and more frequent BSODs (randomly, upon file transfers from my external, etc.), but today I completely re-installed windows again with the method described above (no windows update errors, BSODs are definitely less frequent)

I have experienced two episodes of my computer locking up, cpu going to 100%, requiring hard reset while trying to write this post.

There are ! points in device manager next to 2 entries for Universal Serial Bus (USB) Controller. Right clicking and letting windows search for updates does not find anything.

Here are my minidumps and another error log file and a cpu-z text log about system information hopefully this google drive link works: https://drive.google.com/open?id=0B-z9iovHqQIIdTZlRDd3TE5heE0

My system was 100% stable prior to this windows re-install.

Please let me know if you need additional information.

Thank you for your time and consideration.

JP






 
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
overall, I would remove the BIOS overclock of the CPU then run memtest to check the memory timings.
(or reset the BIOS to defaults)

---

well there is some type of problem with your
Intel(R) 82579V Gigabit Network Connection driver
\SystemRoot\system32\DRIVERS\e1c62x64.sys Fri Aug 10 15:44:15 2012

you can update from your motherboard website or directly from intel:
https://downloadcenter.intel.com/
(just run their scanner)

the error that caused the bugcheck was a failure in mapping physical ram to locations in your pagefile.sys. the table became corrupted.

I would run the intel update software and see if it updates any intel chipset drivers.
I might move the data cable from to a different SATA port on a different controller.

I would run crystaldiskinfo.exe and read the smart data from the drive to see if the drive is just generation errors.

i might delete the hidden c:\pagefile.sys and create a new one
(disable the system virtual memory, reboot, delete the old pagefile.sys and then turn the virutal memory system back on to create another one)

you have one bad driver
\SystemRoot\system32\DRIVERS\xusb21.sys Thu Aug 13 15:10:17 2009

you should remove it and use the usb22.sys driver
(most likely not the cause of this problem)

The debugger thinks you have a memory corruption.
I would reset the BIOS to defaults, you have kind of a strange CPU speed set.
Processor Version Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
Current Speed 3621MHz

the address the debugger did not like, looked like a valid kernel address but maybe there is a bad bit set (i can not tell, at least it is not clearly invalid)



 
Upvote 0 Downvote
H

Hobogaragesale

Distinguished
Jul 5, 2010
16
0
18,510


I ran the intel update tool, it only flagged my network drivers for update, so I went ahead and updated to the latest version, now my internet is cycling on and off over and over and over like it did before when I updated to this version from the one listed on my MB manufacturers website. Also, every-time I run the update tool it flags the network driver for update and if I have version 17.3 installed it tells me I'm running version 12 something... so not really sure what is going on there but now my internet turns off and back on every 15 seconds or so... although the longer I keep my computer on the more stable it appears to be but every so often it cycles on and off still.

I was curious about my clock speed too... not sure how that got like that, I went in to the bios and reset all the defaults, I think it is a normal 3.5 now.

Any advice on how to switch from usb21.sys to USB22.sys? Google is unhelpful with that one.

I'll go ahead and shut down and check my sata cables/switch them around.

Thanks again.
 
Upvote 0 Downvote
H

Hobogaragesale

Distinguished
Jul 5, 2010
16
0
18,510
Well, I reverted my network driver no more connection cycling, removed xusb21, added xusb22.

Found that I can precipitate the BSOD by transferring a 21gb folder from my external to my SSD. I had this problem the first time I re-installed windows the previous day. Found that if I installed windows, ran windows update and did not install any other drivers and initiated the same folder transfer, that it worked (albeit much more slowly). Now I'm back to it BSOD'ing every time (and I believe it BSODs at the same place - as in it BSOds once it reaches a certain point in the transfer).

However, I did find that if I delete the pagefile.sys like you said, and then increase it in size (from 16gb to 22gb - which is pretty obnoxiously large...) that I can make it a lot further in to the folder transfer but I still get the same BSOD... it happens at the same place every time still by the way, but farther in. I know you people are thinking it is probably my external or my memory... but I have run a memtest which cleared fine. I tried to chkdsk my external but it BSOD'd.... I'll go try it on another computer and make sure the external works but I'm really still sure this is a driver/software problem... any other ides would be helpful thanks.

EDIT: CrystaldiskInfo says the health of drives are: "good"
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
I think intel may have changed the defaults for their network drivers for sleep functions.
in the windows 7 days the all of the sleep functions were off by default. When window 8.x shipped sleep functions were turned on by default. It exposed a lot of problems that required BIOS updates to fix or you have to go into control panel find the device and disable the sleep functions of the device. (low power link states)
the devices tend to go to sleep, but not wake back up when you start to use the machine. (most often you update the BIOS and driver for the device or disable the function to work around the problem)


Xbox 360 Wireless Receiver driver
I think if you download the windows 7 64 bit you should get the update that came out in 2012
it will work for the updated usb 2.2 specifications that your BIOS should conform to.

the old xbox driver will corrupt data being transferred via usb 2.x



 
Upvote 0 Downvote
H

Hobogaragesale

Distinguished
Jul 5, 2010
16
0
18,510


Thank you for your time and help John, I really appreciate it.

As a last ditch effort (before another full windows re-install) I attempted one of my classic computer cures. I went ahead and turned off my system, unplugged it, and pulled out the little nickel battery and cleared the CMOS... booted it up and was able to complete the file transfer from my external without BSOD. I'm hesitant to declare the thing "fixed" and I'll need to continue with some stability testing but so far I cannot reproduce the issue.

I'm thinking something got screwy with the memory/processor BIOS values... I'm not sure how I went from stable to not with a fresh install but clearing everything with the CMOS clear seems to have fixed the BSOD's for now. I'll re-update if I experience more problems. Thank you again for your time and assistance.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom