Windows 7: BSOD's Start Again After Reinstalls of Win 7 and Updates

Pherank · 12 Nov 2012

I reformatted the hard drive and began again. Once I get to the point where Windows 7 is pretty much up-to-date with bug-fixes (over 100 of them!), and MS Office is installed, the BSOD's start up again - fast and furious. I can tell my computer has a hard time starting up cold - the hardware needs to warm up a bit before things are happy. But I'm not sure that explains why Win 7 is so undependable. Any ideas, anyone?

Arc · 12 Nov 2012

► Reinstall USB Ports drivers

Code:

fffff800`00b99648  fffff880`030a35c2 USBPORT!USBPORT_Xdpc_iSetState+0x2a
fffff800`00b99678  fffff880`030a3783 USBPORT!USBPORT_Xdpc_iSignal+0xcb
fffff800`00b996a8  fffff880`030a6f99 USBPORT!USBPORT_ReleaseEpListLock+0x21
fffff800`00b996b8  fffff880`030cb06d USBPORT!USBPORTSVC_EtwWrite+0x2d
fffff800`00b996c8  fffff880`030ce208 USBPORT!USBPORTSVC_LogEntry+0x2c
USBPORT!USBPORTSVC_LogEntry+0x2c

Right click on the My Computer icon> Select manage. It will open the computer management window.
Click on the "Device manager" in the left pane.
Expand USB Serial Bus Controller.
Right click > Uninstall them all, one by one.
When Done, restart the computer.
On restart, the necessary drivers will be auto-installed.

► Disable USB selective suspense.
USB Selective Suspend - Turn On or Off

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 6f8, fffff80002dbf415}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80002dbf415

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002cd0569 to fffff80002cd0fc0

STACK_TEXT:  
fffff880`0338cde8 fffff800`02cd0569 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff880`0338cdf0 fffff800`02ccea32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0338cf30 fffff800`02dbf415 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`033aec78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmCheckEnd+0x15


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002dbf400 - nt!PpmCheckEnd
    [ 48:58 ]
1 error : !nt (fffff80002dbf400)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

update the network driver.
First, download the network card driver from manufactuer's website.
Then reinstall the driver:

Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
Double click to expand "Network adaptors".
Right click your network card and click Uninstall.
Check "Delete driver software for this device" check box, click OK.
Restart the computer
If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

Now a suggestion, out of experience. Decision is your.
► Use Microsoft Security Essentials.
Uninstall Norton and all Symentec products using Norton Removal tool. (At least as a test, as there is no proper ground of network drivers failing).
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download and install those, and then run full system scans with both of them, one by one.

Let us know the results.

Pherank · 13 Nov 2012

Thanks for all the details, Arc. I did uninstall the various drivers, including the Network driver, and rebooted to reinstall. And then I ran the update for the Network driver.

I still experience freezing at the Windows login screen, but no crashing. And no recorded errors. Running the "sfc /verifyonly" command finds no problems.

Note that I ran Memtest86 a couple of weeks ago and no problems were found. I've never run into problems with hardware diagnostic tests. I think the PC itself is still solid. But Windows is its usual unstable self.

I still have NIS running on my PC. I suppose the smart thing to do now is to unplug from the LAN, uninstall NIS and try shutting down and leaving the PC off for a while, then rebooting and see if the PC runs more smoothly. Rinse and repeat until sure everything runs great without NIS.

Arc · 14 Nov 2012

One more thing you may plan ... re-seat the RAM modules and SATA ports.

Windows 7: BSOD's Start Again After Reinstalls of Win 7 and Updates

BSOD's Start Again After Reinstalls of Win 7 and Updates problems?