Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Rash of BSoDs - What Could Be the Culprit Here?

- - - - -

  • Please log in to reply
40 replies to this topic

#1
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

Hey guys,

 

XP64 has usually been a very stable and gentle operating system, with the lowest track record of BSoDs in an OS I've ever had. My computer woes tend to be hardware rather than software related; I only had two BSoDs last year, in fact, and both were explicitly caused by XP64 running out of free pages (NO_PAGES_AVAILABLE). A major sign I need to overhaul the RAM given how much multitasking I do.

 

Starting on the 4th of March this year, though, something changed. I've had seven BSoDs since then and now, with the seventh one happening just recently, at the top of the hour (going by my post's timecode). Here's what WhoCrashed has to say about them, starting from the earliest to the most recent:

 

On Tue 3/4/2014 5:13:15 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030414-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xA009B)
Bugcheck code: 0xA (0x6DF9276A1F8, 0x2, 0x1, 0xFFFFF80001036765)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Google query: win32k.sys Microsoft Corporation IRQL_NOT_LESS_OR_EQUAL

 

This was actually two BSoDs, but WhoCrashed only recorded one, because I hadn't had Windows XP64 to not insta-restart. The computer restarted, tried to boot to Windows, BSoD'd and restarted again. Forgot to reset that option after my previous main drive died. The issue resolved itself, weirdly enough, when I did.

 

On Fri 3/14/2014 1:22:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0xA (0xFFFFFAE053001F9A, 0x2, 0x0, 0xFFFFF800010359A2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

This one happened after trying to download the month's round of Windows Updates.

 

On Fri 3/14/2014 1:34:13 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031314-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0x109 (0xA3A03A38293AC51D, 0x0, 0x1ED647BB8F24A122, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
 

This CRITICAL_STRUCTURE_CORRUPTION happened after the previous crash, at which I restarted using Last Known Good Configuration. Several things went wrong right away after booting to Windows: Browsers wouldn't stay open, crashing or closing themselves immediately. Opera kept reporting an error in opera.dll. The Windows Update didn't install, as XP replaced the "Shut Down" with "Shut Down and Install Updates" at the shut down menu. Trying to allow XP64 to do this got me the BSoD, though the actual message wasn't an error code, but "Modification of system code or a critical data structure was detected."

 

I have NEVER seen that one before, not in all my years of using Windows machines. This hasn't happened again after I ran memtest86+, and (later on) dusted my computer out.

 

On Mon 3/17/2014 4:48:40 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031614-01.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0xB9C0E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF97FFD0E1C0E, 0xFFFFFADF8A4F3150, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nv4_disp.sys .
Google query: nv4_disp.sys SYSTEM_SERVICE_EXCEPTION

 

This one happened while Command and Conquer: Tiberian Sun was running in the background.

 

On Sat 3/22/2014 1:05:53 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032114-01.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0xB9C0E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF97FFD0E1C0E, 0xFFFFFADF44382850, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nv4_disp.sys .
Google query: nv4_disp.sys SYSTEM_SERVICE_EXCEPTION

 

This one happened again while playing Command and Conquer: Tiberian Sun, this time while attempting to alt+tab out of the game while it was running.

 

On Wed 3/26/2014 4:04:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032514-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0x50 (0xFFFFFADE959A2D70, 0x1, 0xFFFFFADF8F6B9132, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

Though WhoCrashed says ntoskrnl.exe is the likely culprit, the actual BSoD screen referenced nv4_mini.sys. The BSoD happened while playing Renegade-X, after a match ended and right in the middle of a map change. The current build of the game (as of this post) doesn't transfer to a loading screen when map changing on a server. You get the end-of-match leaderboards and voting, then the scenery goes black as it switches to the new map. That's when the BSoD happened, with hanging sound.

 

On Tue 4/8/2014 2:01:36 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040814-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0x50 (0xFFFFFADE9CEB67A8, 0x1, 0xFFFFF800011A9B28, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

This one happened while I was checking Command and Conquer 3: Tiberium Wars for something. I clicked on a menu option (replays menu), then tried to click back to the main menu. The BSoD instantly happened, again with looping, hanging sound.

 

I highly suspect that installing the Open Beta of Renegade-X has something to do with this. Correlation does not equal causation, I know, but the timing still leaves me suspicious as it was the only new program installed right around the time that I started having these problems (Renegade-X's Open Beta 1 was released on February 26, and I installed it around the beginning of March). Furthermore, there is a known issue I and a number of players experienced first hand, in which the uninstaller for Open Beta 1 deleted the entire Start Menu for the current user--a problem that affected not just XP64, but 7 and 8 as well. It leaves open the question as to whether Renegade-X caused some damage to the OS somehow ...

 

That unofficial DX10 patch I mentioned installing in another thread was done way after these problems started. I installed that one on March 28, and the System Restore suggested to me fixed all issues related specifically to that.

 

Initially an IT friend of mine suspected hardware failure: either the hard drive(s), RAM, or malware (though he ruled out malware and thinks hardware issues are more likely due to the erratic nature of these BSoDs). I haven't ruled out that out entirely; so far I've only been able to verify the integrity of my RAM via MemTest86+, as five passes turned up no errors. I haven't yet been able to verify the integrity of my hard drives, however.

 

EDIT: Oh, I should also add that in the case of the crashes where I referenced those other Command and Conquer games (Tiberian Sun, Tiberian Wars), I was doing heavy multitasking in both cases. Both Opera and Firefox were open, with quite a few tabs between them. These are usual computing habits for me, and as mentioned earlier, they haven't caused BSoDs like this before (save for those two from last year where XP64 had absolutely no memory left to continue running).

 

What do you guys think? What might be the culprit here, and what do you think I could do to fix it?


Edited by TrevMUN, 08 April 2014 - 09:37 AM.



How to remove advertisement from MSFN

#2
5eraph

5eraph

    Update Packrat

  • MSFN Sponsor
  • 1,333 posts
  • Joined 04-July 05
  • OS:XP Pro x64
  • Country: Country Flag

Donator

Had similar problems after installing nVidia GeForce 334.89 on 2014-02-24. Reverting to 332.21 solved the problem. Now using 335.28 (latest current driver) with no problems.

Apparently, nVidia has removed the XPx64 334.89 driver from its site. The link I saved for it now points to another driver (335.04 beta).

Edited by 5eraph, 08 April 2014 - 09:53 AM.


#3
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

You were getting a lot of the same BSoDs and error codes?

I'm currently using nVidia GeForce 335.28, which I updated to from 310.90 (I believe) in the middle of this rash of BSoDs. After the CRITICAL_STRUCTURE_CORRUPTION incident, in fact.

 

Would doing a clean install of 335.28 address the problem, you think?


Edited by TrevMUN, 08 April 2014 - 09:57 AM.


#4
5eraph

5eraph

    Update Packrat

  • MSFN Sponsor
  • 1,333 posts
  • Joined 04-July 05
  • OS:XP Pro x64
  • Country: Country Flag

Donator

Possibly. Completely uninstall the current driver, then reinstall.

#5
5eraph

5eraph

    Update Packrat

  • MSFN Sponsor
  • 1,333 posts
  • Joined 04-July 05
  • OS:XP Pro x64
  • Country: Country Flag

Donator

I wrote these notes to myself at the time for future reference:
 

Consistently causes SYSTEM_SERVICE_EXCEPTION BSoD in NV4_DISP.DLL when seeking within YouTube videos with hardware acceleration enabled. Has caused same error when ALT-TABbing into Dead Space 1, max settings.

BSoDing with DS1 was the deal-breaker, forcing me to revert to driver 332.21 which never blue screened. Bearing in mind that I've never tried 332.21 with Dead Space, it needs testing.

I have disabled driver update checking in nVidia GeForce Experience for now.



http://msdn.microsof...9(v=vs.85).aspx

Quote: This error has been linked to excessive paged pool usage and may occur due to user-mode GRAPHICS DRIVERS crossing over and passing bad data to the kernel code.



#6
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

Hm. Interesting ... So, the driver update might account for the SYSTEM_SERVICE_EXCEPTION BSoDs, since I started getting those when I updated the drivers after the CRITICAL_STRUCTURE_CORRUPTION BSoD? Would it likely be responsible for the PAGE_FAULT_IN_NONPAGED_AREA BSoDs as well?

 

I can't help but wonder if installing Renegade X may have screwed with the drivers in some way, causing this whole mess in the first place. After all, I'd been using 310.90 since January of last year, when I had to make a fresh install of XP64 due to a dying hard drive. I hadn't encountered issues until I installed and started playing Renegade X's OB1 last month.

 

Question: Would telling nVidia's driver installer to do a clean install be functionally equivalent to a complete uninstall and reinstall, or is this something I have to do manually? If so, how would I go about doing that?



#7
5eraph

5eraph

    Update Packrat

  • MSFN Sponsor
  • 1,333 posts
  • Joined 04-July 05
  • OS:XP Pro x64
  • Country: Country Flag

Donator

Haven't tried the "clean install" option. Before trusting the Experience application to update my driver, I would always remove the existing driver with "Add or Remove Programs" and reboot before installing the latest one.

Haven't played Renegade X, so I don't know if it is to blame. Often graphics drivers must be tweaked to work with the latest games; and since Renegade X is still in beta, it's possible that nVidia may need to work on its drivers to get the game to work better.

~IF~ reinstalling the latest driver still causes problems I may have another solution for you to try. But for the sake of the scientific method, let's try one solution at a time.

#8
5eraph

5eraph

    Update Packrat

  • MSFN Sponsor
  • 1,333 posts
  • Joined 04-July 05
  • OS:XP Pro x64
  • Country: Country Flag

Donator

Hm. Interesting ... So, the driver update might account for the SYSTEM_SERVICE_EXCEPTION BSoDs, since I started getting those when I updated the drivers after the CRITICAL_STRUCTURE_CORRUPTION BSoD? Would it likely be responsible for the PAGE_FAULT_IN_NONPAGED_AREA BSoDs as well?


Thought that I might address this separately. The bad nVidia driver definitely causes SYSTEM_SERVICE_EXCEPTION for me, but I received no others. I suppose it's possible that it could cause the others, but I have no way of proving it. The best way to proceed is to eliminate the problem we know first, then perhaps we can work on the rest.

#9
HarryTri

HarryTri

    Member

  • Member
  • PipPip
  • 212 posts
  • Joined 17-August 12
  • OS:Windows 8 x64
  • Country: Country Flag

Also an sfc/scannow in case some system file(s) is/are corrupt could be recommended.


I always love Windows XP!


#10
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

I was wondering about that, actually: If I do an sfc /scannow and it results in a number of files getting copied over from the install CD, how does that affect any that have been patched by Windows Update? Or, I guess I should say, how do Windows Updates and hotfixes mesh with using sfc /scannow?



#11
HarryTri

HarryTri

    Member

  • Member
  • PipPip
  • 212 posts
  • Joined 17-August 12
  • OS:Windows 8 x64
  • Country: Country Flag

The Windows Update files are stored in the "dllcache" folder and sfc can find them there, if you have the "dllcache" untouched there won't be any problems. The same goes for the Service Pack files and the same named folder.


I always love Windows XP!


#12
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

Alright. I'll give it a look-see as the next step.

 

XP64 finally decided it was done with downloading the last official updates, so I took the restart after installing them as an opportunity to get the nVidia drivers sorted out. I manually uninstalled them from Add/Remove Programs and restarted.

 

... Only, XP64 automatically reinstalled drivers for them once I had restarted: Version 310.90. It must have done that because the installer for that version is still in an Installation Files folder I keep on C drive, but I had downloaded 335.28's installer in preparation for this and had it in my Downloads folder of My Documents ...

 

Well, I decided to let nVidia Experience re-download the latest drivers and had it perform a Clean Install. I'll see if that changes anything.

 

If it doesn't, I'll need to figure out how to keep XP64 from automatically installing the older drivers when trying this again. Move 335.28 into the Installation Files directory and temporarily move the older installer elsewhere?



#13
JodyT

JodyT

    Member

  • Member
  • PipPip
  • 276 posts
  • Joined 05-April 11
  • OS:none specified
  • Country: Country Flag

Check the folder \windows\system32\etc\drivers (I think that's the full path) and see if the nVidia driver that keeps reinstalling is nested in there.



#14
oldskool

oldskool

    Newbie

  • Member
  • 46 posts
  • Joined 09-April 14
  • OS:2003 x64
  • Country: Country Flag

Download Memtest86 and make a boot disk.

 

Pull all of your ram out and test the ram in pairs until the all the ram is tested.  Memtest86 will let you know if you have bad ram, To me it sounds like you have a bad stick of ram.  Page faults are memory issues.  After you ran memtest 86 on your ram the way I said if it passes than your video card is bad.  If your video cards memory is bad no amount of driver is going to fix that.  so its just bad if memtest86 passes all your sticks of ram like i said.


Edited by oldskool, 10 April 2014 - 04:11 PM.


#15
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

Check the folder \windows\system32\etc\drivers (I think that's the full path) and see if the nVidia driver that keeps reinstalling is nested in there.

 

I poked around and nv4_mini.sys in the drivers folder. The curious thing is, its Date Modified information says Sunday, March 09, 2014, 3:35:55 PM, right in the thick of all those BSoDs I was getting last month. However, I had updated the drivers on March 14th, not the 9th ... and given its modified date, it doesn't look like it was recently put there by the uninstall/reinstall.

 

 

Download Memtest86 and make a boot disk.

 

Pull all of your ram out and test the ram in pairs until the all the ram is tested.  Memtest86 will let you know if you have bad ram, To me it sounds like you have a bad stick of ram.  Page faults are memory issues.  After you ran memtest 86 on your ram the way I said if it passes than your video card is bad.  If your video cards memory is bad no amount of driver is going to fix that.  so its just bad if memtest86 passes all your sticks of ram like i said.

 

This was already done, as mentioned in my opening post, but not to that thorough of an extent. Five passes turned up no errors.



#16
oldskool

oldskool

    Newbie

  • Member
  • 46 posts
  • Joined 09-April 14
  • OS:2003 x64
  • Country: Country Flag

It wasn't clear to me that the test was ran.  The post was kinda long.  I had the same problem with X64bit and a bad stick of ram.  The error was not always the same.  I initially ran memtest and came up with no errors.  It wasn't until I started tested sticks individualy did the error occour.  I think your video card is bad man Idk what else to say.  There is only so many things that can cause those BSDs and the revolve around memory, bad sectors or HDDs, and Bad video cards.  I usppose other things could cause it but its easy to remove all cards wxcept the video card to narrow it down.



#17
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

Well, it was almost 19 days before I had another BSoD. Almost fooled me into thinking the clean reinstall of the nVidia drivers fixed the problem. However, it just happened again, another PAGE_FAULT_IN_NONPAGED_AREA. Here's what WhoCrashed has to say about it:
 
On Sun 4/27/2014 3:12:54 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042614-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0x50 (0xFFFFFA880C4857C0, 0x0, 0xFFFFF97FFF0416BC, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
 
The actual BSoD screen didn't mention ntoskrnl.exe, however, but win32k.sys.
 
As far as the circumstances of the crash, I can tell you that I had both Opera and Firefox running, as well as City of Heroes (I'd been using the demorecord system for a school project). Both browsers had at 15+ tabs open each. Firefox was in the foreground on a YouTube page, as I was listening to videos from a playlist while mucking around in CoH. I had tabbed to and from CoH multiple times, going between Firefox and CoH checking on certain commands I'd need to for the demorecord system. The BSoD happened as I was tabbed out of CoH and looking at Firefox the currently playing video on the playlist: there was a second or two of looped audio and screen freeze, followed by the BSoD screen.
 
Several of the other BSoDs since March involved having both Firefox and Opera open, and YouTube as well as a game being involved as well. There does seem to be some kind of pattern there.

 

Where should I go from here, you guys think?



#18
MagicAndre1981

MagicAndre1981

    after Windows 7 GA still Vista lover :)

  • Patrons
  • 6,184 posts
  • Joined 28-August 05
  • OS:Windows 8 x64
  • Country: Country Flag

Donator

without the dmp files we can't help you.


Posted Image

#19
5eraph

5eraph

    Update Packrat

  • MSFN Sponsor
  • 1,333 posts
  • Joined 04-July 05
  • OS:XP Pro x64
  • Country: Country Flag

Donator

Since you brought up Win32k, TrevMUN, there is a fix for what's probably an unrelated issue with memory allocation when using nVidia video drivers in XPx64. It has to do with desktop heap exhaustion when opening new windows or starting services, and not necessarily video performance.

The specific error is the following entry shown in Event Viewer (EventVwr.msc):
 

Event Type: Warning
Event Source: Win32k
Event Category: None
Event ID: 244
Date: Date
Time: Time
User: N/A
Computer: ServerName
Description: Failed to create a desktop due to desktop heap exhaustion.


A solution is hinted at in Guru3D's forums. Setting SessionViewSize to 120 MB (78 hex) fixes the problem for me. A reboot is required after adding or changing this registry entry.

INF format
HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management","SessionViewSize",0x10001,120
REG format
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"SessionViewSize"=dword:00000078

Edited by 5eraph, 27 April 2014 - 12:53 AM.


#20
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

without the dmp files we can't help you.

 

.dmp file attached to this post as a .zip.

 

 

Since you brought up Win32k, TrevMUN, there is a fix for what's probably an unrelated issue with memory allocation when using nVidia video drivers in XPx64. It has to do with desktop heap exhaustion when opening new windows or starting services, and not necessarily video performance.

 

I checked Event Viewer to see if that's ever come up, but it doesn't look like I've been hit by that problem. I'll keep this in mind if it ever does show up though.

Attached Files



#21
MagicAndre1981

MagicAndre1981

    after Windows 7 GA still Vista lover :)

  • Patrons
  • 6,184 posts
  • Joined 28-August 05
  • OS:Windows 8 x64
  • Country: Country Flag

Donator

 

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


Could not read faulting driver name
 

 

Run CPU-Z and look at that the RAM timings match to the SPD data.


Posted Image

#22
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

 

Run CPU-Z and look at that the RAM timings match to the SPD data.

 

 

I've never heard of this program until you mentioned it, and due to finals week I didn't have time to figure out what you meant by SPD data. I was going to try and set aside time to do that once finals ended, but wouldn't you know, I got yet another BSoD just earlier.

 

This is what WhoCrashed has to say about it:

 

On Fri 5/9/2014 7:57:57 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0xA (0x1C, 0x2, 0x1, 0xFFFFF800010F141F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

Different error message than the previous crash. I didn't notice any particular file mentioned in the BSoD message this time.

 

Between now and the previous crash I had been doing a lot of work in 3D Studio Max and Adobe Illustrator working on projects for my classes at uni. However, when the crash happened I didn't have them open. I had Opera, Firefox, and Pale Moon open: Firefox had an active tab with a video on it. Steam was also running, as I was letting it update itself/my library of games, but I had no actual game programs going.

 

Also, since you mentioned requiring it last time, MagicAndre, I've included the .dmp file for this crash if anyone wants to look at it.

Attached File  Mini050914-01.zip   23KB   3 downloads

 

EDIT: Okay, I just downloaded, installed, and ran CPU-Z to find out what MagicAndre meant by the SPD and RAM timings. I'm not entirely sure what it is that needs to match.

 

All four RAM sticks report a timings table of 333 MHz (JEDEC #2), 400 MHz (JEDEC #3), 400 MHz (EPP #1), and 333 MHz (EPP #2). All four sticks have a max bandwidth of PC2-6400 (400 MHz) and are using EPP 1.0. There is no difference in any of them that CPU-Z reports.


Edited by TrevMUN, 09 May 2014 - 02:42 AM.


#23
MagicAndre1981

MagicAndre1981

    after Windows 7 GA still Vista lover :)

  • Patrons
  • 6,184 posts
  • Joined 28-August 05
  • OS:Windows 8 x64
  • Country: Country Flag

Donator

the crash happens in steam.exe while doing GDI operation (win32k!vFillGRectDIB32BGRA):

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000000001c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800010f141f, address which referenced memory

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


WRITE_ADDRESS: GetUlongPtrFromAddress: unable to read from fffff800011db3c0
GetUlongFromAddress: unable to read from fffff800011db3e0
 000000000000001c 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiRestoreTransitionPte+9f
fffff800`010f141f 83411cff        add     dword ptr [rcx+1Ch],0FFFFFFFFh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Steam.exe

STACK_TEXT:  
00 nt!KeBugCheckEx
01 nt!KiBugCheckDispatch
02 nt!KiPageFault
03 nt!MiRestoreTransitionPte
04 nt!MiRemovePageFromList
05 nt!MiRemoveZeroPage
06 nt!MiResolveDemandZeroFault
07 nt!MiResolveProtoPteFault
08 nt!MiDispatchFault
09 nt!MmAccessFault
0a nt!KiPageFault
0b win32k!vFillGRectDIB32BGRA
0c win32k!bRectangleMesh
0d win32k!EngGradientFill
0e win32k!GreGradientFill
0f win32k!NtGdiGradientFill
10 nt!KiSystemServiceCopyEnd
11 0x0
12 nt!KiCallUserMode
13 0x0
14 0x0


IMAGE_NAME:  win32k.sys

FAILURE_BUCKET_ID:  X64_0xA_win32k!vFillGRectDIB32BGRA+36d

FAILURE_ID_HASH_STRING:  km:x64_0xa_win32k!vfillgrectdib32bgra+36d

nt!MiRestoreTransitionPte still looks like RAM issues.

 

Post some pictures of CPU-Z, please.


Posted Image

#24
TrevMUN

TrevMUN

    Junior

  • Member
  • Pip
  • 53 posts
  • Joined 26-March 14
  • OS:XP Pro x64
  • Country: Country Flag

Argh, it happened again not even five hours later! This time I got an entirely different BSoD error message, though. Here's what WhoCrashed says:

 

On Fri 5/9/2014 12:09:18 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050914-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2E890)
Bugcheck code: 0xC5 (0xFFFFFADD991B37A8, 0x2, 0x1, 0xFFFFF800011A9B28)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

As far as what I was doing: I had launched Steam again to let it finish updating itself/my games library. I opened a few games just to poke at them (such as the Minimum open beta, to see if I could run it--and I can). Ace Combat Assault Horizon for the PC was the other game I opened briefly. Unlike Minimum, ACAH's screen would flicker black occasionally. I shut the game down after a minute of poking at its options.

 

The crash happened all of a sudden an hour or two later when I had Opera, Firefox, Winamp, and OpenOffice open. The sound from Winamp hung in a looping state.

 

Here's the .dmp file for this crash.

Attached File  Mini050914-02.zip   23.86KB   1 downloads

 

the crash happens in steam.exe while doing GDI operation (win32k!vFillGRectDIB32BGRA):nt!MiRestoreTransitionPte still looks like RAM issues.

 

Post some pictures of CPU-Z, please.

 

Here you go.

Attached File  CPU-Z Information.zip   168.31KB   2 downloads

 

EDIT: Should I also post the dmp files from all the previous crashes since March?


Edited by TrevMUN, 09 May 2014 - 10:09 PM.


#25
MagicAndre1981

MagicAndre1981

    after Windows 7 GA still Vista lover :)

  • Patrons
  • 6,184 posts
  • Joined 28-August 05
  • OS:Windows 8 x64
  • Country: Country Flag

Donator

this time the crash happens while doing pool allocations (driver memory):

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: fffffadd991b37a8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800011a9b28, address which referenced memory

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


BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExAllocatePoolWithTag+c74
fffff800`011a9b28 48897008        mov     qword ptr [rax+8],rsi

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  realplay.exe


STACK_TEXT:  
00 nt!KeBugCheckEx
01 nt!KiBugCheckDispatch
02 nt!KiPageFault
03 nt!ExAllocatePoolWithTag
04 nt!ObpAllocateObject
05 nt!ObCreateObject
06 nt!IopParseDevice
07 nt!ObpLookupObjectName
08 nt!ObOpenObjectByName
09 nt!IopCreateFile
0a nt!CcPfGetSectionObject
0b nt!CcPfPrefetchSections
0c nt!CcPfPrefetchScenario
0d nt!CcPfBeginAppLaunch
0e nt!PspUserThreadStartup
0f nt!KiStartUserThread
10 nt!KiStartUserThreadReturn
11 0x0


SYMBOL_NAME:  nt!ExAllocatePoolWithTag+c74

FAILURE_BUCKET_ID:  X64_0xC5_2_nt!ExAllocatePoolWithTag+c74

BUCKET_ID:  X64_0xC5_2_nt!ExAllocatePoolWithTag+c74

run the driver verifier to get new and better dumps:

 

http://support.microsoft.com/kb/244617

 

 

The RAM timings are ok. You can also try to increase the RAM voltage a BIT to 1.825V.


Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users