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 while Patching ArcheAge, caused by driver ntoskrl.exe

30 Apr 2015   #181
HikariChino

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

It worked! I'm all fully updated.


My System SpecsSystem Spec
.
30 Apr 2015   #182
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

Please post the CheckSUR log so we can see what's happened!
My System SpecsSystem Spec
30 Apr 2015   #183
HikariChino

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

Here you go.
My System SpecsSystem Spec
.

30 Apr 2015   #184
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

Egad! I am totally shocked! - but very happy

Glad it seems to have worked for you.

Good luck!
My System SpecsSystem Spec
30 Apr 2015   #185
HikariChino

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

So should I try to play my games now?
My System SpecsSystem Spec
01 May 2015   #186
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

Why not
My System SpecsSystem Spec
02 May 2015   #187
HikariChino

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

Well this happened.
My System SpecsSystem Spec
02 May 2015   #188
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff880009f4b70, 0, 0}

Probably caused by : intelppm.sys ( intelppm!MWaitIdle+19 )

Followup: MachineOwner
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009ec180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
warning   Warning
If you're overclocking your system, revert back to stock clocks now.

Note   Note
Test the system once the overclock is removed before continuing with the steps outlined below.





BSOD while Patching ArcheAge, caused by driver ntoskrl.exe ONE BSOD while Patching ArcheAge, caused by driver ntoskrl.exe
 CPU TEST

Run Prime95 to stress test your CPU. Hardware - Stress Test With Prime95

warning   Warning
Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them.





BSOD while Patching ArcheAge, caused by driver ntoskrl.exe TWO BSOD while Patching ArcheAge, caused by driver ntoskrl.exe
 RAM TEST

Run MemTest86+ to analyse your RAM. RAM - Test with Memtest86+



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.[/note]




BSOD while Patching ArcheAge, caused by driver ntoskrl.exe THREE BSOD while Patching ArcheAge, caused by driver ntoskrl.exe
 GPU TEST

Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

Note   Note
Run Furmark for around 30 minutes.

warning   Warning
Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them.
My System SpecsSystem Spec
04 May 2015   #189
HikariChino

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

Memtest ran fine, here are the dump when I tried the run the furmark and prime.
My System SpecsSystem Spec
04 May 2015   #190
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

If you are overclocking anything, set everything back to defaults.

This is your Furmark BSOD

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {200139, 9, 0, fffff88005bcbf71}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+19cf71 )
Followup: MachineOwner
That is the Graphics Driver and this is the one you have now

Code:
nvlddmkm
start             end                 module name
fffff880`05a2f000 fffff880`0643a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Mar 13 10:39:56 2015 (550304CC)
  ImageSize:        00A0B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4  CheckSum: 009CE879
The one from prime was pretty unspecific


Code:
    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: 00000000000406f8
Arg4: fffff8a00315c130
Go into BIOS and look at what your Sata Controller is set to (IDE, AHCI or RAID) and remember it. Then set Optimized Defaults, make sure your ram timings, frequency and Dram Voltage is set to Manufacturer's Specs, set the sata controller to what mode it is in right now (or you won't be able to boot) then set your boot order, save and exit. Change nothing else.

Reinstall your graphics drivers, installing only the Graphics Driver and PhysX using this tutortial
NVIDIA Drivers - Avoid Problems

Then please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
My System SpecsSystem Spec
Reply

 BSOD while Patching ArcheAge, caused by driver ntoskrl.exe




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Bsod caused by USB3 driver
I have a weird problem with USB 3 drivers I think. This is my configuration: Motherboard: Gigabyte GA-B75M-D3V Cpu : Intel Core i5 3470 Ram : 8 Gb Corsair 1333 Mhz Video: Gigabyte GeForce GTX 660 2048MB DDR5 OC version Hdd : Western Digital 640 GB 7200 Rpm Case: Segotep SG-Z2
BSOD Help and Support
BSOD - ntoskrl.exe problem, error 0x0000009f
Hi Firstly, many thanks for running this amazing forum! Judging by the number of posts and responses you give, this is a vital service! So... I assembled PC a few weeks ago using a second hand intel motherboard and i3 but all all else new bits and all seemed ok for several weels but a couple...
BSOD Help and Support
BSOD caused by driver ndis.sys
I have rebooted into safe mode without networking, deleted all drivers for my RealTek network card (currently running Realtek PCIe GBE Driver Win7 7067 01/22/2013) and restarted the computer several times. This does not seem to alleviate the problem. I have spent hours researching this and can't...
BSOD Help and Support
BSOD caused by unknown driver?
I've been dealing with BSOD issues with my laptop for almost a year now, supposedly it was a hard drive issue and I had that replaced through my warranty in December. BSOD stopped... for about 36 days, just long enough for my warranty to have expired 15 days earlier. It's only gotten worse since...
BSOD Help and Support
BSOD 0D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL in ntoskrl.exe and ntkrnlmp.exe
Over the last month, whilst the PC is idle (mostly overnight) I have had a few system hangs/crashes. The specific crashes that have resulted in a system Dump all point to the above modules as the offending elements I have, I believe followed the sticky detailing the process and attach the...
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 19:23.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App