random BSOD while gaming

D

dmonger11b

New member
Joined
Nov 27, 2013
Posts
3
Windows 7 64bit
Originally bare bone drive
Retail version
Built system less than 1yr ago
CPU= I5 3750 3.4GHZ
GPU= ASUS Geforce 650TI
MOBO= ASUS P8 Z77-V LK
PS= Corsair CX600 650 watt

Built myself no manufacturer
 

Attachments

Hi Cal (user is a friend of mine),

In regards to the perfmon, it looks fine. Not seeing anything out of the ordinary. Your jcgriff2 output folder however is empty and contains no dump files, this may be due to a few things. First off, manually navigate to C:\Windows and look for a Minidump folder. Is there one? If so, manually zip up and attach any dump files in that folder. If not, check the Windows directory instead for a file called MEMORY and it'll be a .DMP extension. If there is one of those as opposed to a Minidump folder, zip it up and upload it to a 3rd party hosting site such as Mediafire, Skydrive, whatever you'd like as it'll be too large to attach here.

If there aren't ANY (Minidump folder or MEMORY file), ensure all of this is set:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small memory dump is selected and ensure the path is %SystemRoot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Regards,

Patrick
 
Great, thanks. Do the following for me so next time you crash, it's not a huge Kernel -

Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small memory dump is selected and ensure the path is %SystemRoot%\Minidump.
Click to expand...

This dump is actually corrupt, unfortunately. This means we cannot analyze much and things like the modules list, etc, are not available. All we can salvage is the bug check which is DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1).

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

The good thing is given this is the bug check we're seeing, it's most likely a device driver causing corruption and not a hardware issue. We'll see when we can actually look at a dump, though :grin1:

-------------------------------------------------------------------------------------------

Unable to get current machine context, NTSTATUS 0xC0000147

^^ Usually this appears in crash dumps when a page file is missing (or the dump is just corrupt). In addition to the Small memory dump change above, make sure of the following:

Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.
Click to expand...

Once you have changed to Small memory dump and ensured the page file is set, the NEXT time the system blue screens, rather than generating a MEMORY.DMP in C:\Windows, it will be generated in C:\Windows\Minidump

That you can attach here and won't need to use 3rd party hosting sites.

Regards,

Patrick
 
Hi Cal,

The attached DMP file is of the ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc) bug check.

This indicates that an attempt was made to execute non-executable memory.

1. Remove and replace AVG with Microsoft Security Essentials for temporary troubleshooting purposes:

AVG removal tool - AVG | Download tools and utilities

MSE - Microsoft Security Essentials - Microsoft Windows

2. Uninstall the Asus Ai Charger software from Control Panel > Uninstall a Program.

3. RTL85n64.sys - Mon Oct 02 22:36:17 2007

^^ Realtek 8185 Extensible 802.1b/g driver, dated from 2007. A bit old, update here - Realtek

I am also keeping an eye on the Asus PCProbe software... it's known to be buggy.
Code: 
0: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3502

^^ Stock is 3.4GHz but it jumped to 3.5 here at the time of the crash. This may be HyperThreading mixed with SpeedStep, but just in case, ensure the system is at full defaults and nothing is overclocked.

Regards,

Patrick
 
The file is actually a Minidump. Did you check here - C:\Windows\MEMORY.DMP

Anyhow, please follow Patrick's advice.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top