New
#1
BSOD after computer is loaded for around 3 minutes. ntoskrnl.exe
I have had an ongoing issue with my computer ever since I got it over a year ago. I get BSOD 'randomly' when I turn on my computer. It can happen each month or it may take a rest and not do it for three months. It will crash hard and often and then be perfectly fine. Every time you restart the computer it will BSOD until you can shut the computer down properly. Then I just start the computer up after a time and it's totally fine. It only blue screens right when windows loads or when I first load a browser (Chrome and IE).
I've checked the following:
RealTemp - all temperatures are fine.
WD Diagnosis - no errors on my hard drive
MemTest (with Windows loaded, not on boot) - no errors to report
No viruses found with Microsoft Security Essentials (and using others)
I've done Check Disk and looked into the errors and I get nowhere.
Here is the latest dump file:
Symbol search path is: src*c\symbols*http://msdl.microsoft.com/download/s...wnload/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e63000 PsLoadedModuleList = 0xfffff800`030a66d0
Debug session time: Mon Oct 21 18:50:01.932 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:23.150
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002edbeb0, fffff880025c9760, 0}
Probably caused by : win32k.sys ( win32k!xxxRealSleepThread+257 )
Followup: MachineOwner
---------
The following is from BlueScreenView. It recorded the crashes. I have edited it taking away the file names and useless info. I'm hoping it will help.
SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02edbeb0 fffff880`025c9760 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0
PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff880`05867938 00000000`00000001 fffff800`0253e6f6 00000000`00000002 wmiacpi.sys wmiacpi.sys+2bb4938 x64 ntoskrnl.exe+75bc0
DRIVER_CORRUPTED_EXPOOL 0x000000c5 fffff800`13043980 00000000`00000002 00000000`00000001 fffff800`02ff80f8 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0
PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff880`0ab91938 00000000`00000001 fffff800`0313d6f6 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0
KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 nvlddmkm.sys nvlddmkm.sys+5e17c0 x64 ntoskrnl.exe+75b90 C
NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`025d31a8 fffff880`025d2a00 fffff880`012316c7 Ntfs.sys Ntfs.sys+186c7 x64 ntoskrnl.exe+75bc0
DRIVER_VERIFIER_DETECTED_VIOLATION 0x000000c4 00000000`00001001 fffff880`0178a160 fffffa80`0a3428b0 00000000`00000000 tcpip.sys tcpip.sys+18a160 x64 ntoskrnl.exe+75bc0
Last edited by ConquerorG; 22 Oct 2013 at 08:57.