[SOLVED] Windows 7 Professional 64-bit 0x0000003B SYSTEM_SERVICE_EXCEPTION (Param1=NTSTATUS:STATUS_NO_MEMORY)

ScrapMechanicFan2016

Active member
Joined
May 7, 2021
Posts
25
Location
Some Random Farmbot Infested World
i keep getting the bsod at least every day. idk why


the nvidia driver is up to date. and so are the others. plz help

Custom Build specs
Windows Vista Business Service Pack 2
Windows 7 Professional Service Pack 1
Windows 8.1 Pro (broken and wont be used)
all 64-bit
Windows 7 installed on Jan 13 2021
all OSs have been reinstalled a few times
CPU:Core i7 3770k
MB:MSI Z77A-G43
GPU:Gigabyte AORUS GTX 1060 6GB
RAM:32GB (4x8GB) G-Skill DDR3
PSU:Corsair GS700 700W
AV:Webroot Secure Anywhere
CPU IS BEING UNDERCLOCKED TO 3.2GHz(because i wanted to)
OS modifications(IMPORTANT BUT NOT ASKED FOR):UXthemePatch(tho was BSODING before that)
 
There doesn't appear to be any dump files unfortunately, apart from one kernel memory dump file. However, from the event log, I can see that the Stop 0x3B you've had was related to:

Rich (BB code):
0: kd> !error c0000017
Error code: (NTSTATUS) 0xc0000017 (3221225495) - {Not Enough Quota}  Not enough virtual memory or paging file quota is available to complete the specified operation.

Rich (BB code):
Event[5621]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2021-04-27T18:31:14.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: smtale-pc
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000017, 0xfffff80001e62e58, 0xfffff8800c910fd0, 0x0000000000000000). A dump was saved in: E:\Windows\MEMORY.DMP. Report Id:

Could you please post a screenshot of your page file settings?

BSODs but no Dump Files?
 
Why? It's always best to leave the processor at the default clock speed.
ik... i will fix it(it totally wasnt because it was running 5 degrees hotter than before)
There doesn't appear to be any dump files unfortunately, apart from one kernel memory dump file. However, from the event log, I can see that the Stop 0x3B you've had was related to:

Rich (BB code):
0: kd> !error c0000017
Error code: (NTSTATUS) 0xc0000017 (3221225495) - {Not Enough Quota}  Not enough virtual memory or paging file quota is available to complete the specified operation.

Rich (BB code):
Event[5621]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2021-04-27T18:31:14.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: smtale-pc
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000017, 0xfffff80001e62e58, 0xfffff8800c910fd0, 0x0000000000000000). A dump was saved in: E:\Windows\MEMORY.DMP. Report Id:

Could you please post a screenshot of your page file settings?

BSODs but no Dump Files?
sure no problem let me get it
i will add it as a reply to this
 
time to update on the situation. i copied 7 overtop the 8.1 Drive(as all 3 OSs are on seperate drives) and now 7 has so much room available. should i increase the
There doesn't appear to be any dump files unfortunately, apart from one kernel memory dump file. However, from the event log, I can see that the Stop 0x3B you've had was related to:

Rich (BB code):
0: kd> !error c0000017
Error code: (NTSTATUS) 0xc0000017 (3221225495) - {Not Enough Quota}  Not enough virtual memory or paging file quota is available to complete the specified operation.

Rich (BB code):
Event[5621]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2021-04-27T18:31:14.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: smtale-pc
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000017, 0xfffff80001e62e58, 0xfffff8800c910fd0, 0x0000000000000000). A dump was saved in: E:\Windows\MEMORY.DMP. Report Id:

Could you please post a screenshot of your page file settings?

BSODs but no Dump Files?

yep heres the page file settings
 

Attachments

  • Pagefile Settings.png
    Pagefile Settings.png
    27.7 KB · Views: 4
  • Pagefile Settings(part2).png
    Pagefile Settings(part2).png
    26.2 KB · Views: 4
I would individually set the paging file size as system managed for each drive and then select the checkbox at the top afterwards, just as a precautionary measure.
 
I would individually set the paging file size as system managed for each drive and then select the checkbox at the top afterwards, just as a precautionary measure.
k its set. will be responding again if it does bluescreen again. i will give it a full week of gaming and discord. and if i dont get a BSOD at all this week. well lets just say its fixed
 
Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

Find Check Disk (CHKDSK) results.

Code:
Event[4397]:
  Log Name: System
  Source: Ntfs
  Date: 2021-04-29T21:39:41.167
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: smtale-pc
  Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume G:.


Event[10099]:
  Log Name: System
  Source: Ntfs
  Date: 2021-04-15T22:21:22.526
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: smtale-pc
  Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume D:.

Code:
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
Free Space: 755.9 GB
Total Space: 953.9 GB
File System: NTFS
      Model: HGST  HTS721010A9E630 SCSI Disk Device

      Drive: D:
Free Space: 689.5 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: WDC WD20SPZX-22UA7T0 SCSI Disk Device

      Drive: E:
Free Space: 87.1 GB
Total Space: 228.9 GB
File System: NTFS
      Model: WDC WDS240G2G0B-00EP SCSI Disk Device

      Drive: G:
Free Space: 209.2 GB
Total Space: 715.4 GB
File System: NTFS
      Model: Hitachi HTS547575A9E384 SCSI Disk Device
 
Last edited by a moderator:
well today i got a Different BSOD

051021-40497-01.dmp 5/10/2021 18:58:34 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`045a3805 fffff880`02d0ac08 fffff880`02d0a470 nvlddmkm.sys nvlddmkm.sys+ccfc90 NVIDIA Windows Kernel Mode Driver, Version 466.27 NVIDIA Windows Kernel Mode Driver, Version 466.27 NVIDIA Corporation 27.21.14.6627 x64 nvlddmkm.sys+d2a805 E:\Windows\Minidump\051021-40497-01.dmp 8 15 7601 411,192 5/10/2021 19:01:28

yes im using the latest NVidia Driver. so 0x0000003B is solved. back to 0x1000007E
any ideas for this?
also i might just use this thread as a help for all BSODs i get on PC (windows 7 unless specified otherwise) lol

(copied the XP style BSOD from Bluescreenview because why not)

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: nvlddmkm.sys

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x1000007e (0xffffffffc0000005, 0xfffff880045a3805, 0xfffff88002d0ac08,
0xfffff88002d0a470)

*** nvlddmkm.sys - Address 0xfffff88004548c90 base at 0xfffff88003879000 DateStamp
0x60833867
 
Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

Find Check Disk (CHKDSK) results.

Code:
Event[4397]:
  Log Name: System
  Source: Ntfs
  Date: 2021-04-29T21:39:41.167
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: smtale-pc
  Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume G:.


Event[10099]:
  Log Name: System
  Source: Ntfs
  Date: 2021-04-15T22:21:22.526
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: smtale-pc
  Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume D:.

Code:
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
Free Space: 755.9 GB
Total Space: 953.9 GB
File System: NTFS
      Model: HGST  HTS721010A9E630 SCSI Disk Device

      Drive: D:
Free Space: 689.5 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: WDC WD20SPZX-22UA7T0 SCSI Disk Device

      Drive: E:
Free Space: 87.1 GB
Total Space: 228.9 GB
File System: NTFS
      Model: WDC WDS240G2G0B-00EP SCSI Disk Device

      Drive: G:
Free Space: 209.2 GB
Total Space: 715.4 GB
File System: NTFS
      Model: Hitachi HTS547575A9E384 SCSI Disk Device
that part usually happens when i force my PC off. so i ignore it mostly because i havent had data issues
 
so 0x0000003B is solved. back to 0x1000007E
any ideas for this?
also i might just use this thread as a help for all BSODs i get on PC (windows 7 unless specified otherwise) lol
The Stop 0x3B most likely wasn't caused by your graphics card driver, it was because there was no virtual memory remaining, because you didn't enable the system to manage the page file by itself. It appears that dump files are being produced now too which is good.

From the Stop 0x7E crash:

Rich (BB code):
5: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff880`03879000 fffff880`05d7f000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Apr 23 22:13:11 2021 (60833867)
    CheckSum:         0246CDF6
    ImageSize:        02506000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Rich (BB code):
5: kd> .cxr 0xfffff88002d0a470
rax=0000000000000000 rbx=fffffa8025b45f70 rcx=f885de149e000000
rdx=fffff8800409e870 rsi=fffffa8025b45f70 rdi=0000000000000000
rip=fffff880045a3805 rsp=fffff88002d0ae40 rbp=fffffa801f293390
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=000000000000000f r13=fffff88002d0b258
r14=0000000000000000 r15=fffffa801f104000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nvlddmkm+0xd2a805:
fffff880`045a3805 498b9e80000000  mov     rbx,qword ptr [r14+80h] ds:002b:00000000`00000080=????????????????

It appears that your graphics card driver was using a null pointer hence why the system crashed.

I would downloading the version from the support page which has a release date of the 29th April 2021. Please ensure that you perform a clean install of the driver using the following tutorial - Utilizing DDU Display Driver Uninstaller Properly
 
here u go. it saved it to my desktop due to my documents not being there rn
If you're concerned that the log collection tool will grab files from your documents folder; it doesn't. It looks in a particular set of directories and only gathers specific files from them.
 

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

Back
Top